CMS Made Simple Forums

@minneapolis_dan : I'm using 1.5.1 without a problem. I have never been logged out. I use only core modules, no extra. You should upgrade to the latest stable 1.5.1 (today) version and report any problem with "System Info" to point at your modules list.

Pierre M.

alby wrote:

hhm wrote: Any reason why the contact_form plugin has been removed / disabled????

And what's the (best) alternative..?

Use FormBuilder module.
It has already a contact form

Alby

can it handle multiple contacts and multiple target emails per contact like simon's mod to the original, and MUCH SIMPLER contact_form tag?

imho, pulling out such a basic function and requiring a third-party addon that is infinitely more complex is just stupid.

Thanks Pierre M. I think I figured out the problem. My session_save_path was not set, and once I corrected that, the log out problem went away. I'm not sure I would have noticed the problem if not for the new security features that require a session ID while logged in to the admin. 

duclet wrote: There was a code change to 1.5 that requires a security key to be added to the URL of all links within the admin section. This of course would break any links (which many modules has) from working at it redirects to the login page. So in essence, it isn't your host but the update to CMSMS. I am sure most developers, myself included, are updating our modules links where necessary. As to other parts of the site, I haven't digg in too deep to know.

I can confirm the problem with links not containing security key in the notification mails sent out from the module. E.g.
Comments - when comment added, mail is sent to administator with the link to comment. Link doesn't work.
Guestbook - when entry is added, mail is sent to administator with the link to the entry. Link doesn't work.

I have not tested more modules, but is there the solution for this issue? Since you cannot know security key you cannot place correct link in mail. Or?

Yep I think there is no way around it and the links should just get removed completely. Every gateway would lead to a possible XSS so it will make the whole protection thing useless.

I'm having the same problems.  Any resolution to this?

Unfortunately, there is nothing you can do about this. It is up to the module's developers to make sure that their module include the new security key. I myself was very much upset with this upgrade when I first heard about it since I still don't believed it really does much of anything beside adding one extra step. Nevertheless, since most of my modules is using customized URLs which it seems like it is not affected by the change, I really don't care that much.