Restrict access to CMS - users must login first

[stidy]

Hi,

I would like to setup CMSMS so that users MUST login first to see any content - ie. they only ever see a user login screen when they first go to the site.

Forgive me if this has already been discussed - in which case point me in the direction of the solution please.

-s

[calguy1000]

You want the frontendusers, and custom content modules available on the forge.

then you just modify your template to only show the login form to non logged in people.

[stidy]

Thanks - I'll try it out

v quick reply - thankyou

[stidy]

Hi,
OK - installed the modules.
But how do I "just modify your template to only show the login form to non logged in people" ?
(Sorry -newbie)

[monghidi]

Sorry to bother -- I'm following this and a few other threads regarding customcontent and its ability to direct specific users to specific content.

It seems to me that customcontent doesn't actually 'protect' files/pages, but only 'presents' custom..er, content or pages. Or am I missing something? I'd like to achieve totally protected files and/or pages, which if you are NOT logged in are just plain inaccessible.

I think that's what stidy is looking for, too?

Thanks!

[calguy1000]

CustomContent uses either smarty, or text processing to remove output that is not available for unauthorized peop.e

i.e:


This text will be displayed to logged in members of the blob group

This text will be displayed to anonymous people or people who aren't members of the blah group


If the test fails, then the only content that will be displayed is the stuff inside the else statement, everything else is physically removed from the output.

so yes, CustomContent, does "protect" users from seing things.

[monghidi]

Thank you tons, calguy. I really appreciate the incredible amount of work you must be putting into CMSMS!

A quick thing: smarty doesn't work at all for me in CustomContent, though funky comments do. I'm using 0.13-beta4, and PHP 4.3.10 on a linux box, latest versions of CustomContent, FEU, CMSMailer, and SelfRegistration (unimplemented). Everything else is great and I am considering converting several "old" websites to CMSMS and the variety of modules as they work so well.

Anyhow, any clue why smarty won't fly for custom content? My templates include calls to both FEU and CC.

Thanks!

[calguy1000]

it's probably my fault

I may not have issued a release.