Forums / Setup & design / Warning : Variable 'nodeContent' is already defined.

"Please Note:
  • At the specific request of Ibexa we are changing this projects name to "Exponential" or "Exponential (CMS)" effective as of August, 11th 2025.
  • This project is not associated with the original eZ Publish software or its original developer, eZ Systems or Ibexa".

Warning : Variable 'nodeContent' is already defined.

« 
Previous topic
|
Setup & design
|
Next topic
 »
Author Message

H-Works Agency

Sunday 27 November 2005 4:22:02 pm

I have this warning but its not mentionned anywhere on the site.

What is this ? What do i need to fix ?

Debian/EZP7.2/Apache2/Php4

Thanx
Martin

EZP is Great

Nathan Kelly

Sunday 27 November 2005 7:33:46 pm

Hi Martin, where does this error occur? If it is occurring in a template you have edited/created it may help if we can see your code.

I'd say you may be trying to define a variable that you have already defined in previous code, or you may not have un-defined a variable with {undef $myvariable} where you may have needed too?

Cheers!

Pardon me while I burst into flames...

H-Works Agency

Tuesday 29 November 2005 7:49:04 am

Hi Nathan

This Warning occurs on the admin interface :

Warning: eZTemplate:def  	Nov 29 2005 16:43:15

Variable 'nodeContent' is already defined.

This is the only place where a '$nodeContent' var is present :

design/admin/templates/children_list.tpl:       {def $nodeContent=fetch( 'content', 'object', hash( 'object_id', $Nodes.item.contentobject_id ) )}

But i never modified this template so how this warning is happening ?

There is another thing but this time its an 'error' happening on the site part :

Error: eZTemplate:elementValue  	Nov 29 2005 16:42:39

Missing array data structure, got NULL

Martin

EZP is Great

Nathan Kelly

Tuesday 29 November 2005 6:36:21 pm

Hi Martin, this may be a 3.7.2 issue, unfortunately I'm using 3.6.0 so I don't know what has explicitly changed between the versions (I assume some templates have been updated). I've never seen these errors on 3.6.0, so I can't help, sorry.

Maybe someone else will have an idea?

Cheers!

Pardon me while I burst into flames...