Value-optional attributes

etc · 2016-09-23 19:45:51

ruud wrote #301715:

Why not $attribute = "1", to achieve better compatibility with existing plugins that do strict === comparisons?

Unfortunately, then <txp:if_variable name="test" value>... would not work, since "1"=="some value" is false, while true=="some value" is true.

Last edited by etc (2016-09-23 20:30:48)

ruud · 2016-09-24 08:38:40

etc wrote #301716:

Unfortunately, then <txp:if_variable name="test" value>... would not work, since "1"=="some value" is false, while true=="some value" is true.

But <txp:if_variable name="test"> would work and have the effect you intend while being shorter due to this bit of code:

        if (!isset($atts['value'])) {
            $x = true;
        }

etc · 2016-09-24 09:18:45

ruud wrote #301719:

But <txp:if_variable name="test"> would work and have the effect you intend

Not exactly, it would not check for value emptiness.

ruud · 2016-09-24 11:40:40

If you wanted to check for value emptyness, you’d set value="".

etc · 2016-09-24 12:45:25

ruud wrote #301726:

If you wanted to check for value emptyness, you’d set value="".

It’s checking for non-emptiness that I wanted to simplify in the OP. $value = true will match any non-empty string, while $value = "1" matches only itself.

Textpattern CMS

Textpattern CMS support forum

#25 2016-09-23 19:45:51

Re: Value-optional attributes

ruud wrote #301715:

#26 2016-09-24 08:38:40

Re: Value-optional attributes

etc wrote #301716:

#27 2016-09-24 09:18:45

Re: Value-optional attributes

ruud wrote #301719:

#28 2016-09-24 11:40:40

Re: Value-optional attributes

#29 2016-09-24 12:45:25

Re: Value-optional attributes

ruud wrote #301726:

Board footer