Last modified: 2013-10-25 00:01:14 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 12263 - redirect on cross-page deletion
redirect on cross-page deletion
Status: NEW
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.9.x
All All
: Low minor (vote)
: ---
Assigned To: Nobody - You can work on this!
: testme
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-10 04:59 UTC by Robert Rohde
Modified: 2013-10-25 00:01 UTC (History)
2 users (show)

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


Attachments

Description Robert Rohde 2007-12-10 04:59:02 UTC
This bug is exotic and as far as I know not reproducable on any Wikimedia sites, but I am going to enter it here in case it is helpful to someone else someday.

I was writing a new Special Page for a private wiki.  One of the functions of this special page was to perform deletions on other pages and images via direct calls to Article->doDeleteArticle and Image->delete.

After calling either of these functions it appears that a $wgOut->mRedirect gets set to target the deleted page.  This interferes with the output of my Special Page by redirecting the content.  I've yet to figure out where this is occuring (and it is obviously quite well buried, because I spent a long time looking without success).

The obvious workaround is to cancel the redirect by doing the equivalent of $wgOut->mRedirect = '' after the deletion calls.

It also appears that this bug is not triggered by normal deletions because action=delete is embedded as a process in the normal article and image page views and the redirect is somehow being automatically cancelled if the current Title is the same as that for the hypothetical redirect.  (In other words, it doesn't try to issue a redirect if it thinks it is already at the right page.)

Obviously an exotic bug like this isn't much of a priority since it doesn't affect Wikimedia directly, but I felt it was worth posting a note after wasting several hours trying to pin down where the redirect was coming from.
Comment 1 Andre Klapper 2013-01-29 17:25:26 UTC
Hi Robert! Sorry that nobody has taken a look at this report yet and given feedback.

If this is still a problem in a recent MediaWiki version, is there any chance to get a minimal testcase, e.g. the code of that "Special Page" that you have written?
Comment 2 Bawolff (Brian Wolff) 2013-02-06 15:53:50 UTC
(In reply to comment #0)
> This bug is exotic and as far as I know not reproducable on any Wikimedia
> sites, but I am going to enter it here in case it is helpful to someone else
> someday.
> 
> I was writing a new Special Page for a private wiki.  One of the functions of
> this special page was to perform deletions on other pages and images via
> direct
> calls to Article->doDeleteArticle and Image->delete.
> 
> After calling either of these functions it appears that a $wgOut->mRedirect
> gets set to target the deleted page.  This interferes with the output of my
> Special Page by redirecting the content.  I've yet to figure out where this
> is
> occuring (and it is obviously quite well buried, because I spent a long time
> looking without success).
> 

That is odd sounding. It certainly shouldn't happen (ui should be separate from the actual delete action). A lot has changed in MediaWiki since 2007 in these areas, I wonder if this bug is still present.
Comment 3 Andre Klapper 2013-10-25 00:01:14 UTC
Robert: Does this still happen?

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


Navigation
Links