FrontEndUsers, CustomContent and CMSMS 2.0
Posted: Fri Jun 19, 2015 8:30 pm
Hi all.
I am in the middle of fixing some issues for the FrontEndUsers module wrt 2.0. Particularly the issue with smarty scopes, and with the smarty security policy.
The {$feu_smarty} class (provided to smarty) provides numerous methods for interacting with the FEU database from within your various templates. I was forced to completely re-factor this class and its implementation and there will be compatibility problems.
For users currently using {$feu_smarty->method} style tags in their templates, once they upgrade to FEU 1.29 they will notice errors. they must now use the static {feu_smarty::method) instead.
Because of this change I took the opportunity to re-implement much (but not all) of the functionality from the CustomContent module. So that sites that need to do custom user based logic will no longer need that module.
The plugins from CustomContent that were not migrated are the {cc_menufilter_loggedin} and {cc_menufilter_memberof} plugins that took the nodelist from MenuManager and filtered it based on various properties in the content page. These plugins would not work properly with Navigator (the new Navigation module for CMSMS 2.0) and were of limited use.
Additionally, some feu_smarty method parameters have changed slightly, to take an optional uid. So please refer to the help and changelog before upgrading.
The Protected Content content type should be used instead if possible.
As of this date, I am officially deprecating the CustomContent module. It will not be supported for CMSMS 2.0.
Edit: The compatibility issues will be introduced in FrontEndUsers 1.29, which should be released in a few days
Thank you for your support.
I am in the middle of fixing some issues for the FrontEndUsers module wrt 2.0. Particularly the issue with smarty scopes, and with the smarty security policy.
The {$feu_smarty} class (provided to smarty) provides numerous methods for interacting with the FEU database from within your various templates. I was forced to completely re-factor this class and its implementation and there will be compatibility problems.
For users currently using {$feu_smarty->method} style tags in their templates, once they upgrade to FEU 1.29 they will notice errors. they must now use the static {feu_smarty::method) instead.
Because of this change I took the opportunity to re-implement much (but not all) of the functionality from the CustomContent module. So that sites that need to do custom user based logic will no longer need that module.
The plugins from CustomContent that were not migrated are the {cc_menufilter_loggedin} and {cc_menufilter_memberof} plugins that took the nodelist from MenuManager and filtered it based on various properties in the content page. These plugins would not work properly with Navigator (the new Navigation module for CMSMS 2.0) and were of limited use.
Additionally, some feu_smarty method parameters have changed slightly, to take an optional uid. So please refer to the help and changelog before upgrading.
The Protected Content content type should be used instead if possible.
As of this date, I am officially deprecating the CustomContent module. It will not be supported for CMSMS 2.0.
Edit: The compatibility issues will be introduced in FrontEndUsers 1.29, which should be released in a few days
Thank you for your support.