Go to main content

Textpattern CMS support forum

You are not logged in. Register | Login | Help

#13 2015-06-25 09:45:20

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 11,250
Website GitHub

Re: [Answered] if_plugin conditionnal wrapping

etc wrote #292042:

If stored as you suggest, it will always be parsed.

Gotcha. Dumbass oversight on my behalf.

As you were.


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#14 2015-06-25 09:47:24

Bloke
Developer
From: Leeds, UK
Registered: 2006-01-29
Posts: 11,250
Website GitHub

Re: [Answered] if_plugin conditionnal wrapping

etc wrote #292048:

If <txp:variable /> had parse attribute

If that’s something that would be useful in situations like this, then I’m up for it even if it is an advanced performance tweak. Wanna propose a patch and we’ll see how it flies? If parse="1" was default, nobody would be any wiser :-)

I’m sure there have been one or two times in the past I’ve wanted to defer variable parsing until later (injecting into smd_query or <txp:yield /> blocks, for example).


The smd plugin menagerie — for when you need one more gribble of power from Textpattern. Bleeding-edge code available on GitHub.

Txp Builders – finely-crafted code, design and Txp

Offline

#15 2015-06-25 10:12:32

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

Re: [Answered] if_plugin conditionnal wrapping

That’s easy to do, but I don’t know how it goes security-wise… It would mean the possibility to inject (willingly or not) not parsed content, could it be harmful?

Re processing deferring, I vaguely see something that could be done, but it’s a bit raw atm.

Offline

Board footer

Powered by FluxBB