Note: many special pages do their own parsing of the input and some of them allow multiple parameters. Would be nice to standardize the syntax. Not sure how to do it in bc way though.

• Bug 23150 has been marked as a duplicate of this bug. ***

happy.melon.wiki wrote:

The issue is that most special pages take most of their parameters from the URL GET request using $wgRequest->getVal(). One parameter is extracted from the subpage of the page title, so that's easy to achieve in transclusion, but the problem with the other parameters is that you have not only to pass them through, but also to make the execute() method actually *use* them.

(Edit conflict :))
I'm assigning this bug to myself. Fixing it consists of two parts:

1. Making the parser pass on an array of already-parsed arguments
2. Make every single includable special page accept and use those parameters (beside $wgRequest)

Okay, problem 1. is solved (just want to make sure no one else wastes hours on that :))

Parser passes on an associative array which contains the parameters.

Okay, fixed it. Thanks to Happy-melon, he figured out how to turn the DOM tree into an associative array. The rest is also fairly simple and short, even though it's not the nicest thing to fake $wgRequest (but then again, the code is only as bad as the surrounding code).
I'll commit it after some more tests and in case no one complains here.

attachment patch ignored as obsolete

Small fix

removed some debugging code.

Comment from some devs at !wmcon: Nasty way of doing this, but there doesn't seem to be an easy & nice sollution.

Attached:

Fixed in r93758.

reachouttothetruth wrote:

*** Bug 2447 has been marked as a duplicate of this bug. ***