Big problem with scope variables

[yourchoice]

I declared {$NO_ADS=1 scope='global'} in file header.tpl.

Then in main page (main.tpl) I try to use this variable and seems to not be recognized.

This happen with the last version ....30/37

[uwetews]

Read the newfeatures.txt regarding the bubble_up option flag.

{$NO_ADS=1 scope='global', bubble_up}

[yourchoice]

Why was necesary this option bubble_up ?

[ophian]

Read the newfeatures.txt regarding the bubble_up option flag. {$NO_ADS=1 scope='global', bubble_up}

Hm, strange use of parameter quoting... The new feature docu says it is: {$foo = 'bar' scope=global bubble_up} without any quotes and comma, but shouldn't it be {$foo = 'bar' scope='global, bubble_up'} in real or anything like it? @uwetews

[ophian]

@uwetews ? (see above)

[yourchoice]

so, the correct sintax is

1. {$NO_ADS=1 scope='global', bubble_up} ? Here is a comma that not appear in NEW_FEATURES.txt

2. {$NO_ADS=1 scope='global' bubble_up}

3. {$NO_ADS=1 scope='global bubble_up'}

For me 2) working ...

I think this feature need better documented ...

[uwetews]

Sorry, for the compiler attribute=string is identical to attribute='string'
I should not have use this syntax option in my example.
bubble_up is a tag option flag which are never quoted. (like nocache)

I updated NEW_FEATURES.txt

[uwetews]

The master branch has been updated once again regarding scope handling.
The bubble_up option flag has been removed and variable changes are bubbled_up to the current template by default because this does make sense.

read the NEW_FEATURES.txt for the latest comments.