Jan 2 2018
Thanks @Bawolff for the explanation as well as the workaround - hardly something I would have thought of!
Dec 27 2017
Aug 5 2017
It makes sense to restrict the envisaged 'usedebugtoolbar' permission to sysops or bureaucrats by default. It would be a breaking change so that's why I made the suggestion but I'm fine with either approach.
I'm not sure how much discussion we still need. For a smooth transition, I'd say: if the toolbar is enabled, show it to all users by default (current situation) and offer a config setting to tie its visibility to specific user rights.
Jul 17 2017
Speaking on behalf of a lot more people than just myself, this is certainly one of the most impactful and enduring issues that I've had to encounter since last year, although much has been improved.
Apr 16 2017
Alright, thanks - it's a no-go then.
Apr 9 2017
Jan 15 2017
In 1.26 we are on line 1035 for this.
Jan 11 2017
Could this be related to T153618 ?
Jan 9 2017
okay, thanks for working on this
Jan 8 2017
Experiencing the same issue following an upgrade to MW 1.28 (on a Windows machine). The version of SMW I'm using is recent, however (2.4.4).
Feb 11 2016
Feb 7 2016
Jan 23 2016
FWIW, ICU's collation demo has a setting for numerical sorting: https://ssl.icu-project.org/icu-bin/collation.html
Oct 23 2015
Sep 25 2015
Shouldn't we wait until VPS hosting or cloud hosting is at least in a comparable price/budget range as shared hosting today? Not to put too fine a point on it, not being able to upgrade could be a personal disaster. I'm running a large and complex site with Semantic MediaWiki (my main reason for sticking with MediaWiki) and forty-odd extensions - Composer is used to install some of these locally before the files are transferred to the remove server. $10 a month is still an awful lot of money to me so the costs of relocating would be forbidding I'm afraid.
Apr 2 2015
Mar 20 2015
Mar 17 2015
Jan 18 2015
Task created: T86959
Jan 15 2015
Jan 14 2015
Thanks Cicalese for your speedy reply!
I'm using SF 3.0 (SMW 1.9, MW 1.22) and the mapping template still does not work with such input types as "combobox", "tokens" or "text with autocomplete". This may be due to certain issues with "combobox" and "tokens", because in some cases they autocomplete on the wrong category.