Problem with conditions (nested modifiers)

Hey all,
I’m playing with Revo and at the moment I’m stuck on PHx -> Filters/Modifiers step.
I have this code in my template:

And:

First one gives me errors and headache. It displays description but always with `]] at the end of output. Looks like it just don’t work.
Second example works fine.

Is it that Revo filters doesn’t support multi-level conditions? Nested on in another?

It might work if you put it all on one line, but conditional modifiers, especially complex ones, are very slow and inefficient. I would use a snippet. Something like this:

Quote from: BobRay at Apr 21, 2011, 01:04 AM

It might work if you put it all on one line, but conditional modifiers, especially complex ones, are very slow and inefficient. I would use a snippet.

Thank you for reply, BobRay.
I’ve already tried one line option and it didn’t work.
I’m very used to PHx conditional modifiers wich worked perfectly on Evo. Now I found this basic technic to be problematic in Revolution. Maybe it is slow and inefficient but I have never experienced that when using it in Evolution. They aren’t that complex and writting snippets for every conditional part is not an option for me.

Quote from: BobRay at Apr 21, 2011, 01:04 AM

It might work if you put it all on one line, but conditional modifiers, especially complex ones, are very slow and inefficient. I would use a snippet. Something like this:

isn’t the slowness only relevant if the page is fully dynamic? e.g. if its cached it shouldn’t matter since its rendered once no?

thanks for the input..

Quote from: krisj at May 10, 2011, 02:26 PM

isn’t the slowness only relevant if the page is fully dynamic? e.g. if its cached it shouldn’t matter since its rendered once no?

Exactly, once cached it’s fast as typical static (MODX) content.

Yes, but every time you clear the site cache (which happens a lot for me) the first visitor will have to wait.

which should be redesigned by the way! what about high traffic sites? we should be able to selectively clear the cache of individual resources (and their dependent elements). which brings us into another topic altogether

Quote from: krisj at May 10, 2011, 05:10 PM

we should be able to selectively clear the cache of individual resources (and their dependent elements).

And thats a realy nice idea. Sounds like a perfect solutions to me.