publicForm > Form expired
January 23, 2010 at 3:30 pm #160984
I also have the same problem, with a fresh installation. I get the "Session Expired" message even if I click instantly on the Submit button.January 24, 2010 at 11:29 am #160985
Problem solved. The "session.save_path" directory wasn’t writable. Now everyting is working well!March 6, 2010 at 4:57 pm #160983
even when loading the form new and instantly submitting, i´m getting constant warnings, that the form expired…March 6, 2010 at 4:57 pm #160986
I am getting this "Error : The form has expired".
It appears in :
* my publicForm
* the shorter form done with "pods_ui_manage"
but it doesn’t appear in the regular form.
If the trick is to make session save_path writable, I am affraid I can’t do that : I am on a shared hosting solution.
Is there another solution ?April 6, 2011 at 7:19 am #160987
sc0ttkclarkKeymasterPost count: 804
Additional information on the error:August 7, 2012 at 2:36 pm #168141
I made a simple form with the Pods UI, but now I am blocked with the error:
“This form has expired. Please reload the page and Ensure your session is still active.”
I have looked for a solution on the forum and also googled’it but can not find how to solve the problem.
The error is with a fresh installation of WordPress. The server is a Plesk VPS with the following definitions taken from the PHP phpinfo () function:
Session Support enabled
Registered save handlers files user
Registered serializer handlers php php_binary wddx
session.cache_expire 180 180
session.cache_limiter nocache nocache
session.cookie_lifetime 0 0
session.gc_maxlifetime 1440 1440
session.name PHPSESSID PHPSESSID
session.save_handler files files
session.save_path /var/lib/php/session /var/lib/php/session
I have tried to give permissions to the /var/lib/php/session folder -rwx rwx rw- where everyone can write and read, but did not resolve.
Also I I disabled the other plugins :
- Grunion Contact Form
The strange thing is that installing WinXP on my personal computer works well, even with two active plugins:
I had developed so many PHP code to use this plugin and now i’m stucked.
Please does anyone know how to help me?August 7, 2012 at 8:50 pm #168143
I’ve run into this myself on a recent site. I got the error with a fresh WP install, fresh Pods install, created one simple Pod with a couple fields, then tried to create a record in the Pods admin. If you strip down to that do you still get the error? Or did this only start creeping in when you added extra Pods UI code? I’ve checked the mentioned settings in other threads and everything appears to be okay, but it’s failing regardless.
I haven’t found the cause nor a fix yet but I will keep you posted on anything I find. In order to keep it from road-blocking development I made a hack to my /wp-content/plugins/pods/ui/ajax/api.php. The failing check is in the process_save_pod_item() function, at the top. I’ve simply bypassed the call and subsequent check of pods_validate_key by commenting those three lines out. This is obviously not an acceptable long-term solution and the site is done and soon to go live, so I’m going to have to dig into it much sooner than I’d like :/.August 7, 2012 at 9:20 pm #168144
I rolled up the sleeves, uncommented the workaround hack…. aaaaaaand no error now.
I’ve suspected something weird and wrong on the hosting end all along, it was just going to be a fiddly matter of finding out /what/. Apparently they’ve straightened out the problem before I even had to put in a ticket. I wish I could get more things to solve themselves.August 8, 2012 at 7:18 am #168146
@PG Lewis Many many Thanks… for sure I had started creeping :s
I had not carefully explained before. The form in question is a Pod created in the Admin area without any intervention or any change to the code by me, I just do PHP programming for presentation in the public areas along with the HTML by going to the API’s of WordPress and in this case the Pods Framework. What I could not do was simply add a new, or any, record from the Admin area to a simple Pod with three fields [Name][Slug][Quantity(num)].
@PG Lewis said:
I haven’t found the cause nor a fix yet but I will keep you posted on anything I find. In order to keep it from road-blocking development I made a hack to my /wp-content/plugins/pods/ui/ajax/api.php. The failing check is in the process_save_pod_item() function, at the top. I’ve simply bypassed the call and subsequent check of pods_validate_key by commenting those three lines out.
I followed your tip and did almost the same. I just add a comment to the two lines if (false === $columns) and subsequent action die(“This form has expired. Please reload the page and ensure your session is still active.”);
That worked for me.
Now I can add records to Pods. That is very cool but very strange.
So, is it too risky to deliver a website with this solution/hack?August 11, 2012 at 2:54 pm #168161
Those checks are in place to thwart bad guys from spoofing session information to try to do bad things (TM). It’s never a good idea to bypass security measures, so I wouldn’t consider commenting those lines out as an acceptable permanent solution.
My ongoing saga is this:
* The site did NOT fix itself, I was brain dead and didn’t hit the magic button to copy the changes to the server. It was late
* Further troubleshooting found that, not only was my session save path unwritable… it didn’t even exist. This is a job for a hosting ticket.
* Due to unrelated technical issues, we’ve moved the site to another host. The problem goes away on its own again.
We may or may not follow up to get the broken hosting account fixed, but it looks like it’ll be a tech support fix if we do.August 13, 2012 at 6:34 am #168164
I’m getting this error when I try to use the form in the dashboard (backoffice). Never even got to the point of public form yet.
My host is Fatcow.
NofiaAugust 13, 2012 at 6:44 am #168167
OK, just so you all know. I had switched my PHP to 5.3 before I got this error.
I read the threads on this issue. thought about what I had changed in PHP.ini. Nothing. But i went back into my server PHP sets and saw I had updated to PHP 5.3 so changed back to PHP 5.2 and the error has gone away.
In short, the plugin seems to be incompatible with PHP 5.3.
Hope this helps someone.
Fatcow note on PHP 5.3:
Information About PHP 5.3
PHP 5.3 introduced significant positive changes to PHP. However, some older applications may not work with PHP 5.3, as some php.ini directives are not compatible with PHP 5.3+ (e.g register_globals or cgi.force_redirect). If you are having issues, PHP 5.2 is available for backwards compatibility.August 13, 2012 at 11:40 am #168174
I have 2 recently started websites that are hosted on Fat Cow and both have had this problem. The value for the session save path was set to:
but that directory does not exist. This is NOT a problem with PHP 5.3 compatibility and I do NOT advice downgrading to an older version of PHP. Check your session save path with the code snippet here:
If the session save path is not writable or doesn’t exist (this was the case for BOTH new Fat Cow accounts) then contact your hosting and have them fix it. It is your hosting that is broken, not PHP 5.3.
You must be logged in to reply to this topic.