Here are the release notes for FANDOM's code release scheduled for February 20, 2018:
- BUGFIX: We will fix a situation that could result in duplicate template contents being substituted into an article when using the classic rich text editor.
Here are the release notes for FANDOM's code release scheduled for February 20, 2018:
Andrewds1021 wrote: Wasn't this already fixed? Or was it previously just for some cases?
There are multiple cases to fix - and we're still looking at some more.
@MechQueste : the recent major classic rich text editor update turned many templates from puzzle pieces into rendered templates, but technical restrictions means we can't do that for everything (and we've had to scale it back a bit from the original release).
Why was ever since the classic RTE has been upgraded, there are always bugs in it?
That's what happens every time a product upgrades. It's not specific to RTE nor Wikia.
RTE is a tricky product that needs a lot more testing by users than by QA. Nobody really knows how can users use wikitext in a way that may break RTE.
I mean, I do know that a new product or an upgrade to a product can cause a few bugs, but I didn't expect a lot of bugs just because of the RTE upgrade. Thanks for the information, anyways.
KockaAdmiralac hit the nail on the head there - and this editor update in particular was very significant internally, even though not a great deal visibly changed for editors. Wikitext is incredibly, amazingly flexible - but this means there's many edge cases that have to be accounted for.
Note: We've no special release notes for the next release (Wednesday), so no new Technical Update post today.
Siblings of .cke_button were recently updated, however, a few siblings of .cke_button_big seem to have been inadvertently skipped and still use the old classes.
For the Add Table and Add Infobox buttons that appear in the RTE rail, they were updated. For the others, they were missed. The following classes need to be updated to the newer ones.
On a side note, the old popover modals also ought to be updated or replaced. Among other things, they aggressively violate the principle that "tables should be used for data, not design".