Last modified: 2014-09-18 02:28:38 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 T72062, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 70062 - Changing protection on already-existing protection results in error
Changing protection on already-existing protection results in error
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
Page protection (Other open bugs)
1.24rc
All All
: Normal normal (vote)
: ---
Assigned To: Jackmcbarn
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-08-26 20:12 UTC by Courcelleswiki
Modified: 2014-09-18 02:28 UTC (History)
1 user (show)

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


Attachments

Description Courcelleswiki 2014-08-26 20:12:56 UTC
So, a page is indef protected from moves; when I go in and change the edit protection (or pending changes protection) the move protection time selector does not go to "indefinite", it goes to "other time".  (Even if I set a time for other protections).  This results in an error when trying to save the page.

Shouldn't the existing protection and proper expiration show when modifying move protections?  (Time-limited move protections work properly, the problem appears to be indefinite protections.)  I've verified the problem on both en.wp and meta.
Comment 1 Gerrit Notification Bot 2014-08-29 15:34:08 UTC
Change 157160 had a related patch set uploaded by Jackmcbarn:
Supprt existing expiry time when it's infinity

https://gerrit.wikimedia.org/r/157160
Comment 2 Gerrit Notification Bot 2014-09-18 02:27:59 UTC
Change 157160 merged by jenkins-bot:
Don't break existing expiry time of "infinity" when modifying protection

https://gerrit.wikimedia.org/r/157160
Comment 3 Jackmcbarn 2014-09-18 02:28:38 UTC
The fix will be live on the entire WMF cluster on September 25th.

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


Navigation
Links