Last modified: 2011-06-28 05:52:35 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 T31619, 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 29619 - Magic words and substitution don't function properly in WikiLove preview
Magic words and substitution don't function properly in WikiLove preview
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
WikiLove (Other open bugs)
unspecified
All All
: Unprioritized normal (vote)
: ---
Assigned To: Ryan Kaldari
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2011-06-28 03:03 UTC by MZMcBride
Modified: 2011-06-28 05:52 UTC (History)
0 users

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

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

Description MZMcBride 2011-06-28 03:03:31 UTC 
Running r90927 of trunk and WikiLove, when a user goes to put in "{{FULLPAGENAME}}" or "{{subst:BASEPAGENAME}}" or some combination of magic like this, the preview renders the result of such magic as "API".

After the WikiLove message is submitted, the expected behavior occurs (the text is substituted and/or the variable is appropriately rendered). It appears to only break during preview.
Comment 1 Ryan Kaldari 2011-06-28 05:30:11 UTC 
WikiLove is using the API to do the parsing:
api.php?action=parse&text=blahblah&prop=text&pst=true

Could be an API bug, or we're not calling it correctly.
Comment 2 Ryan Kaldari 2011-06-28 05:43:44 UTC 
It looks like most magic words work fine, for example {{CURRENTYEAR}}. Apparently the parser can't deal with {{FULLPAGENAME}} or {{BASEPAGENAME}} since it's not actually being called from a page, it's being called from the API. Just need to have the AJAX call include a title parameter for the page and that should fix it...
Comment 3 Ryan Kaldari 2011-06-28 05:52:35 UTC 
Fixed in r90940.
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