Last modified: 2010-05-15 16:03:11 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 13768 - api prop=info doesn't show create protection
api prop=info doesn't show create protection
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
API (Other open bugs)
1.13.x
All All
: Normal enhancement (vote)
: ---
Assigned To: Roan Kattouw
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2008-04-16 20:16 UTC by CBM
Modified: 2010-05-15 16:03 UTC (History)
2 users (show)

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


Attachments

Description CBM 2008-04-16 20:16:45 UTC
The prop=info query with inprop=protection doesn't indicate when a page is protected from creation. This query

http://en.wikipedia.org/w/api.php?action=query&prop=info&inprop=protection&titles=Real_social_dynamics

gives

<?xml version="1.0" encoding="utf-8"?>
<api>
  <query>
    <normalized>
      <n from="Real_social_dynamics" to="Real social dynamics" />
    </normalized>
    <pages>
      <page ns="0" title="Real social dynamics" missing="">
        <protection />
      </page>
    </pages>
  </query>
</api>

but the page is currently protected from creation.
Comment 1 Roan Kattouw 2008-04-17 12:59:11 UTC
http://en.wikipedia.org/w/api.php?action=query&prop=info&inprop=protection&titles=Real_Social_Dynamics

does give the right results. Create protection affects all case variants because the pt_title field is case-insensitive. Fixed in r33473.
Comment 2 Brion Vibber 2008-04-17 19:13:01 UTC
Reverted r33473 and added a proper fix for the field's encoding in r33508. pt_title is now properly case-sensitive, matching the behavior of all other title fields.

If the field were meant to be case insensitive, it wouldn't work correctly as previously written!

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


Navigation
Links