Custom content / protected content

[kmesd62]

I”ve just noticed that since upgrading to cmsms 2.0 last year that login/custom content on one site is no longer working (viz input boxes disappeared from login form, prompts still there)... this looks like a substantive change, e.g. from -> to :: syntax in templates that might also explain a 500 error on the customcontent module... I”ve also just seen calguys 2015 post announcing deprecation of custom content module and the feu group custom menus won”t be supported.

Could someone share a couple of bullet points on what I would need to do to migrate custom content functionality implemented c. Cmsms 1.11 so that it’s doing the same kind of thing in cmsms 2.2.6?

It’s possible that there’s a resource already prepared that covers this, scenario in which case I apologize for not having found it yet.

Thanks in advance for your assistance.

[Rolf]

You will find more info about the FrontEndUsers module here:
https://www.cmscanbesimple.org/blog/set ... ers-module
https://www.cmscanbesimple.org/blog/add ... e-features
https://www.cmscanbesimple.org/blog/mar ... navigation

The CustomContent module isn't needed anymore.

[kmesd62]

thanks Rolf for the prompt response...

in my 1.11 set up i displayed menu/navigator nodes according to the user's privileges, and tested this as follows:

Code: Select all

{if !$node->extra1 or $ccuser->memberof($node->extra1) }

thus in 2.x, the test for a non-protected (and ok to display) node would seem to be:

Code: Select all

$node->type != 'feu_protected_page'

and for group-specific pages I can test the groups a user is a member of like this:

Code: Select all

{feu_smarty::is_user_member_of($groups)}

, but what's the name of the node property that would give me the groups the protected page is assigned to? $node->feu_groups?

[I also need a reminder of how to enumerate an object to display all the properties!]