Lots of 'sections' and html whitespace

Friday 20 February 2004 4:17:00 am

Im adding logic to my templates for some situations, and when i look at the html source im finding it to contain lots of extra whitespace, which i believe are due to the many section/section-else statements. I've removed any tabs i have and the only whitespace remaining are normal spaces and new lines.

After removing such whitespace (making a huge single line) the html produced is what i expect.

So, is there a way to eliminate the indentions caused by logic code through the changing of a template? From the cause/effect experiments i've tried this seems to a lib/kernel issue.

Paul

Friday 20 February 2004 7:09:06 am

Pasted here from:

http://ez.no/community/bug_reports/template_logic_code_shouldn_t_produce_whitespace

to use the code tag!

            {section var=menu loop=$mainMenu}
                {section show=eq($menu.item.id, $menu_home_node)}
                     {set menu_url_alias="/"}
                {section-else}
                     {set menu_url_alias=$menu.item.url_alias}
                {/section}
                {section show=$menu.item.is_selected}
                    {* Only show the selection image if the current node is the same as the menu item *}
                    {section show=eq($node_id,$menu.item.id)}
                        {* If the current node is the last selection show the border *}
                        {section show=eq($menu.item.id,$last_selected_node)}
<li class="menu_link_level_{$menu.item.level}_selected"><a href={$menu_url_alias|ezurl}>{$menu.item.menu_name}</a></li>

Saturday 08 September 2007 5:25:55 am

Hi, I'm having the same problem, has anyone found a solution to this issue?
Unless I don't indent the code in the templates, the html source contains empty lines and spaces.

Thanks in advance.

Monday 10 September 2007 12:43:41 am

Thank you for your reply.
I tried to enable / disable the UseFormatting setting, but it doesn't seem to do the trick. Well, I should say, I don't see any difference in the html source.
(The setting TemplateCompile is enabled though.)

When I first changed the UseFormatting setting, ezP generated bad code in the compiled templates. (I'm using ezP 3.9.2)

I got an unexpected T_String error, so I had to look into the compiled templates.

The content of $variableNameText in line 2698 of /lib/eztemplate/classes/eztemplatecompiler.php contains double quotes, resulting in something like this:

$tpl->warning("Variable "testvar" is already define.");

The original code of eztemplatecompiler.php

$php->addCodePiece( "    \$tpl->warning( '" . EZ_TEMPLATE_DEF_FUNCTION_NAME . "', \"Variable $variableNameText is already defined.\" );\n" );

I used a quick fix to replace double quotes by single quotes, to prevent this

$php->addCodePiece( "    \$tpl->warning( '" . EZ_TEMPLATE_DEF_FUNCTION_NAME . "', \"Variable ".str_replace("\"", "'", $variableNameText)." is already defined.\" );\n" );

Now the generated code should look like this:

$tpl->warning("Variable 'testvar' is already define.");

Not sure why this bug suddenly appeared when changing the UseFormatting setting, but anyway, with this fixed, I'm still having empty lines and whitespace in the html source.
Is there something else other than TemplateCompile that could have effect on UseFormatting?