next »

[jamesbisset]

I've inherited a CMS MS site (so I'm a newbie) and upgraded it from 1.06 to 1.2.3. I've also upgraded FEU to 1.4.2 but I have a couple of problems.

1. The 'change settings' link on the logout page doesn't go anywhere. The only difference that I can see from other links which do work (eg lost password or logout) is that those links include "m6"

- "http://my.domain.com/index.php?mact=FrontEndUsers,m6,default,1&m6form=forgotpw&m6returnto=64&m6returnid=64&page=64"

whilst the 'change settings' link doesn't

- "http://my.domain.com/index.php?mact=FrontEndUsers,cntnt01,default,0&cntnt01form=changesettings&cntnt01returnid=64"

Is that the issue or is it something else entirely?

2. I'm not convinced that all the default templates are in place or correct. eg: The lost username template has two fields, but the first one (Lost Username Details Template) is empty. Resetting 'defaults' makes no difference. Is there somewhere I can copy original defaults from, or am I barking up the wrong tree (again)?

Lastly, when testing stuff like 'lost password' I can see messages stored in the url, but these messages don't get echoed out in the page itself. Is that the default behaviour?

[xpatriot]

Hi
I'm experiencing the same type of problem.
I am new to CMSMS
I installed and configured CMSMS + FEU last week (laters versions)

The page with : {cms_module module=FrontEndUsers form="changesettings"}  works fine if there is no user logged in as I get a relevant error message.
However, when there is a user logged in, the page comes up with just the {$title} and nothing else.

Thanks for any help

[jamesbisset]

Well, I think I've finally cracked it!

In my inherited site, the {cms_module module=FrontEndUsers} was in a template. The login page used that template but had no content. And the template didn't use the {content} tag.

So, on the basis that it was the 'page' that was doing the work, I removed the {cms_module module=FrontEndUsers} from the template, replaced it with {content} and put the {cms_module module=FrontEndUsers} into the login 'page'.

Then, and I'm guessing this is the most important bit, I used the options tab and unchecked the 'cachable' checkbox.

I found out about the 'cachable' option by reading the help page on the custom content module which had also been installed.

I've no idea whether the custom content module is required - I think not - but the principle that the login page shouldn't be cached makes sense, because the messages on there will only be available to individual users.