CMS Made Simple Forums

Posted: **Thu Oct 13, 2016 1:34 pm**

I have a template that outputs text or HTML based on a query parameter. This works well in 2.1.4 (and a few versions below), but fails with the following error ins 2.1.5

Syntax error in template "tpl_top:36" on line 9 "" unclosed {else} tag

The simplified template code is as follows:

Code: Select all

{content assign="my_content" wysiwyg="false"}
{strip}
  {process_pagedata}
{/strip}
{if isset($smarty.get.text)}
  This is plain text
{else}
<!DOCTYPE html>
< html>
< head>
  <title>Test</title>
</ head>
< body>
This is HTML body stuff
</ body>
</ html>
{/if}

Any hints as to how adapt in my code to account for the changes in 2.1.5 is much appreciated.

Note: I had put spaces in the HTML tags in the code above so it would look right in this posting.

TIA,
Sanjay

Posted: **Thu Oct 13, 2016 1:39 pm**

I have an extended demo template here: http://www.cmscanbesimple.org/blog/base ... d-metatags

Posted: **Thu Oct 13, 2016 1:50 pm**

@Rolf - thanks for link. There are some good references there.

However, it does not address the specific parsing issue I'm facing.

Also it looks like the scope processing has changed in the current version of the platform. For instance I used to be able to assign a variable in zone 1 and use it in zone 2 without needing to declare global scope. That does not seem to be the case any more in 2.1.5

Posted: **Thu Oct 13, 2016 2:00 pm**

Just to clarify my current use-case/need (in pseudocode):

Code: Select all

if logic condition is true
then
  display text information (no html tags)
else
  display html page
end if

I need to be able to do this at a template level, so that the page can render text or html output depending on how it is accessed. If there is a better (more standard) way to do this, please let me know.

Thanks,
Sanjay

Posted: **Thu Oct 13, 2016 3:47 pm**

Note the explanation about the template areas!
You can't have an {if} in an other area/scope as the {else} or {/if}

Posted: **Thu Oct 13, 2016 5:02 pm**

Got it.

I was using a way to hide the <head> tag from the template parser:

Code: Select all

{assign var="htmlhead" val="head"}
<__html>
<{$htmlhead}>
...

I'm assuming this is unstable workaround at best. Is there any other way to accomplish what I need (as outlined in my earlier pseudo-code)?

CMS Made Simple Forums

New template compile error in 2.1.5

New template compile error in 2.1.5

Re: New template compile error in 2.1.5

Re: New template compile error in 2.1.5

Re: New template compile error in 2.1.5

Re: New template compile error in 2.1.5

Re: New template compile error in 2.1.5