mtype for attributes?

Is it possible to have an attribute displayed only if the field inside of it is merged successfully? Perhpas something similar to magnet and mtype only for attributes?

I have an array that looks something like this:


I'd like to merge a block with this array and have an attribute (for instance "class") set on any of the products that have the "in_cart" key set to 1 (I can change the array to set the "in_cart" value to '0' if necessary).

Perhaps something like this:


I think I'm off on a few things. Just wondering if something like this would be possible.

Thanks.

Hi,

This should work:

Note: parameter 'when' is only for [onload] or [onshow] blocks (TBS 2.0 and 2.01).

Thanks, Skrol29, as always.

So, one can use any field params on a block field? That makes since. Sorry I didn't research it more.

Would you ever consider changing the mtype/magnet params to include one for attributes? That would keep the XHTML valid.

The code could looks something like:

In the example above the "magnet" parameter is probably not needed since it would be redundant next to the "mtype=attribute" parameter.

Just an idea.

That's not a bad idea. Making valid XHTML templates is nice.
I will see if it's easy to do.
Founding the attribute before seems easy, but the pair of double quote is maybe more difficulte as it seems.

Skrol29,

I haven't studied out how TBS does its parsing, but would it not be possible to look for the first space to the left and either the first space or first ">" to the right? That might avoid the double quote problem altogether.

You would know better of course.

Thanks for considering the idea, Skrol29.

  > the first space to the left
And what if the man code it (att = "value") with spaces?

  >first space or first ">" to the right?
And what if the man code it with other attributes after this one?

It looks like possible but not such simple.
I'll study this because the feature is nicelly interesting.

have you considered implementing this feature or not ?
may i help ?

By the way, while attempting the solution you propose, i got some weird behaviour (i guess it is normal, but not very clearly documented in the manual ?)


where for example
and
this works !
but is unexpected,
and in contradiction with the semantics of
i got the point : being able to access the field array so we can make tests on other columns.
in this case, this should be DOCUMENTED SOMEWHERE. Or i missed it ?

hope this helps improvement

oops
sorry it doesn't work at all.

i don't get it, something doesn't work with array fields

Hi,

Yes it can be implemented and probably will.
I've coded a function for the Excel plug-in which can read XML attributes of any tag.
This function can now be inserted into the HTML plug-in in order to provide your feature easily. The best way is to give it via parameter "ope". This parameter is to be preferred for parameter enhancement via plug-ins.

I cannot tell when I will do it because I have to do another plug-in before (not big).

I was suprised it could work. [val] is just a keyword for TBS (event if its separators change with TBS tag separators).

[var.pagenext;if [val]!='';then 'tata']

where $pagenext = "toto";

this doesn't outputs tata

any clue ? i guess it's my syntax ?

thanks for your help

> [var.pagenext;if [val]!='';then 'tata']

Are you sure that $pagenext is set before this TBS tag is processed ?

this is not my day...
it works, BUT in my case it doesn't work :
in html :


in php :
// this echoes 'index.php?ua=oml&pg=4'
// this echoes 'tata'

first case is not desired !

if i don't put equal (=) chars in my string it works...

Before TBS 3.0, default value for parameter "esle" is '' (empty string).
I know this looks strange, but it used to had a sens in TBS 1.x.
  :/
The behavior in not the same in TBS 3.0.

You should code:

that's the right syntax for me :

[var.pagenext;if [val]='';then '';else nexthref="[val]"]

change anything and it doesn't work...

You last snippet works fine for me. With both TBS 3.0 and 2.05.