CustomContent SOS, can't make it working

[jindravavruska]

Hello,

I installed FrontEndUsers and CustomContent. I started simple by splitting  the demo Home page between logged-in users (regular content) and not logged-in users

So I took the page template 'Left simple navigation + 1 column' First, I added {cms_module module=CustomContent}. Then I enclosed every part of the page content (breadcrumbs, search, navigation menu, news and content) into smarty tags {if customcontent_loggedin} and {/if}, however I kept the two main divisions "sidebar" and "main" outside the conditionals, so that the page would not break down.  I also added into sidebar one extra section with FrontEndUsers logout form enclosed between {if customcontent_loggedin} and {else}, and FrontEndUsers login form between {else} and {/if}.

It did not work. The page appeared with all "loggedin" features shown, but when I clicked at the link to customize my FEuser data, the input form showed warning that I was not logged in (which was true). Why then did CustomContent let all the loggedin content go through and blocked the login form? Anybody had a similar problem?

Then I took a different approach. I replaced all smarty tags with around each section of the content, and to avoid false effect of 'else' I also enclosed the login form between 'startif not loggedin' and 'endif'. Well, interestingly, all the content, including the login form, appears in the page. Definitely not the way it is supposed to work.

If I use the {get_template_vars} smarty, it shows CMS variables (sitename, appname, script URL, page id etc.) but no variables coming from CustomContent, like customcontent_loggedin, customcontent_groups, etc.

Do yoiu anybodu know what's going on? Is there any diagnostics that could be used to identify the problem? I am helpless.

Jindra

[jindravavruska]

I will answer myself It might be helpful to someone else.

I still don't know what's the trouble with smarties. A friend of mine would say "I know.  It's broken!". So I won't use them, although I believe that they make the page code more consistent and readable than some dubious comments.

The comment syntax is sensitive to extra spaces between the comment tag '<!--' and the word 'customContent'. There must be no space. Calguy1000, with all respect to your effort, this was worth mentioning in the documentation.

Jindra

[calguy1000]

Did you try turning off page caching in the page editor when using custom content on the page.