Tim Lucas wrote:
Only problem though is that some publishing rules output directly, and so you can't just check request.aInvocations.
If you find a rule that outputs directly, reoprt the bug. No publishing rule should output directly for exactly these sorts of reasons. Those that do are in need of revision.
Normally you could check the length of generatedcontent at the end of the tag, but the container tag hasn't been designed with start/end in mind (and neither have any templates).
What I suggest is that I add the start/end functionality to the tag, so for those who use <con:container .../> in their templates they get the new functionality, and those who use <con:container ...> don't notice any difference.
All custom tags execute twice.. once in start and once in end mode -- regardless of how they are implemented. It's just a case of putting in a switch to act accordingly.
But in any event, the containers were *designed* to accommodate text blobs and object calls. There really shouldn't be any reason at all why everything can't just be put in aInvocations and rendered. Those rules that output direct to the HTML stream are not adhering to the API and should be changed.
-- geoff http://www.daemon.com.au/
--- You are currently subscribed to farcry-dev as: [EMAIL PROTECTED] To unsubscribe send a blank email to [EMAIL PROTECTED]
MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia http://www.mxdu.com/ + 24-25 February, 2004
