Last modified: 2011-03-04 13:33:57 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 9007 - & in expressions cuts adress bar link off
& in expressions cuts adress bar link off
Product: MediaWiki extensions
Classification: Unclassified
WikiLexicalData/OmegaWiki (Other open bugs)
PC Windows XP
: Normal minor (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
  Show dependency treegraph
Reported: 2007-02-17 01:47 UTC by Martin Killmann
Modified: 2011-03-04 13:33 UTC (History)
1 user (show)

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


Description Martin Killmann 2007-02-17 01:47:54 UTC
The bug appeared while creating

If you click on the syntranses that contain & (ampersand), the expression is cut
off before the ampersand in the adress bar. The software needs to wrap around
the & to display the correct link.
Comment 1 Brion Vibber 2007-02-18 20:42:18 UTC
The problem here is probably the rewrite rules; it looks like the site is
rewriting URLs to a form like index.php?title=$1 ... this will break the
parameter when a %26 occurs because Apache forces it to be de-escaped to & for
reasons not known to mortal man.

As a hackaround on the broken rewrite scheme, you could use the patch for Apache
1.3.x we provide which adds a rewrite function to re-escape the & in the title.


A cleaner method with an Alias may be preferable, depending on configuration.
Comment 2 Kipmaster 2011-03-04 13:33:57 UTC
Seems to work as expected now.

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