Last modified: 2014-01-03 17:08:43 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 12619 - cleaner URLs for editing, previewing skins, etc.
cleaner URLs for editing, previewing skins, etc.
Status: REOPENED
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.11.x
All All
: Lowest enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
http://onekopakaspace.strangled.net/w...
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-01-14 01:06 UTC by Darren VanBuren
Modified: 2014-01-03 17:08 UTC (History)
5 users (show)

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


Attachments

Description Darren VanBuren 2008-01-14 01:06:06 UTC
Very easy fix. If clean URLs are in use we should use things like this:
wiki/index.php/Sandbox?action=edit

Currently we do things like this:
wiki/index.php?title=Sandbox&action=edit

The first is much cleaner, and used by competing wiki software such as MoinMoin.

They work just the same, see the URL, which is demonstrating the first style of URLs.
Works like this just fine on Wikimedia sites:
wiki/Sandbox?action=edit
Comment 1 Daniel Friesen 2008-01-14 02:40:15 UTC
Then what happens when someone uses path to query rewrites?

/wiki/Sandbox?action=edit
becomes:
/index.php?title=Sandbox?action=edit
Then no-one is able to edit...

Something like this is already possible if someone configures it that way in $wgActionPaths.
Things like this should not be automatic, because there is a strong chance that new setups may be broken by it.
Comment 2 Brion Vibber 2008-01-14 23:45:45 UTC
(The rewrite case mentioned in comment #1 would be due to misconfigured rewrite rules -- you should use the QSA option, otherwise you break various forms in the system as it is.)

While it would be possible to append various options direct to a plain view path, there are several arguments against it. Chief among them are my favorites:


First, the lack of a consistent prefix for non-view links means they can't be excluded cleanly from robots.txt; this can lead to excessive search spider traffic. (Meta tags will keep edit pages and such out of indexes, but the spider has to load the pages to reach the meta tags.)

Second, autocomplete algorithms in browser URL bars will sometimes pick up such URLs, and you find yourself acccidentally hitting enter for a different action than you intended. Personally I find that a bit annoying. :)


The first is functional and the second is merely aesthetic, but I consider them worthy. :) My own preference for prettier action URLs is to add additional prefixes with $wgActionPaths and either stub scripts or rewrite rules, eg /edit/Sandbox
Comment 3 Gabriel Wicke 2014-01-03 17:08:43 UTC
(In reply to comment #2)
> First, the lack of a consistent prefix for non-view links means they can't be
> excluded cleanly from robots.txt;

This is no longer the case as search engines now support glob rules: https://www.mediawiki.org/wiki/Requests_for_comment/Clean_up_URLs#Migration

> Second, autocomplete algorithms in browser URL bars will sometimes pick up
> such
> URLs, and you find yourself acccidentally hitting enter for a different
> action
> than you intended. Personally I find that a bit annoying. :)

At least in Chrome, the same is actually true for the ugly /w/index.php?title=...&action=..., but in that case it is harder to get to the actual article URI by just deleting the query.

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


Navigation
Links