update to 3.2.13, compiled template defect about smarty HOT 8 CLOSED

must have been 3.1.23 not 3.2.13 :-)

from smarty.

I can't reproduce your problem.

it does compile to

from smarty.

the example ist part of a longer template. Is there any reason where smarty can forget to escape the variable name? eg. [sid] instead of ['sid']

from smarty.

It looks like that sid is a defined constant.
A couple of versions ago the use of costanstants by their name was introduced.
However it did not work in all places.
It was fixed that a constant can now be used also as array index.
Maybe this is now the problem in your application.

from smarty.

I've that same problem in 3.1.24.
Something is wrong with this "sid"

When i try to use $smarty.get.params.sid, variable is null, but $smarty.get.params['sid'] is ok

from smarty.

Once again. I you have somewhere in your application sid defined as a constant. Support of constants was added to Smarty a couple of versions ago. In $smarty.get.params.sid will then not be interpreted as string array index, but the value of the constant will betaken. It' a naming conflict you must either rename the constant or use an other array index, So it's not a bug.

from smarty.

It turned out that SID is a constant created by session_start()

from smarty.

Hi Uwe,

it's quite awkward to prohibit an usecase that's supported by php. Is there any configuration option to disable this "feature"? Why was it introduced? There was already the possibility to use constants by $smarty.const.foo

Sincerely yours

Hasan

from smarty.