Evo 1.04 - [*content-placeholder*] and phx: question

Hi
can’t seem to make this work:

Works like a charm in Ditto calls - eg: [+stuff+] - but it almost seems like PHX doesn’t work with content tags...?

I’ve tried this with template vars, content placeholders, and combinations thereof.
I have a phx snippet called isnotempty, which I call like:

but again it only works with Ditto calls.

so am I daft? have I missed something really bleeding obvious?

thanx for any suggestions.

-g
ps:
I thought maybe going through these contortions might help...

Notice the uncached everything, my last ditch attempt... at least it stopped showing all my ]*]] stuff. haha

have I missed something really bleeding obvious?

This justifies a basic question, I hope: Is it plugged in? (One of the two basic helpdesk questions, closely followed by "is it switched on?". These sort out an amazingly large proportion of problems.) In this context, have you installed the PHx plugin? Ditto uses its own copy of PHx, and applies it in its template chunks. If you want to use PHx on the main content areas, you need to install it as a plugin in its own right.
KP

hah!
oh thank you, I seem to have misunderstood when someone said, "you don’t need to install PHX anymore"!
They were talking about for Ditto, not for normal operations!

That’s awesome.

Thanks again
-G

Or they may have been referring to Revo, which has phx functionality built-in.

Yeah, that’s possible actually. I have to make the jump I think.

I wonder how tough it will be to move my freshly built CMS structure over to Revo...?

I see no need for it. But then I never use the phx plugin. A snippet does the job just as well without the extra weight of a plugin. As an addition to a snippet for using in the snippet’s tpl is another matter. Ditto and Jot do very well with it.

The phx plugin is buggy anyway; it eats everybody else’s placeholders. I suspect the regular expression in its garbage collection is bad but I don’t get along well enough with regex to see where the problem is. If it can detect its own placeholders to process, it should certainly be able to detect them for removal.

The phx plugin is buggy anyway; it eats everybody else’s placeholders. I suspect the regular expression in its garbage collection is bad but I don’t get along well enough with regex to see where the problem is. If it can detect its own placeholders to process, it should certainly be able to detect them for removal.

i stopped using PHX outside of Ditto & MaxiGallery, too, but as far as i remember, there’s an updated version floating around somewhere ...i’ll search for it later