Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#13 2014-01-07 20:30:49

gaekwad
Server grease monkey
From: People's Republic of Cornwall
Registered: 2005-11-19
Posts: 4,137
GitHub

Re: [solved] Parsing interleaved tags

Steve, Uli and Oleg – thank you very much for your input. This has been a really useful thread.

The crux of the issue seems to be that the unmatched tag is dropped, which makes sense when I think about it, but I hadn’t even thought of that.

The reasoning behind the if_plugin tag was to make it optional, and short of reengineering my form and page structures, I could just remove the if_plugin tags and make the plugin required. The pragmatic approach, if a little less elegant, will do just fine for now.

And who bet money on etc_query being able to solve the problem? Every. Single. Time.

Last edited by gaekwad (2014-01-07 21:53:15)

Offline

#14 2014-01-07 21:50:29

etc
Developer
Registered: 2010-11-11
Posts: 5,053
Website GitHub

Re: [solved] Parsing interleaved tags

I was partly wrong here, corrected now.

Offline

#15 2014-01-07 22:07:02

etc
Developer
Registered: 2010-11-11
Posts: 5,053
Website GitHub

Re: [solved] Parsing interleaved tags

gaekwad wrote #277893:

And who bet money on etc_query being able to solve the problem? Every. Single. Time.

You ‘ve lost could have won :P

<txp:etc_query data='<txp:if_plugin name="rah_replace">1</txp:if_plugin>' parse="">{%<}txp:rah_replace from="	,
" to=""></txp:etc_query>
...exciting stuff...
<txp:etc_query data='<txp:if_plugin name="rah_replace">1</txp:if_plugin>' parse="">{%<}/txp:rah_replace></txp:etc_query>

Last edited by etc (2014-01-08 14:52:07)

Offline

Board footer

Powered by FluxBB