I use at least the last three, and will test this weekend
Thanks for the work on Lingo!!
Greg Rundlett
https://eQuality-Tech.com
https://freephile.org
On Fri, Mar 23, 2018 at 10:03 PM, Stephan Gambke
wrote:
> I worked on the Lingo extension ([1]) in the past few days,
I worked on the Lingo extension ([1]) in the past few days, fixing bugs and
restructuring the injected HTML to be less intrusive in the main article text.
In the past there were reports about incompatibilities with other extensions
and the latest changes should potentially fix some of these
Hi Kate,
We made a small change to the code which may or may not fix some of these
bugs - though not the last one, which I can't reproduce; we'll have to look
further into what's going on with that. But I would recommend upgrading
TinyMCE and trying it again.
-Yaron
On Fri, Mar 23, 2018 at 8:10
You are right that most VE installs won't actually be able to upgrade to
this newer version of Parsoid if they are running LTS versions of MW
(which probably most installations are -- looks like only a few hundred
installs are based on MW 1.31 and later according to
Heiya,
I apprechiate this e-mail informing about breaking changes.
So basically everybody still on MW 1.27 LTS, 1.29 and 1.30 will have to
hold parsoid updates since I do not assume that VE of December 12, 2017
will run on MW 1.27.x, etc.
I just hope that VE for MW 1.31 LTS will not have a hard
Hello everyone,
We are releasing the next version of the Parsoid deb and npm packages
(v0.9.0) later today. There is one significant change in this release
that might affect some VisualEditor installations. This version of
Parsoid wraps sections in tags and bumps the HTML version to
1.6.1.
Hi again,
I've found another bug with TinyMCE: when trying to edit a new category the
edit-link in the browser:
http://wiki.fhb.fh-swf.de/wiki/index.php?title=Kategorie:Test=tinymceedit=1
leads to the following errormessage:
Fatal error: Call to undefined method
Hi Yaron,
thank you for your quick answer.
To be honest, I'm not sure, where the inside the navigation-snippet came
from. I've managed to eliminate it with the help of the text-replace-extension
and now TinyMCE seems to have a lot less problems with the already existing
pages then before.