In T370230#9989106, @Samwilson wrote:

We could look again at putting the messages in WikimediaMessages, that'd be quicker to deploy, and we could then copy across all the translations that do get done to the extension when we're ready for that (so as to not waste translators' time).

Hi! If possible, I'm requesting a date and approximate time be chosen for when you'd like to do this for XTools. The db isn't big or anything, but it is used for shared session management, so taking it down I think will take down XTools entirely. Which date and time doesn't matter; I'd just like to put up a banner so folks know to expect it. Thank you!

@sbassett As you may have noticed, work on this extension stalled. We had to go the MediaWiki-extensions-Gadgets route for the initial launch, but we are planning to extensionize the code.

It's a different error now but we're at least letting the user know if the wish can't be parsed.

The bot has been updated. I'd move this task along, but only 2 days into the new Wishlist, we've already received a wish that was written in English but has a baselang of Russian (which I've since changed). This illustrates the necessity for a field in the form.

I think the message changes we were after have been made. Assigning this one to @STei-WMF !

Test case added to the Selenium test with https://gitlab.wikimedia.org/repos/commtech/wishlist-intake/-/merge_requests/209

I think this is done? Refer to Figma for designs

Thanks! Closing as declined.

Okay, with the TOC added, the bug mentioned here is avoided. The actual bug has been filed with VE (T369883), thanks Sam :)

Fixed by removing the TOC as part of T369878. Declaring this resolved.

When I save the content, it appears to not show this referenced bug. @DLynch is this something that the editing team has been tracking for some time?

See my existing wish: https://wishlist-test.toolforge.org/wiki/Community_Wishlist/Wishes/New_wish_with_a_link

It's not user-facing, but I think the errors are logged and thus we'll probably get yelled at to fix it. It is being proposed to remove the table of contents entirely at T369878. If we do that, it will fix this issue as well.

See also T368471: Wishlist intake does not play nicely with Vector 2022 section observer. Removing the TOC would fix that, too.

!183 merged. The other part of this is to have the bot read the baselang and set the page language.

Per some meeting the other day that included Jack, we're going to add an "invisible field" that's set to the interface language. We'll wait and see if we get any wishes written in the wrong language, and if so, then evaluate the need for adding a visible input in the form. For now we just want a means for the page language to change automatically to the user's language (which is usually the same as the interface language).

I think we can call this done.

Following T369764 we now have:

@dom_walden is this still happening for you? I can't repro. A lot of things were reworked yesterday so this might have gotten fixed in the process.

See also T369878: VisualEditor doesn't understand the wish template when editing as a full page which would I guess necessitate us reviving the "Edit with form" tab.