We should probably validate the keys of the fields. There should be some reserved names and things like }}}#DROPTABLE should be disallowed. Not that they would work.

Un-assigning myself. I don't see how can a possible future change in backend logic help solve a trivial UI issue.

Un-assigning myself. I've also detached this from the tree of tasks, as this is self-contained right now.

Closing this, as there is no interest in this feature from any party, and there are major technical challenges to overcome. It's not likely anyone will ever do this.

Post mortem comment: when introducing the new config format, I've noticed that the serializer will single-quote strings that contain single quotes, which in case of markup like '''bold''' produces the completely unreadable '''''''bold'''''''. I've managed to fix this upstream (see PR), but the change went into the 6.1 branch, which is only compatible with PHP 8. So, we will get better string handling, but only after MW upgrades to PHP 8. Uhhh ehhh, ok.

Ok, let's formalize this. Let U be the Hermitian matrix representing the user at time step t0... no, just kidding.

Note: this will be a bit frustrating when you just want to add an extra line in a campaign. One solution would be to allow adding pre-/postfixes to the description template, but what about e.g. extra arguments to {{Information}}?

Solution draft:

In T292926#7445550, @Jdlrobson wrote:

However, since you want to disable some previews, then I'd advise a solution in the API. The API is how we communicate if previews are available. In the REST base endpoint we use in production for English Wikipedia, we have special handling for certain namespaces and types of links, so in this case, I'd imagine the API would reject the request, or serve a generic preview. That said I assume you are using TextExtracts?

@roman-stolar I've submitted an initial version of the excessively large patch, but there's really one interesting piece of code here: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/MediaUploader/+/730888/1/includes/Campaign/CampaignContent.php#172

In T292926#7421641, @Jdlrobson wrote:

• It sounds like when a user is viewing a page NS_TEXT_GAME you do not want to show page previews to anything that links to a page in NS_TEXT_GAME. Is this correct? Or is that you never want to show previews for links to NS_TEXT_GAME for any namespace? For example would previews show on Special:All pages ?

In T292926#7420514, @Jdlrobson wrote:

Could you explain to me why you can't modify $wgContentNamespaces ? Are you relying on another feature such as Special:Random ?

I got all the existing configuration settings wrong, so I just edited the task description. The point still stands.

Great, that should simplify the mess around content handlers, I'll look into it in a few days. Probably some serious refactoring will be involved.

THICC is in the process of being archived: T292948: Archive the THICC extension

See: T292948: Archive the THICC extension

...but it was a really good task.

See: T292948: Archive the THICC extension

See: T292948: Archive the THICC extension

See: T292948: Archive the THICC extension

See: T292948: Archive the THICC extension

See: T292948: Archive the THICC extension

See: T292948: Archive the THICC extension

See: T292948: Archive the THICC extension

See: T292948: Archive the THICC extension

See: T292948: Archive the THICC extension

See: T292948: Archive the THICC extension

I've just noticed this in the docs: Popups appear on links to pages in content namespaces only. This is a limitation of Popups; TextExtracts are available from other namespaces.

This should wait for a few other MVP-related tasks to finish, to minimize the amount of changes after the translation goes public.

In T292011#7385545, @DannyS712 wrote:

Hmm, except both of the extensions (it looks like MediaUpload's code is a copy of UploadWizard)