Last modified: 2014-07-05 12:44:37 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 T12814, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 10814 - Delete and move warning should be displayed for associated talk pages
Delete and move warning should be displayed for associated talk pages
Status: NEW
Product: MediaWiki
Classification: Unclassified
Special pages (Other open bugs)
unspecified
All All
: Low enhancement with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
:
: 18260 (view as bug list)
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2007-08-06 13:33 UTC by Meno25
Modified: 2014-07-05 12:44 UTC (History)
1 user (show)

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

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Meno25 2007-08-06 13:33:08 UTC 
When moving a page over another page (available only for sysops) the talk page is not moved if the talk page of the second page exists and an error message appears saying that the talk page was not moved. This should not happen, instead the delete and move warning should be displayed another time (first time for the page itself, second time for the talk page) for the talk page making it possible to move the page and its talk page together.
Comment 1 Andre Klapper 2014-07-05 12:44:21 UTC 
*** Bug 18260 has been marked as a duplicate of this bug. ***
Comment 2 Andre Klapper 2014-07-05 12:44:37 UTC 
Nowadays, when you move a normal page, you have the setting "Move associated talk page" autoticked (also see bug 17775).

I wonder if that influences this bug and if the overwriting of the Talk page is still silently dropped in the described case. Can anyone reproduce?
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links