Last modified: 2007-04-27 17:48:39 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 9583 - Cascading protection has no effect on image uploads
Cascading protection has no effect on image uploads
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
PC Windows XP
: Normal normal with 1 vote (vote)
: ---
Assigned To: Nobody - You can work on this!
: 9687 (view as bug list)
Depends on:
  Show dependency treegraph
Reported: 2007-04-15 03:38 UTC by Casey Brown
Modified: 2007-04-27 17:48 UTC (History)
1 user (show)

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


Description Casey Brown 2007-04-15 03:38:58 UTC
The cascading protection feature has no effect on restricting image uploads to a specified filename.  
However, once the image is uploaded, cascading protection kicks in and fully protects the page.  Example 
at meta: [].
Comment 1 Majorly 2007-04-19 12:12:00 UTC
Like with permanently deleted pages, there are images which are simply
placeholders to prevent uploads.
Comment 2 Casey Brown 2007-04-20 00:26:24 UTC
meaning this []?
Comment 3 Aaron Schulz 2007-04-24 01:39:06 UTC
Note sure exactly when this was fixed, but on my test wiki and on en wikipedia I
cannot reproduce this, I get "protected page" warnings.
Comment 4 Majorly 2007-04-24 16:41:44 UTC
Yeah, it appears to work on Meta-Wiki too.
Comment 5 Casey Brown 2007-04-24 19:42:58 UTC
Seems to have been fixed then.
Comment 6 Brion Vibber 2007-04-26 19:09:01 UTC
*** Bug 9687 has been marked as a duplicate of this bug. ***
Comment 7 Mark Clements (HappyDog) 2007-04-26 23:03:50 UTC
Still seems to be a problem on  See, which should be
protected due to its inclusion on

Is this because the image is being pulled from commons?
Comment 8 David Levy 2007-04-26 23:12:09 UTC
The image isn't transcluded; it's simply linked.

Try [[Image:MediaWiki logo.png|1px]].
Comment 9 Mark Clements (HappyDog) 2007-04-26 23:14:38 UTC
It is included using standard template syntax: {{Image:MediaWiki logo.png}}
'What links here' for the image says: Project:Protected titles/list (inclusion)

That seems like it's been transcluded to me, and is exactly the same as the
other non-image pages in that list behave.
Comment 10 David Levy 2007-04-26 23:31:28 UTC
What's transcluded is the nonexistent image description page, not the image
itself.  Image transclusions are noted not on the "What links here" page, but
below the image description (under the "Links" heading).

That syntax transcludes most types of pages, but not images.  Please try the
syntax suggested above.
Comment 11 David Levy 2007-04-26 23:45:35 UTC
I just noticed that the image already is transcluded on the main page (which has
cascading protection enabled), so this shouldn't even be necessary.  What issue
are you experiencing?
Comment 12 Mark Clements (HappyDog) 2007-04-26 23:46:52 UTC
OK - well that worked, and achieves what I wanted.  However it does raise the
question as to why {{Image:foo}} doesn't protect the description page from being
edited (even if it doesn't protect against new uploads)...
Comment 13 Mark Clements (HappyDog) 2007-04-26 23:48:09 UTC
Re comment 11, I'm not sure what's going on there.  It isn't included on the
main page, and that cascade was never there before.  It appeared when I went to
check it after adding it to the protected titles list, but has now vanished
again.  Glitch?  [[MediaWiki]] hasn't been edited since january.
Comment 14 David Levy 2007-04-27 00:02:55 UTC
1. I don't know why that syntax fails to protect the image description page.  I
just know that it does.  :-)

2. I thought that I saw the image on the main page (in addition to the logo in
the upper left-hand corner).  Is it possible that someone edited one of the main
page templates to include it (and then reverted)?  Otherwise, yeah, I suppose
that it must have been a glitch.
Comment 15 Mark Clements (HappyDog) 2007-04-27 00:06:20 UTC
1.  Worth logging a separate bug for?

2. Well, I thought that might be the case, but I can't see anything in recent
changes.  Maybe that's what it was though.  Either way, it was transitory.
Comment 16 David Levy 2007-04-27 00:15:57 UTC
No, I wouldn't bother filing a bug report.  The use of cascading protection to
prevent page creation isn't an officially supported MediaWiki function; it's a
kludge that I devised.  With the existence of an alternative workaround, I see
little point in asking the developers to fix a feature that they didn't even
intend to include.  :-)
Comment 17 Aaron Schulz 2007-04-27 00:18:54 UTC
(In reply to comment #7)
> Still seems to be a problem on  See
>, which should be
> protected due to its inclusion on
> Is this because the image is being pulled from commons?

Cascading protection does not cascade accross projects.
Comment 18 Mark Clements (HappyDog) 2007-04-27 00:29:06 UTC
Interesting... I thought it was a kludge _I_ devised *grin*

Re: Comment 17, I am aware that the cascade won't protect the image on commons,
but it should stop people uploading a local version that obscures it, or from
editing the page (we get a lot of test edits all over the place on
Comment 19 Brion Vibber 2007-04-27 17:40:20 UTC
"This page has been protected from editing, because it is included in the
following page, which are protected with the "cascading" option turned on:

    * Project:Protected titles/list 

Return to MediaWiki."

If there is a problem elsewhere, please open a new bug report which is specific
to the problem experienced.
Comment 20 Mark Clements (HappyDog) 2007-04-27 17:48:39 UTC
Brion - the cascading protection works provided you link the image using
[[Image:foo]] rather than transclude it using {{Image:foo}}.  The latter does
not protect the decription page (which, imho, is a bug) or the image upload
(which is, imho again, not a problem).  As per the advice above (that this was
an 'unsupported use case' I have not logged the issue.  If you think I should
log it then let me know and I will do so.

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