This is a puzzle to me.
shows the span tag, like above, when I open the category tree on my
test wiki running MediaWiki 1.31.1 with extension CategoryTree
(bundled in MediaWiki) enabled. That span tag should get parsed by the
browser, not be displayed.
This did not happen with new MW 1.31.1 install plus CategoryTree
(which is included in that version of MW). That expanded or closed the
category trees for me correctly.
It started happening when I dumped my wiki's database into that new MW
1.31.1 instance's database. Yes, I did run maintenance/update.php
after dumping my wiki's database in there. Didn't have any trouble
It is a puzzle to me whow the database input and update can cause this
problem of the span tag showing. The span tag is dynamic text -- it is
not selectable in the web browser. The rest of the page text is, but
that problem span tag and it's arrow is not, for example, when you
click on one of the ► arrows on my test wiki's Contents page, which
uses CategoryTree, here:
http://m.rogerchrisman.com/Contents you will see the problem <span tag.
I don't think my site root level URL shortening is the problem.
CategoryTree worked fine with that, till I dumped my teflpedia wiki's
database into above test wiki. That is when the <span tag started
The MediaWiki 1.22.2 wiki I am trying to upgrade
(http://teflpedia.org) uses an old version (from about 2013) of
CategoryTree that does not have this problem. I tested installing the
old version of CategoryTree on my upgraded wiki and that works fine.
However, I'd rather not use an out of date version, and I am puzzled
as to what is causing this <span style="color:#0645;"> tag to show up
displayed on the page instead of being interpreted as html the way it
normally is. It shows up in both Firefox and in Microsoft Edge on my
Windows 10 and in Firefox on my Xubuntu. Haven't tested other
Welcome to test it in your browser:
(and click one of the little arrows, not the category page names, to
expand or close the tree). That is what shows the problem <span tag.
Happy New Year!
I can't believe it, 2019... almost!