Last modified: 2014-07-12 11:12:56 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T69415, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 67415 - String "display:none" is generally blacklisted and should not be. It must be whitelisteable, at least.
String "display:none" is generally blacklisted and should not be. It must be ...
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Unprioritized major with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
http://wiki.piratenpartei.de/wiki/ind...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-07-02 14:18 UTC by Purodha Blissenbach
Modified: 2014-07-12 11:12 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Purodha Blissenbach 2014-07-02 14:18:05 UTC
You cannot save wiki pages having the string "display:none" inside. You cannot even put the string into the page MediaWiki:Spam-whitelist so as to get rid of this nonsential and by far too broad limitiation.

I was unable to find the place where it is blacklisted even after extensive rtfm, thus this bug is against MediaWiiki. If you happen to know the right place/extension, please move it.

While I understand that SPAMmers use the string so as to hide their spam from readers and expose it to machines, there are plenty of good uses, most prominently inside user written navigational templates using CSS to reveal parts only on :hover with the mouse, which need to be initialized with a display:none property.

So I request to either drop display:none from its respective blacklist or allow it to be whitelisted.

BTW: While you can easily overcome the blacklisting with some html-comment or nowiki magic when saving pages, both system and user CSS pages stop working if you do. This is opposed to what sane users would expect.
Comment 1 Bartosz Dziewoński 2014-07-02 15:33:36 UTC
I am not aware of any such blacklist. Have you verified that this isn't caused by one of your antispam extensions? http://wiki.piratenpartei.de/Spezial:Version#sv-credits-antispam
Comment 2 Bawolff (Brian Wolff) 2014-07-02 17:40:20 UTC
This definitely works fine in default mediawiki. Inclined to call this not a bug. If you configured your wiki not to allow some text via $wgSpamRegex or some extension, that doesn't make it a bug in mediawiki.
Comment 3 Purodha Blissenbach 2014-07-02 19:05:30 UTC
I clearly state that I was not able to figure out why it is blacklisted.
Yes I put effords in it, until I was not able to find any more place to check and I ran out of ideas.
It is not blacklisted by wiki configuration, to the best of my knowledge.

If something is rejected by an anti-SPAM measures, one (at least an admin) should be able to figure out why, and how to change it. A generic message, which we see, is certainly not sufficient if you want to call this bug report 'not a bug', because then the problem cannot be solved.
Comment 4 Andre Klapper 2014-07-02 19:57:51 UTC
http://wiki.piratenpartei.de/Spezial:Version#sv-credits-antispam lists:
Abuse Filter 	(40d66e5) 22:02, 8. Apr. 2014
AntiSpoof 	(97c04d4) 21:37, 6. Apr. 2014
ConfirmEdit (Version 1.3) (254982a) 22:34, 7. Apr. 2014
Title Blacklist (Version 1.5.0) (ead5577) 22:38, 7. Apr. 2014

https://test2.wikipedia.org/w/index.php?title=Special:Version#sv-credits-antispam lists:
Abuse Filter	–	
AntiSpoof	–
ConfirmEdit	1.3
SpamBlacklist	–
Title Blacklist	1.5.0

I just created https://test2.wikipedia.org/wiki/67415 successful with the first sentence of this bug report which does include the string display:none.

So based on default configuration there's very either no bug in the extensions code, or there was a bug that we have not heard of which was fixed in code changes within the last ~80 days. 
Still it's very very likely an issue with the configuration of your wiki.

I'm also proposing to close this as INVALID - sounds like a request for support on https://www.mediawiki.org/wiki/Project:Support_desk
Comment 5 Bartosz Dziewoński 2014-07-02 20:39:00 UTC
(In reply to Purodha Blissenbach from comment #3)
> I clearly state that I was not able to figure out why it is blacklisted.
> Yes I put effords in it, until I was not able to find any more place to
> check and I ran out of ideas.

By "Have you verified that this isn't caused by one of your antispam extensions?", I meant "Try disabling all of the antispam extensions and see if that fixes the issue".
Comment 6 Purodha Blissenbach 2014-07-03 01:25:18 UTC
(In reply to Bartosz Dziewoński from comment #5)
> By "Have you verified that this isn't caused by one of your antispam
> extensions?", I meant "Try disabling all of the antispam extensions and see
> if that fixes the issue".
I cannot enable or disable extensions in the wiki. Even if I could, I would be hesitant to do so in a heavily used production site.

(If I had a chance to try something the like, believe me, I had done that already) But that is nothing that solves this bug, since any message has to make clear to the user what (s)he can do to. Users complain to us admins, and even we do not know what to do or how to find out. _That_ is the problem. If it is/was an issue of the wiki configuration, where to look for it? An how to fix it?
Comment 7 This, that and the other (TTO) 2014-07-03 02:48:22 UTC
It is almost certainly because this string is present in $wgSpamRegex in the wiki's LocalSettings.php. You should ask the server administrator to take it out.

I just added $wgSpamRegex = '/display:none/'; to my LocalSettings.php and I get the exact same error message.
Comment 8 Purodha Blissenbach 2014-07-12 11:12:56 UTC
Thank you for your help. The fix was made in the wiki as suggested.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links