2009/8/5 Brion Vibber br...@wikimedia.org:
Looks normal. Since your tag is opaque, the preparser can't descend into
its contents for additional parsing.
I'm not sure offhand whether we have appropriate interfaces already for
declaring a tag hook at setup time as containing wikitext.
To
On Sat, Aug 08, 2009 at 01:03:35PM +0200, Roan Kattouw wrote:
2009/8/5 Brion Vibber br...@wikimedia.org:
Looks normal. Since your tag is opaque, the preparser can't descend into
its contents for additional parsing.
I'm not sure offhand whether we have appropriate interfaces already for
2009/8/8 Alex Bernier alex.bern...@free.fr:
Is it possible to call the preprocessor in the foo handler ?
Indirectly, that's what's already happening, but in a later stage. The
sequence of events is:
1. Preprocessor recognizes fooblahbarblah/barblah/foo as an
extension tag foo with content
On Wed, Aug 5, 2009 at 9:20 AM, Alex Bernieralex.bern...@free.fr wrote:
Hello,
I have what I think is strange behaviour with parser called by the API
and tag extensions.
snip/
A little bit of debug show that the includes/parser/Parser.php, the
extensionSubstitution function is only called
Hello,
I have what I think is strange behaviour with parser called by the API
and tag extensions.
Here is the code of a tag extension :
function efParserInit() {
global $wgParser;
$wgParser-setHook( 'foo', 'effooRender' );
$wgParser-setHook( 'bar', 'efbarRender' );
return
On 8/5/09 1:20 AM, Alex Bernier wrote:
function efParserInit() {
global $wgParser;
$wgParser-setHook( 'foo', 'effooRender' );
$wgParser-setHook( 'bar', 'efbarRender' );
return true;
}
[snip]
I crate a page on my Wiki with the following text :
