Last modified: 2014-03-13 16:39:37 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 T39068, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 37068 - Parser functions do not work in RSS template
Parser functions do not work in RSS template
Status: ASSIGNED
Product: MediaWiki extensions
Classification: Unclassified
RSS (Other open bugs)
unspecified
All All
: High normal with 1 vote (vote)
: ---
Assigned To: T. Gries
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-05-24 05:35 UTC by T. Gries
Modified: 2014-03-13 16:39 UTC (History)
4 users (show)

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


Attachments

Description T. Gries 2012-05-24 05:35:09 UTC
Reported in https://www.mediawiki.org/w/index.php?title=Extension_talk:RSS&offset=20120524012622&lqt_mustshow=15624#x.23sub_ParserFunction_doesn.27t_work_anymore_15114 

I used this snippet to trim/strip long title segments in the RSSPost-Template:

{{#sub:{{{title}}}|0|60}}}}

But after updating from version 1.9 to 2.16 20120424 it doesn't work anymore. The parser function is not applied to the title. I already switched to the new template name etc. Therefore I can't use the latest version in my production environemnt, because the long title will destroy my layout respectively my main page.
Comment 1 T. Gries 2012-05-24 05:50:20 UTC
This may be indeed a regresssion caused by one of the latest changes. I'll try to fix this with some priority.
Comment 2 Andre Klapper 2014-03-13 16:39:37 UTC
T. Gries: You assigned this issue to yourself two years ago.
Could you please provide a status update and inform us whether you are still working (or still plan to work) on this issue? 
Only in case you do not plan to work on this issue anymore, should the assignee be set back to default and the bug status changed from ASSIGNED to NEW/UNCONFIRMED? Thanks.

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


Navigation
Links