Last modified: 2012-08-14 11:42:39 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 8828 - Parameters are not passed to hooks
Parameters are not passed to hooks
Status: RESOLVED DUPLICATE of bug 2257
Product: MediaWiki
Classification: Unclassified
Templates (Other open bugs)
All All
: Normal normal (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: 8802
  Show dependency treegraph
Reported: 2007-01-30 09:43 UTC by Emilien ARNAUD
Modified: 2012-08-14 11:42 UTC (History)
1 user (show)

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

Activate parameters in hook functions (420 bytes, patch)
2007-01-30 10:04 UTC, Emilien ARNAUD

Description Emilien ARNAUD 2007-01-30 09:43:21 UTC
Because of striping the parameters are not passed to hooks located in templates.

I mean you cannot use <myhook param="{{{paramPassedToTemplate}}}">...</myhook>

I made a very little change to that: include a unstrip function on each end od
parse of a template...

Does it have side effects ? The parsing flowchart is really hard to understand,
and I hope I broke nothing...


P.S.: I would attach a patch helping you to see what I changed...
Comment 1 Emilien ARNAUD 2007-01-30 10:04:20 UTC
Created attachment 3161 [details]
Activate parameters in hook functions

The patch
Comment 2 Aryeh Gregor (not reading bugmail, please e-mail directly) 2007-01-30 16:41:21 UTC

*** This bug has been marked as a duplicate of 2257 ***

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