Custom content / protected content
Posted: Sat Mar 03, 2018 7:47 pm
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.
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.