I think this is done!

This problems are not logner valid because the changes in the skin and more in general in the ui. There are some other bugs which needs to be fixed, but I would simply open another ticket instead of using this one.

this was fixed with great style by @crisbal

I built the Visual Editor gadgets.

the bot is ready, we need only to use it when is needed, right?

this is fixed?

did I answer you enough on the chat?

I'm writing the bot.

The gadget for visual editor seems to me the best options. We have not a real alternative I think.

I can understand your fear but I think this is still the best option we found when we were choosing what to do with templates. My idea would be to extend visual editor with a gadget listing all the main templates, so when a user choose to insert a predefined template the opening template and closing one are automatically inserted (I don't know if it possible though).

I would like to reopen this task and discuss it a little bit further.
if we implement the solution number 3, this would require instructing the editors about remembering to close the tag (and this requiring the editor to double interact with VE interface).

All the dmath tags have been removed from the production website.

Seems like I can't reproduce the bug anymore :/

Check if code editor is working correctly:
I found that if insert a new formula it shows you a big textarea where you can write. If you save it and then redit that formula, the textarea become just 2 rows large.

Just to confirm, the bot will be able to work without requiring an atomic change, i.e. pages can be converted one by one, as backwards compatibility has been preserved.

The solution #3 has been implemented, so you would write something like this, for example:

In T3057#43963, @crisbal wrote:

Have we checked if this works?

https://www.mediawiki.org/wiki/VisualEditor/Portal/TemplateData

This might be what we need, I could check it today and report back

Have we checked if this works?

perfect, the important that is somewhere in the best place!

In T2880#43260, @mte90 wrote:

I added that step in a new paragraph Update MediaWiki http://meta.wikitolearn.org/WikiToLearn_Home/WikitoLearn_Home_Documentation/Local_WikiToLearn_Instance

Sexy :-) remember that now you should also be able to close tasks via git commits!

nope, I think what I wrote is what we want, i.e. releasing 0.8 with VisualEditor in "test" mode, i.e. only users who explicitly select it will see it.

Reading https://www.mediawiki.org/wiki/Extension:VisualEditor#Complete_list_of_configuration_options I don't understand what AutoAccountEnable really does. Do you think it can be helpful?

You simply need to include in LocalSettings.php the following line:

$wgDefaultUserOptions['visualeditor-enable'] = 0;

This will make VisualEditor be off by default, but enablable for each user under their preferences

It should be fixed with b701e7c32b8116bfcc6d46042142c44ba39d652f

Keep in mind that it's the Echo extension that triggers the html attribute of the notifcations to set them grey when read and blue when unread. But its' really strange that with the new version it has suddenly disappeared. If someone wants to dig in it I think it's pure css to handle on Neverland. Here is the guide

Let's wait for the staging instance to test it better

In T2968#43595, @ruphy wrote:

OK, so we should mark it as invalid?

OK, so we should mark it as invalid?

They said me it's a restbase warm-up problem.

In T2975#41545, @tomaluca wrote:

I think we can add a "Deprecated" message on the UI for the next relase to make a gracefull replacement.

In case this is still open, we should file an upstream ticket with a proper testcase!

I think grey is a great color, and we should have them stand out if needed (i.e. when you receive a message). In that case, green is a great highlight colour.

I spotted a bug on the local instance.

any news for it? in case i can do the css code to get the old ones

@rigolo add the extension. Wee need it

I added that step in a new paragraph Update MediaWiki http://meta.wikitolearn.org/WikiToLearn_Home/WikitoLearn_Home_Documentation/Local_WikiToLearn_Instance

First version by me http://meta.wikitolearn.org/Tech_Team/Phabricator

In T3122#43013, @grigoletti wrote:

We found that using TemplateData template are loaded and autocompleted correctly. Should we integrate this extension?

Would have clarified what extension it looks.. but from the above thread , I think it's clear..

I don't know exactly which file is it. Why are you asking?

Do you see the changes from the current version? We have gray buttons for the notifications. Do we want to keep the new ones like this?

What's the file name which calls the input widget for the template ?

@tomaluca me and @davidev made some tries to see what's going on. It seems that when you're trying to insert a string on the input field there is a query calling templatedata (an extension that provides metadata for visualedtior about templates: https://www.mediawiki.org/wiki/Extension:TemplateData)

Now it works. Maybe cache? Sorry :(

In T2895#43010, @davidev wrote:

When a new page is inserted in the URL bar, the only option to create the page is "Create with wikitext".

Is it a bug?

When a new page is inserted in the URL bar, the only option to create the page is "Create with wikitext".

I don't understand what the problem is here. Can you clarify?

It seems fixed as of now. I will close the task. If there are some others glitches I will reopen it