Here is the procedure:
I choose text + title for the translated article
I click the "Start a new translation"
The page I arrive at has the original to the left, an empty field to the right, and a grey "Publish translation" button
I click the paragraphs, one by one, and get translations from Apertium. Now, things go good or bad:
After my first click, I get translated text, and the grey button turn green. Now I know I may continue, I will be able to publish in the end.
After my first click, I get translated text, but the grey button does NOT turn green. Now I know I have to abandon this translation. No matter what I do, I will not be able to translate on any point. The button will stay gray, and nothing will happend when I press the grey button.
No other error message turns up. The button either starts out gray and continues as gray, or it turns green when the first paragraph is translated (I imagine the program scans the text for errors)..
|Resolved||Amire80||T95655 CX Phase 2 deployment issues (tracking)|
|Open||None||T96003 Publishing and saving errors (tracking)|
|Resolved||• Nikerabbit||T120837 Publish button does not become active when editing the translation|
yes, sometimes (appr in 20% of the cases) I am able to publish ("green button"), and sometimes I am not. Unfortunately, I have not been able to spot any correlating factor (I have tried varying article type). But as long as I do not know what causes the problem it is also hard to look for it. I also have not got any feedback from others in this thread as to whether they are able to replicate my results, or whether nb-no works for them.
After a meeting today with Runa and Niklas, it turned out that I had an old .js page under my user page area (having to do with author counting of WP pages). After deleting it, all pages tested so far work. I will return with more info, but at present it seems that my bug (the grau button not turning green for nb->nn) is solved.
Content Translation is known to be susceptible to other scripts causing issues, specifically gadgets. We can add local user scripts to the list of suspects.
Do reopen this bug if the issue still occurs.