Last modified: 2007-04-19 02:35:49 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 T11024, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 9024 - Restrict page moves in
Restrict page moves in
Product: Wikimedia
Classification: Unclassified
General/Unknown (Other open bugs)
All All
: Highest normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: shell
: 9566 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2007-02-18 17:23 UTC by Dantadd
Modified: 2007-04-19 02:35 UTC (History)
0 users

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


Description Dantadd 2007-02-18 17:23:26 UTC
After regular poll, editors in have decided to restrict move
pages to users with  45-day-old registered accounts. That's the first time I do
a request, I apologize in advance for any possible mistake.
Comment 1 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-02-18 19:06:53 UTC
That seems very restrictive.  It would probably be a good idea to run this past
the Foundation, via Foundation-l or whatnot, to make sure that they're okay with
that degree of restriction on page moves.
Comment 2 Dantadd 2007-02-18 20:31:40 UTC
Ok, but I think that a similar restriction is already running of fr.wikipedia. I
understand your concern and I will do what you suggested. In the meantime is
possible to set the same restriction used on or Thank you.
Comment 3 Dantadd 2007-02-22 23:57:47 UTC
As suggested, I've brought up the subject on the Foundation mail list and it's
been more than four days with 20 messages about the topic and 12 different

Nobody argued that there could be any problem with the Foundation. Therefore I'd
like to know if it's possible to set up what the Portuguese Wikipedia community

Comment 4 Dantadd 2007-03-02 13:52:37 UTC
We'd like to know if we will have any news about this subject any time soon. I
don't want to "rush" things, but it would be useful to have a idea when the
present request will be considered. 
Comment 5 Raimond Spekking 2007-04-12 14:25:12 UTC
*** Bug 9566 has been marked as a duplicate of this bug. ***
Comment 6 Dantadd 2007-04-12 14:31:03 UTC
*** Bug 9566 has been marked as a duplicate of this bug. ***
Comment 7 Dantadd 2007-04-12 14:31:58 UTC
I was forced to enter a new bug because since it seems that nobody cares for the
old one anymore. The
Portuguese Wikipedia community has decided, the Foundation didn't oppose the
request, then I BEG OF YOU to help us with our request. Please, we NEED this to
be done soon. Please, do not ignore our request. Thank you.

There must be a solution. We can not wait forever, and - as I said before
- at least temporarily it could be set a similar restriction that already exists
in the English or German Wikipedia.
Comment 8 Aaron Schulz 2007-04-12 14:52:58 UTC
Currently, move permissions leach of autoconfirmed, I suppose we'd need a new
dummy group for moveconfirmed...
Comment 9 Rob Church 2007-04-12 14:55:01 UTC
(In reply to comment #8)
> Currently, move permissions leach of autoconfirmed, I suppose we'd need a new
> dummy group for moveconfirmed...

That seems counterintuitive to the permission system, actually. A better overall
method would be to allow multiple implicit groups to be defined in the
configuration with individual requirements for the account age and edit count
prior to membership.
Comment 10 Dantadd 2007-04-13 14:19:18 UTC
Well, unfortunately I can't exchange ideas with you because I have absolutely no
knowledge of these technical questions. As I said, please, at least set the
"autoconfirmed" as already is done with and . Thanks.
Comment 11 Dantadd 2007-04-19 01:18:09 UTC
Please, at least set the "autoconfirmed" restriction already done on and

Please, we need this. I already BEGGING here. 

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