CustomContent and FrontEndUser modules don't seem to be working properly

[Eagle1]

Hi,

I am using CMSMS version 1.0.2, CustomContent 1.4.3, FrontEndUsers 1.1.1, and cannot seem to get them to work properly. I've read all the help files, but don't understand all the settings needed in FrontEndUsers to get it working, I guess.

What I'm trying to do: I need to display members-only content when a member logs in. They should have a generic login username and password for all members. It doesn't need to be a personal username and password. And all I need from them is their username and password--the default fields for FrontEndUser. In other words, I don't need any "properties" in the FrontEndUser Management screen.

Yet, logged in as a member or an admin I cannot see the content of the page.

Here's my template code:

Code: Select all

{cms_module module=CustomContent}
{if $customcontent_loggedin}
<h2>Welcome {$customcontent_loginname}</h2>
{content}
{else}
<h2>Sorry, you must be a logged-in member to view this page.</h1>
{cms_module module=FrontEndUsers}
{/if}

Any help or further guidance would be much appreciated. I have searched the forums, but couldn't find anything similar to this problem.

Thanks,
Matt

[jmcgin51]

try {if $customcontent_loggedin == 1}

instead of {if $customcontent_loggedin}

[petert]

try {if $customcontent_loggedin == 1}

This works better for me (most of the time)

  if $customcontent_loggedin == '1'

it's the single quotes that do the trick. Shame that the examples in the module are not updated yet

[Eagle1]

Thanks to both of you for replying.

I've tried both:

if $customcontent_loggedin == 1

and:

if $customcontent_loggedin == '1'

and still no luck. Are there settings within the admin panel of Frontend User Management that perhaps I'm not setting up correctly?

Thanks again.

[jmcgin51]

just curious - have you tried using the comment tags version of CC instead of the Smarty tags?

also, make sure you turn off page caching for any pages that contain CC-protected content...

[calguy1000]

two things:

a) therre's a caching bug that's fixed in 1.0.3 that may effect what's happening.
b) you will probably want to have {content} displayed at all time in your template, as certain modules, etc. require it.  I had problems when I did a similar thing in my template I got really weird results.  however, wrapping additional content blocks in customcontent stuff should work fine.

[Eagle1]

just curious - have you tried using the comment tags version of CC instead of the Smarty tags?

also, make sure you turn off page caching for any pages that contain CC-protected content...

I have tried both the Smarty template way and the comment tag versions.

Turned off page caching, still no luck.

two things:

a) therre's a caching bug that's fixed in 1.0.3 that may effect what's happening.
b) you will probably want to have {content} displayed at all time in your template, as certain modules, etc. require it.  I had problems when I did a similar thing in my template I got really weird results.  however, wrapping additional content blocks in customcontent stuff should work fine.

a) I do have version 1.0.2. When do you expect 1.0.3 to be available to the public?
b) I tried it both with {content} and without, still no luck.