XOOPS Version: 2.2.3
Module Name/Version: Not sure, notifications?
PHP Version: 4.3.11
MySQL Version: 4.0.26
Web Server Software (Apache/IIS/Other): Not sure, it's hosted
Operating System: Not sure, it's hosted
Theme you are using: modified version of sev_dravid
Custom template: No
PHP Debug Messages: None listed when PHP Debug is turned on.
MySQL Debug Messages:
Smarty Debug Messages:
A full description of the issue:

Hi Gang,

I was having a problem with Notifications when I was running version 2.0.13.1. The problem was that after choosing a notification, it would say the database had been updated but the notification didn't save. I'm not sure how long this had been happening. I know it worked at one point because I have a number of notifications for my account.

I was unable to find anything on this issue in the forums so I decided to upgrade to version 2.2.3. For the most part, the upgrade went smoothly. However, when I try to set notifications now, I get this error: Quote:

I have read several other posts but have not found a problem exactly like mine. Some of the other posts ask about custom sessions. They're turned off on my site.

Can anyone suggest a fix?

Sean
PS I'm hoping that since this error occured after an upgrade that I'm posting in the right forum. If not, please feel free to move this post. Thanks!

I get the same error when I click on the get new password link from the request lost password e-mail.

I am also running XOOPS 2.2.3a-final. This is a fresh install, not an upgrade.

*bump*

Is anyone else having this problem? Is there a suggested fix for it?

Are there any kind people out there who are in the Holiday spirit and might like to suggest a fix for this?

Sean

several folks including myself have been having problems with "no valid security token" on 2.2.3. Mine is pretty much with comments only. There has been no resolutions as far as I can tell from those who have posted.

You can try emptying the contents of your session table in phpMyAdmin. This will at least reset all sessions.

Thanks for the suggestion Todd. Unfortunately, I've tried that several times without success. Tried it again after reading your post - no luck. Is this a known bug that the developers are working on? Does anyone know?

Sean

I saw your post on my bug entry on the dev log. So far, a lot of bugs have not been "assigned" including this one. I posted it there after a month or so of not being able to fix it. I don't know if this issue has gotten any attention from the dev side of the house. So far, the only repsonses have been from users who have the problem. I don't think there are many here who are familiar with the security token functionality, hence the lack of response.

My issue is primarily with Firefox and not as much with IE, though it does happen on any browser. Sadly, I have to recommend to people NOT to use Firefox and use IE instead. . Go figure.

Quote:

Have you tried turning them on?
Set your custom sessions for an hour. It's worth a try.

yes, it's definitely worth a try. I have tried every combination of custom sessions imaginable, on/off, long/short, etc. and it doesn't resolve my token error issue on XOOPS comments.

But definitely try it out.

Quote:

Thanks for the suggestion Clever/Lisa. I just tried turning on the sessions with a 60 minute duration and a 15 minute duration. I then emptied the session table. Both configurations provide the same results - the token error.

Unlike the post from ToddHerrold above, I get the error message every time anyone tries to add a notification in both IE and Firefox.

I must admit to some frustration that this has been going on since November and we've not even received any recognition of the problem from a developer.

Notifications are important to our site. They are the "hook" to get people back to visit. Without them, our membership think that the site is stagnant and don't come back.

Sean