Tech:Noticeboard/Notice about the SocialProfile extension

{{ {{Mbox|text=This page is a draft}} }} The SocialProfile extension adds several features to a user’s profile, such as avatars, adding friends/foes, and gifting. It was a popular extension, but also generated a disproportionate amount of burden for the Technology Team due to multiple issues:

  • SocialProfile only supports LTS versions of MediaWiki (1.43 right now; 1.47 once it releases), while Miraheze upgrades to every stable version (we are on MediaWiki 1.46). Issues we encounter may not be fixed by maintainers of the extension because they do not support our MediaWiki version (see for example T443385).
  • SocialProfile has some heavy technical debt that is still not resolved. For example, it does not use extension registration, a feature available since MediaWiki 1.25 and adopted by almost all extensions (see T152865).
  • SocialProfile only receives the minimal amount of maintenance, and non-critical bugs are often left unaddressed.
  • Other problems which cannot be disclosed right now.

In light of the above, the Technology Team has already restricted the extension so that no new wiki can enable it. Due to its popularity, we will not remove SocialProfile outright. However, we will no longer offer the same level of support for this extension. Wikis are encouraged to disable SocialProfile and use UserProfileV2 instead.

Wikis that stay on SocialProfile are more likely to encounter bugs and other breaking changes when using the extension and are unlikely to receive help from the technology team. If members of the community still want to continue using the extension, they can report bugs upstream to maintainers of SocialTools and send fixes to gerrit.

Discussion

NEWSECTIONLINK Please reply here. PetraMagna (talk) 11:15, 6 November 2026 (UTC)

I’ve been thinking about a migration script from SocialProfile to UserProfileV2 which imports avatars and descriptions of oneself. However, with our current shortage in technology team members this is unlikely to happen. PetraMagna (talk) 11:17, 6 November 2026 (UTC) I would appreciate this as a prominent user of the extension, though I would understand why it’s not possible. Would the data for the extension still exist if I disable it? –zeus, f• k• a blad 13:24, 6 November 2026 (UTC) It will still exist. So the workflow would be as follows: disable SocialProfile, enable UPV2, and then migrate data from SocialProfile (no longer accessible by users but are still in the database) into UPV2. PetraMagna (talk) 00:32, 7 November 2026 (UTC) I like this idea and would be curious on how it could be done; could profile images on swift be reused or do we need to handle moving files to a new container and changing names and such? I imagine other pieces of data would be a lot easier to transfer by yoinking data from SP’s database into UPV2 (I would check the schemas now but GitLab decided to hit me with a cinder block rate limit so I can’t see UPV2’s source).
If we don’t have a task on Phorge for this idea yet, may be a good idea to make one so the idea doesn’t evaporate, and for visibility for new and prospective techers to take. — PixDeVl (T|C|G) 05:15, 7 November 2026 (UTC)


Go to Source →