Using let/set within namespaces

Wednesday 23 April 2003 5:17:51 am

Im trying to use some logic that sets a variable from within a section call.

{let found_something=0}

{section name=Something loop=$my_array}
{set found_something=1}
{/section}

{$found_something}

When run {$found_something} outputs '0', and I receive the error:

Warning: eZTemplate:set Apr 23 2003 13:12:37

Variable 'Something:found_something' doesn't exist, cannot set

This sounds logical since the variable is within another namespace.

If i try to specify the namespace then i receive an invalid characters error. I guess let/set dont like $ chars in there...

Can i alter a variable from one namespace from within another namespace?

This example is simplistic. My real use is more complex and requires a global variable to be changed from within multiple section calls. Is it possible to be shown an example of this working?

thanks

Paul

Wednesday 23 April 2003 5:37:55 am

Thanks Sergiy,

I had read the doco on using {let name=...} but earlier that caused problems with my three nested sections(!). But, i manged to get it working using a single namespace, though it does ruin the namespace structure somewhat...

Paul

Thursday 24 April 2003 6:25:50 am

As the template engine is today all reads are done using the root namespace of the file while writes are using the current namespace. To overcome the problems you have to move the namspace as Sergey noted.

Future versions of the template engine will probably support namespace declarations in function input variables as well as relative namespace references.

Some examples:
{set #:found_something=1}
sets the found_something variable in the root namespace
{set ..:found_something=1}
sets the found_something variable one namespace up
{$..:found_something}
Accesses the found_something variable one level up from the current namespace

Also another way to use section would help out, something like:
{section variable=i loop=$items}
{$:i.key} - {$:i.item.name}
{section variable=j loop=$:i.item.children}
{$:j.item}
{/section}
{/section}
Here the template loop variables are set as an hash array in the current namespace.

Last a new way to do if/else-if/else style checks.
{section show=eq($a,$b)}
{section-else show=eq($a,$c)}
{section-else show=eq($a,$d)}
{section-else}
{/section}

Nothing has been decided yet so please come with suggestion for things you would like to see in the template engine (not just namespaces).

--
Amos

Documentation: http://ez.no/ez_publish/documentation
FAQ: http://ez.no/ez_publish/documentation/faq

Wednesday 28 May 2003 10:33:47 am

An "explode" function would be useful - I want to split the path_string attribute on the '/' character into an array so I can easily access the node_id's of the ancestors of a particular node without having to loop up the tree. (I'm currently doing this and building a linked list of arrays within arrays, which is pretty resource intensive - and consequently a bit frustrating given that the information's already there in path_string!!)

Of course I may be missing something as I'm still very new to this! (are there any string handling functions apart from concat?) If I've missed the point, please do put me straight.

I'll post up the code I'm currently using once I'm sure it's all working. I had some trouble with namespaces, but this is now resolved thanks to Sergiy and Jan :)

Cheers
- Chris

Thursday 29 May 2003 7:49:17 am

I had the same problem Paul. Try nesting them instead:

{section show=$search_count|gt(1)}
{$search_count} things found.
{section-else}
{section show=eq($search_count, 1)}
1 thing found.
{section-else}
No things found.
{/section}
{/section}