Last modified: 2006-09-24 06:54:35 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 7029 - __NOGALLERY__ does not work with url in php form
__NOGALLERY__ does not work with url in php form
Product: MediaWiki
Classification: Unclassified
Categories (Other open bugs)
All All
: Normal minor with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2006-08-16 12:32 UTC by Duncan Harris
Modified: 2006-09-24 06:54 UTC (History)
0 users

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


Description Duncan Harris 2006-08-16 12:32:07 UTC
__NOGALLERY__ tag stops a category from displaying images.  This is important
for fair use because we can't produce a gallery of work under fair use criteria.

However, it does not work if the url is in the form: 

e.g. as produced by the link from the Table of Contents:
Comment 1 Raimond Spekking 2006-08-16 15:45:39 UTC
See Bug 6031 too. 

action=edit - images are shown: 

action=purge - images are not shown:
Comment 2 Duncan Harris 2006-08-16 17:21:29 UTC
Actually when you edit you don't see anything, but you wouldn't expect to.

If you then click preview on the other hand, it again doesn't work, so I think
this is a bug which appears whenever the php url is used.
Comment 3 Raimond Spekking 2006-08-16 17:24:56 UTC
If preferences "Show preview on first edit" you can see the effect instantly.
Comment 4 Duncan Harris 2006-09-23 18:28:46 UTC
Seems now this has been fixed.

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