I have been getting reports of the following error occurring regularly when users are trying to create or edit any nodes (not specific to any content types):
"Validation error, please try again. If this error persists, please contact the site administrator."
After researching this error on drupal.org and Google, it seems the issue might be related to caching and/or sessions. But I haven't been able to replicate the error myself (I primarily use Firefox 3 and tend to clear the cache every time I close the browser). Users have reported needing to logout then back in again to "clear" the error. I tried checking the "recent logs" but it looks like these types of errors aren't logged(?) and I'm not familiar with other ways to troubleshoot the problem or where I should be narrowing my search (core or modules or both?).
Here are some specs for the site:
Drupal 5.12, Webauth (specific to our university), CCK, Content Access, Devel, Event, FCKeditor, Javascript
Tools, IMCE, Token, Webform, Update Status, Views, CAPTCHA
Roles: Users experiencing problems are logged in and have 2 roles - admin (full access) and webauth user - very basic "access content" permission)
Browsers: Primarily IE7 - some Firefox 3
Caching: All site caching turned off in admin settings
Two fixes that I have attempted so far:
1. In the settings file, I edited line 130: ini_set('session.cache_expire', 0);
2. In the .htaccess file, increased the php maximum execution time to 300
Any help would be greatly appreciated - Thanks!
Comments
Comment #1
timeandagain commentedAny update? We've had the same issue and don't have any idea how to fix it. Thanks
Comment #2
chill5-0 commentedI have had some luck with this issue. Unfortunately, I can't pinpoint the solution, so I've decided to simply document the process here:
1. I upgraded the following modules which were out of date: Date, FCKEditor, Signup, Contemplate (I forgot to mention some of these in my original post)
2. I deleted the event module to "clean house" -- we weren't really using it on the site.
3. In the settings.php file, I changed line 130 back to it's original setting: ini_set('session.cache_expire', 200000);
4. Also in the settings.php file, I uncommented line 147 (which creates sessions based on domain names) and added the full name of the domain. Since there are a large number of subdomains for our university, I thought this might help keep sessions clear.
It appears that #4 might have solved my particular problem, as I haven't been able to replicate the error since that change. I hope this helps!
Comment #3
ainigma32 commented@alakon: Can you confirm that the info provided by chill5-0 works for you too ?
- Arie
Comment #4
ainigma32 commentedLooks like alakon won't be posting any feedback so I'm setting this to fixed.
Feel free to reopen if you think that is wrong.
- Arie