Validation error, please try again. If this error persists, please contact the site administrator.
mrfelton - October 15, 2009 - 13:00
| Project: | Profile Setup |
| Version: | 6.x-3.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
Description
I have a pageroute setup with two pages. The fist just displays a node, the second lets the user edit their profile (content_profile). On clicking the forward button on the second page (the one that uses this modules 'User account editing' page type), I get taken back to the first page, with the error message:
Validation error, please try again. If this error persists, please contact the site administrator.

#1
More info...
If the User account editing is the only page in the pageroute, it works.
If the User account editing page is the second page in the pageroute, with a Node display page before it, I get the validation error when saving the second page
If the User account editing page is first in the pageroute, and a Node display page follows it, there are no errors after submiting the first page (User account editing), but when submiting the second/last page (Node Display) I get taken back to the first page, with the Validation error AND another error stating that one of the cck fields (numeric) is required - even though the field already had a value, and I didn't even try to edit that field!
#2
Hi,
I'm unable to recreate this error.
What form fields do you have in your content profile form?
Thanks
Tom
#3
I have 3 cck fields, an Imagefield, a Float, and a CurrencyCCK. It is the Float field that gets reported as missing a value when I get booted back to the form as described in my 3rd scenario above,.
#4
After a VERY painful debuging session, I have managed to trace thei to an incompatibility with the memcache module. It seems that with that module enabled, $form_state is not managed properly and your attempt to do
if (!isset($form_state['storage']['route']))inpageroute_form()returns false, resulting in the pageroute being built again from page1.#5
Actually, restarting memcached seems to have fixed it and now it works just fine with memcache installed. Really strange.
#6
Thanks for testing this out and tracking down the issue!!
I've marked it as "needs review" so we can keep any eye on it, I haven't had time to test it with MemCache yet.
Tom
#7
I actually think the problem is more related to pageroute than to profile_setup, since that's where all the logic comes from.
#8