Last modified: 2011-01-25 01:31:09 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 T19307, 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 17307 - Remove {{DISPLAYTITLE:}} restrictions for wm2009wiki
Remove {{DISPLAYTITLE:}} restrictions for wm2009wiki
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Site requests (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Rob Halsell
http://wikimania2009.wikimedia.org/wi...
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2009-02-01 19:26 UTC by Casey Brown
Modified: 2011-01-25 01:31 UTC (History)
1 user (show)

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

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

Description Casey Brown 2009-02-01 19:26:11 UTC 
Would it be possible to remove the restrictions for {{DISPLAYTITLE:}} on the Wikimania 2009 site?  If not, could at least lessen them a bit so we can get the page's <h1> to change name instead of just capitalization? :-)
Comment 1 Brion Vibber 2009-02-24 21:13:33 UTC 
This'd be setting $wgRestrictDisplayTitle to false... Rob, can we give this one a whirl on this wiki and see what it breaks? ;)
Comment 2 Rob Halsell 2009-02-26 18:04:22 UTC 
This has been completed and pushed live.  If there are any questions or concerns, please do not hesitate to let me know.
Comment 3 Casey Brown 2009-02-28 03:15:22 UTC 
This doesn't seem to be working for me, but I could be doing it wrong: http://wikimania2009.wikimedia.org/wiki/?diff=3590
Comment 4 Rob Halsell 2009-03-02 15:56:57 UTC 
Brion,

This change was pushed, but Casey reports an issue.  Please advise.
Comment 5 Brion Vibber 2009-03-05 01:16:03 UTC 
Need to use literal true and false, not strings. 'false' evaluates to true. :)
Comment 6 Rob Halsell 2009-03-05 16:40:40 UTC 
Ok, I set this correctly now and deployed.  It should be working as expected.
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