letset and section-else changes in 3.6

Previous topic

Setup & design

Next topic

Author	Message
James Ward	Friday 17 June 2005 8:45:56 pm Is it just me or was there major changes to the way ezpublish handles letset statements and sections in 3.6? I upgraded a 3.5.1 site to 3.6 and found lots of broken code due to sets without matching lets and section-elses that now seem to require two /sections at the end. Is there a note about this in the changelog somewhere? I'd like to get a better idea on what else may be broken if I upgrade more sites. working at www.wardnet.com blogging at www.jamesward.ca
James Ward	Friday 17 June 2005 9:21:53 pm Ok both problems seem to come from the same place. An unterminated let statement inside a section statement will cause the section-else to run everytime in ez3.6. I'll be adding this as a bug. Simple code to test: {section show=eq(1,1)} section {let test=1} {section-else} section-else {/section} Will output section section-else working at www.wardnet.com blogging at www.jamesward.ca

Author

Message

James Ward

Friday 17 June 2005 8:45:56 pm

Is it just me or was there major changes to the way ezpublish handles letset statements and sections in 3.6?

I upgraded a 3.5.1 site to 3.6 and found lots of broken code due to sets without matching lets and section-elses that now seem to require two /sections at the end. Is there a note about this in the changelog somewhere? I'd like to get a better idea on what else may be broken if I upgrade more sites.

working at www.wardnet.com
blogging at www.jamesward.ca

James Ward

Friday 17 June 2005 9:21:53 pm

Ok both problems seem to come from the same place. An unterminated let statement inside a section statement will cause the section-else to run everytime in ez3.6. I'll be adding this as a bug.

Simple code to test:

{section show=eq(1,1)}
 section
 {let test=1}  
{section-else}
 section-else
{/section}

Will output section section-else

working at www.wardnet.com
blogging at www.jamesward.ca