Last modified: 2011-03-08 14:29:25 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 5880 - Allow magic words in EasyTimeline
Allow magic words in EasyTimeline
Status: RESOLVED FIXED
Product: MediaWiki extensions
Classification: Unclassified
EasyTimeline (Other open bugs)
unspecified
All All
: Normal enhancement with 1 vote (vote)
: ---
Assigned To: Erik Zachte
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-05-09 07:01 UTC by Ral315
Modified: 2011-03-08 14:29 UTC (History)
2 users (show)

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


Attachments

Description Ral315 2006-05-09 07:01:17 UTC
Not sure on the feasibility of this, but it would be useful to be able to use
magic words inside EasyTimeline, in order to be able to parse things such as
{{CURRENTDAY}}, {{PAGENAME}}, etc.  This could be done just through parsing
Define statements for Wikisyntax, forcing everything to be done through
variables, or done fully.
Comment 1 Phil Boswell 2006-05-09 13:03:46 UTC
I suspect that this is the same situation as prevents transclusional parameters 
from being used in an EasyTimeline: the order of parsing/evaluation doesn't 
support such a thing.

So the raw text gets passed to EasyTimeline which naturally barfs...
Comment 2 Ral315 2006-05-10 19:17:01 UTC
My thought was that it might be possible to change the EasyTimeline parsing
order to where it's handled separately from the rest of the parsing.
Comment 3 Mollerup-no 2008-02-23 10:44:55 UTC
I was about to enter a new bug, but maybe I can just comment on this. For at least four months and at least up until Feb 23 2008 08:59 CET, I was able to use the following Template using parsing to create a timeline figure on nowiki: http://no.wikipedia.org/wiki/Mal:Navnefigur

To make the parsing work, the template had to be put in using "subst:", so no pages actually use this template dynamically. The last successful use of the template is seen here: http://no.wikipedia.org/w/index.php?title=Mats&diff=prev&oldid=3372588 (Due to the subst, you just see the result of the template.)

At least from Feb 24, 2008, 14:00 CET it was no longer possible to use this template, as the parameters were not parsed, so the result looks like this (only one of the erroneous lines extracted):
Line 12: bar:1700 from:{{{1}}} till:end shift:(-80,20)

As you see instead of parsing the first parameter, the text {{{1}}} is used directly.

Is it possible to find out why the parsing no longer works? And maybe also to fix the problem? :-)

Comment 4 Splarka 2008-02-23 11:12:30 UTC
The parsing probably no longer works as Wikimedia was switched to the new preprocessor about then: http://meta.wikimedia.org/wiki/Migration_to_the_new_preprocessor

You can probably use the new parserfunction (not part of the ParserFunctions extension, but core) called #tag (which turns any XML-style extension tag into a parserfunction, which does allow preprocessing of parameters, magicwords, parserfunctions, templates, etc), see 
http://meta.wikimedia.org/wiki/Help:Magic_words#Formatting for more info.
Comment 5 Mollerup-no 2008-02-24 12:39:08 UTC
Thank you, this solved the issue! Also, using the #tag function made the use of the Template much better than before, since there is no longer a need to use "subst:". Again, thank you for the info!
Comment 6 Siebrand Mazeland 2008-08-13 11:49:25 UTC
Assigned to extension developer.
Comment 7 Bergi 2011-03-08 14:29:25 UTC
The #tag-function should have solved this issue.

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


Navigation
Links