@KK, there are some tag calls around which do execute tags directly via $TAGS object - some in the core code, which is okay, some in custom code that raises up my concern. Events are not fired in such calls and therefore anything that is triggered by alter_tag_xxx_execute or tag_xxx_executed is skipped.
I want to write a wrapper for the tag <cms:addslashes> - <cms:add_slashes) (I spoke about it in the recent topic).
If I go like this I lose my mod - extended functionality of addslashes (particularly ability to escape a comma (\,))
Here are my options:
#1 Use couch code, parse it with parser and embed as code.
#2 Dispatch events myself in the function my_new_tag_add_slashes().
What is the best way to address the problem? Are there any other better ways to run original tag?
I want to write a wrapper for the tag <cms:addslashes> - <cms:add_slashes) (I spoke about it in the recent topic).
If I go like this I lose my mod - extended functionality of addslashes (particularly ability to escape a comma (\,))
- Code: Select all
$FUNCS->register_tag( 'add_slashes', 'my_new_tag_add_slashes' );
function my_new_tag_add_slashes( $params, $node ){
global $TAGS;
return $TAGS->addslashes( $params, $node );
}
Here are my options:
#1 Use couch code, parse it with parser and embed as code.
#2 Dispatch events myself in the function my_new_tag_add_slashes().
What is the best way to address the problem? Are there any other better ways to run original tag?