It seems like the solution here is to use the value of the constant, or to modify SMW to set the constant earlier.

WikiTeq would like to maintain this extension https://phabricator.wikimedia.org/T302773

Can you help with this please, @Legoktm ?

Can we request that this be put on hold please? WikiTeq might want to pick up maintenance of this extension. I'll probably know within a couple of months.

Unless there are any objections, I'll merge this soon.

Sorry I missed this before. We'll have a look.

I can't comment directly on the merits of the +2 requests because I don't know enough about the requirements and process. But I can attest that at WikiTeq @Kizule has always been eager to help and eager to learn. Of note, he steps in to perform important but less exciting tasks, and I think his commits reflect this as well.

Thanks!

I think it should be saved when the form is submitted (though I can see an argument against that)

Thanks @Kizule for your recent patches. I'm inclined to archive the extension instead of adding this to the WikiTeq group. There already is a more popular (though unmaintained) extension with similar functionality. What do you think @Kizule?

Noting that I agree with this request.

I agree that this extension should be archived. Thanks!

Fully understood. We started alerting wikis from WikiApiary. Please give us (WikiTeq) a week to try and find others. At that time, please feel free to publicize.

Should we be alerting the wikis using this extension? Is there a process for identifying who uses it (wikiapiary?) and who to contact? It seems like anyone using this extension is on an obsolete version of MediaWiki right now: https://wikiapiary.com/wiki/Extension:Push

Thanks @daniel ! And I agree with everything in your comment. We aren't seeking +2 on mediawiki. We're just asking for a Gerrit group so that we can do a better job of maintaining these and other extensions. I believe that I personally have +2 on all of these extensions, but relying on me to review and +2 patches has turned out to be a bad idea. We're trying to improve our extension maintenance and having this group would be helpful.

Should the task description say "Confluence to MediaWiki migration guide"?

We're going to give this a rewrite.

This was created for a third party wiki.

I think it's ready, but I don't have +2 on that repo.

There is actually a patch in review that quietly fixes this issue. It is https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Push/+/625988

Sorry about the delay in responding. I'll answer on behalf of @Vedmaka. We aren't working on this right now and we don't if/when we will be able to pick it up again.

Can we hold off on archiving this? We'll try and get the code in soon.

Sorry about the delay. I think we can get rid of it. The extension was written but I doubt that it will be released. If it does end up getting released I guess we'll just recreate the repo. Thanks!

I'm still the maintainer in theory, but not doing a very good job of it. At some point I'll need to give it an overhaul but feel free to break it as needed in the meantime. Thanks!

Just noting that it seems like this would be resolved by solving T20914.

WikiWorks is working on this task. We should have a patch within a week.

It seems that nobody's adopted this. Feel free to archive the skin and the accompanying CustomPage extension. Thanks!

I think the Flow composer settings should be inserted in composer.local.json, with something like this:

I think there are two separate bugs here, though they are related. The first is that data shouldn't be lost on MediaWiki update. The second is that the extension should work on fresh installs of MediaWiki 1.26+. Regarding that, I can confirm that the extension works on fresh installs of versions 1.28 and 1.29.

I believe this was fixed in dfc16883980d. Please re-test this by installing that version manually or trying the 1.29 or master branches.

That is indeed the case. The skin shows nothing, so it is a blank skin, with blank as an adjective.

Sorry about that. You are correct that GooglePlaces does not require GoogleAPIClient. The documentation was for an early version that was never released.

introduced by commit a66f25c

How do I recreate the error, please?