Topic on Template talk:Extension

needs-updatephp = Yes

6
Kghbln (talkcontribs)

.. not loaded reliably via "extension.json". I guess because something was not specified correctly in the respective extension's file. Until this is fixed we do need to add this information again. Since it appears that this information was now deleted unconditionally in masses we could have run in documentation issues like the one I fixed for External Data

Pppery (talkcontribs)

This bit of autoloading has actually existed since 2018, and was originally added by Bawolff. It works by checking if the extension defines the LoadExtensionSchemaUpdates hook in extension.json.

Kghbln (talkcontribs)

This means that this field cannot reliably be filled since this particular extension does not use this hook...

Bawolff (talkcontribs)

I always assumed we would keep manually specifying for exts that cant be autodetected or arent in gerrit.

Pppery (talkcontribs)

So, what's happening here is that I erroneously assumed that the code would work for every extension that is in Gerrit and uses extension registration, and thus batch removed all information that could be loaded from the repo whenever I noticed that the hooks (or, occasionally, other loadable information) were outdated. It appears that assumption was incorrect, and I'll try to be more careful if I do that kind of cleanup again.

Pppery (talkcontribs)

I've looked through all 216 pages recently converted by myself or Shirayuki to load stuff from extension.json, and re-added information that shouldn't have been removed to about 15 of them. In four cases (DataTable2, AccessControl, ImageRating, WikibaseMediaInfo), this was |needs-updatephp=yes, and in the rest of them it was other information that probably should be in extension.json in the repo, but isn't.

Reply to "needs-updatephp = Yes"