CPF_VALUE broken after update

Post

Posted
Rating:
#6185 (In Topic #1309)
Updated today. So far everything's still there except the little radio player. I added a CPF value to allow people to allow music from the player to be autoplay or not autoplay. The player is on the landing page. The following code worked until the update today:


<tempcode params=""><iframe height="425" src="https://www.reliastream.com/player/PaganRadio?autoplay=true" width="99%"></iframe> </tempcode>

<tempcode params=""><iframe height="425" src="https://www.reliastream.com/player/PaganRadio?autoplay=false" width="99%"></iframe> </tempcode><br />

(there is an autoplay argument in the link that indicates yes or no)

In a test, , 1}} seems now to return Yes and No, and not 1 and 0 like it used to before to update. I changed the code to try to use Yes and No, instead of 1 and 0, but it didn't work.

Any ideas folks?
 

Post

Posted
Rating:
#6189
{$CPF_VALUE,43,{$MEMBER},1} should be just {$CPF_VALUE,43,{$MEMBER}} I think.

Previously that final '1' parameter did nothing, now it flags Composr to use the rendered rather than raw value of the CPF value.

i.e. we added a new feature that by coincidence overlaps with a non-existent parameter you had been using.
1 guest and 0 members have recently viewed this.