Last modified: 2011-03-13 18:05: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 T22199, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 20199 - ParserFunctions blocks display of page content
ParserFunctions blocks display of page content
Status: RESOLVED WONTFIX
Product: MediaWiki extensions
Classification: Unclassified
ParserFunctions (Other open bugs)
unspecified
All All
: Lowest normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-08-12 21:03 UTC by ZRHwiki
Modified: 2011-03-13 18:05 UTC (History)
0 users

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


Attachments

Description ZRHwiki 2009-08-12 21:03:17 UTC
Since I updated my MediaWiki installation to the latest MW version via SVN, pages that use the ParserFunctions extension don't contain any content, there're virtually empty.

Deactivating the ParserFunctions extensions solves the problem, i.e. the page content is shown including the part of the source thought to be parsed by the ParserFunctions extensions.

An update to the latest ParserFunctions version via SVN didn't solve the problem.

Versions in use:

MediaWiki 1.16alpha #54887
ParserFunctions 1.1.1 #54888

Example page in my wiki: 

http://www.zrhwiki.ch/wiki/Lufthansa?useskin=monobook
Comment 1 ZRHwiki 2009-08-12 21:54:43 UTC
I'm going to roll back my MW installation in order to temporarily resolve this problem. I've therefore created screenshots for your information:

http://www.zrhwiki.ch/tmp/zrhwiki_parserfunctionsON_001.png (no content)
http://www.zrhwiki.ch/tmp/zrhwiki_parserfunctionsOFF_001.png (content including template source)

Comment 2 ZRHwiki 2009-08-23 18:58:59 UTC
I've just noticed that the above-described bug only occurs if the respective page contains category information (i.e. [[TEST:Lorem ipsum]] AFTER the ParserFunctions extension is used. If the respective doesn't contain category information or the category information is located BEFORE the ParserFunctions extension is used, the problem doesn't occur.
Comment 3 ZRHwiki 2009-08-23 19:59:20 UTC
I've been able to solve the above-described bug by splitting the templates using the ParserFunctions extensions, i.e. instead of using one pretty long template for various purposes and with any IFs, I use now multiple single purpose templates. Maybe the ParserFuctions extension was just overextended …

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


Navigation
Links