Validation error?

Events happening in the community are now at Drupal community events on www.drupal.org.
findAtutor's picture

Hello everyone, long time lurker, first time poster to the Vancouver group discussion. I'm more of a drupal "user" than "developer," but the person who does most of the programming is also subscribed to this group, so we'll both get the feed back, so hopefully one of us can find a solution.

I have converted my web site to be a drupal site and launched it as the new drupal site about a month ago. I've been getting reports from some of my customers as having problems logging in. At first I thought it was due to confusion, and for some just not getting it, but now I've received an e-mail from a user that copied the message they received from the web page when they tried using the request new password feature, and they received the following message:

"Validation error, please try again. If this error persists, please contact the site administrator."

What they said they did was requested a new password, clicked on the link in the e-mail, used the one time login, entered a new password in both fields, clicked on submit, and that's when they got the message. From what they sent me, there was the standard drupal user account information there (the View/ Edit/ Track / Account settings/ Personal information ) but where they should see content (in the case of my web site, a tutor listing) there is the validation error instead and nothing else.

I myself have received a validation error as I navigate the site, but that's while I'm logged in as an administrator, and I didn't think it was a concern for other users. I'm much more concerned about paying customers seeing this, as it limits their access to using my services (including paying me!)

Has anyone else come across this? Any ideas what may cause it, or what I can do to track or determine the reason for it? Any possible solutions? So far I can't replicate the problem, but this particular customer has been complaining for days that they can't login, so it's possible that it's consistent for other users.

Suggestions are welcome and would be greatly appreciated!

Thanks,
Johanna

PS My web site is http://www.findatutor.ca FYI. I'll leave the shameless plugging for another time!

Comments

Permissions and ACL Settings

TechSteve's picture

Hey Johanna,
I think you may double check the permissions and acl settings.

cheers,
steve

A Drupal Developer

Hi Steve, I don't think its

findAtutor's picture

Hi Steve,

I don't think its a permission thing, as all users are granted the same permission settings, and most users have no problems logging in, this is the only officially "documented" case I have. When I get the error, it seems to be random (I don't get it every time I do the same task).

Other ideas?
-Johanna

findAtutor.ca
Tutor listing service
Get help and excel!

OK for now.

findAtutor's picture

The customer who has not been able to login for days just e-mailed me saying they finally figured out what to do and no longer have any problems.

That's good to know, unfortunately it still doesn't explain why the validation error seems to pop up occasionally.

Until the next question...

Thanks,
Johanna

findAtutor.ca
Tutor listing service
Get help and excel!

I've seen this kind of thing

dale42's picture

I've seen this kind of thing come up when the cookie domain name gets confused. This was a problem with earlier versions of Drupal when you had two different sites with the same base domain, like www.example.com and videos.example.com. This issue has been fixed, I can't recall in which release.

I've also run into this kind of thing when the same site is available from 2 different domains. For me it usually happens in dev/staging type situation.

I can't recall for sure, but I think Drupal equates example.com and www.example.com as the same thing in this respect. Anyone know? It's a good idea for SEO to insure the users get one or the other, not both, in any event.

Clearing browser cookies is a temporary fix. If you think this might be the issue you should review your Apache and Drupal config to see if something is manipulating cookie domain values behind the scenes.

Modules used

dwees's picture

It might be useful if we knew exactly which modules you had enabled. You could also check the issues queue for messages like the one you had.

Try looking through the results of this search:

http://drupal.org/search/node/Validation+error%2C+please+try+again.+If+t...

Thanks for the extra info. I

findAtutor's picture

Thanks for the extra info. I didn't see your message until after I posted my last reply.

We're also seeing a problem when someone clicks on logout, it doesn't appear that they have logged out. The user is actually logged out, but the user menu stays. I get this happening in Firefox (but not IE). We have a feeling there is some kind of cache or cookie thing going on.

Will investigate and post another question if we get stuck.

Thanks again!

findAtutor.ca
Tutor listing service
Get help and excel!

This is not a cookie problem

hound's picture

and it is not fixed (at least in Drupal 5.14.)

Failure mode: I have a lot of blocks (many automatically created by the aggregator module.) If I create a new block or try to enable or move an existing, enabled block (it does not matter whether the block is automatically created or was manually built,) I often will get the pink warning box with

"Validation error, please try again. If this error persists, please contact the site administrator."

(Of course I am the god user, so this is not applicable)

It does NOT matter whether page caching is enabled.

On occasion I've also gone into the actual MYSQL tables and manually moved blocks around (since I have fifty themes, this is a really really ugly way to do work, trust me!)

Workaround:

I have noticed that if I create (but do NOT ENABLE) several blocks, and then DELETE one of them, the validation problem goes away. Once I am able to move or enable a block, then I can pretty generally move or enable all I want!

I've taken to creating a surplus stash of dummy blocks (SPACER1, SPACER2, etc) with no content. When I want to do something with the block arrangement, I just 'burn off' one of these spares by deleting it - as I say, it is a crude workaround and I have NO IDEA why this should do anything. It usually works for me.

If any Drupal developers are reading this thread, please fix this! It is really a deal killer for deploying a client site!

You still haven't told us

dwees's picture

You still haven't told us what contributed modules you are using. Stop complaining unless you are willing to give us the information we require.

Dave

Validation Errors persist

casperl's picture

Trying to comment to a node in Drupal.org - in a group that I belong to - I also get "Validation Error" - see the attached screendump. Somebody needs to complain since this problem has been around for a long, long time!

Aaah I see you are using

dwees's picture

Aaah I see you are using Opera. Has anyone experienced this problem when using a different browser?

Here is a possible (although semi-unlikely answer).

  1. Forms API uses invalid IDs occasionally for some of its hidden form elements.
  2. Opera or some standards compliant browser refuses to validate the invalid IDs, or modifies them to make them valid, or ignores those fields when submitting the form (no idea if this actually happens or not).
  3. Drupal doesn't have all of the form fields in question, and so throws a weird validation error.

Solution:
Make sure that all form ids begin with a letter so they are valid. Is this being worked on by anyone?

Validation Error: SOLVED! (for me, anyway)

hound's picture

I have fixed this problem on my own sites - it turned out that because I was running Suhosin-hardened Apache and PHP5 (the Ubuntu default install,) and I had a large number of blocks (as noted in my original 'workaround' fix above,) I had exhausted the Suhosin variable limit.

The problem went away for me when I edited my php.ini file to insert the following lines:

[suhosin]
suhosin.post.max_vars = 400
suhosin.request.max_vars = 400

The default limits are 100 for each, I believe.

Of course if you are not using a Suhosin version of Apache and PHP this will have no effect (it is harmless, though.)

As always, YMMV, but it worked for me. Good luck! (and please post here if this was in fact your problem.)

Also, I used Firefox exclusively - not Opera. That was not the issue for me.

Other relevant posts:

See http://drupal.org/node/346015

and http://drupal.org/node/350563

Secure Pages

916Designs-gdo's picture

I am using secure pages and switching from localhost to a dev site. Secure pages has an "insecure" and "secure" path setting which didn't match the domain the site was running on once I took it offline.

Disabling Secure Pages took away the validation error... someone is bound to run into it.

I ran into the same issue

perandre's picture

I ran into the same issue using the secure site module. Disabled it, and tataaaah!

Per André Rønsen | Front | Twitter: @perandre

I just had the same problem

nsputnik's picture

I just had the same problem trying to send a mass e-mail with the mass_contact module. Flush All Cache fixed the problem.

This worked for my situation.

jon360's picture

This worked for my situation. Thanks!

Flushing worked - thanks

ambiance7's picture

This worked for me too. Thanks!

-

work77's picture

I was getting this on the "clear cache" action. I logged out. Then logged back in again, and it's fine. Mysterious. I was using separate browser tabs before, but I'm not sure why that would make a difference.

I also have the same problem but on editing the comments.

hmdnawaz's picture

I also have the same problem but on editing the comments of discussion. I receive the following error message.
"Validation error, please try again. If this error persists, please contact the site administrator."

I don't know what is the problem.
If someone know its solution then please tell me.

Thanks in advance

Alternative Solution

SteveMM's picture

One of our Drupal experts found a solution to our particular problem. He said that when he looked at the Apache error log it had messages that the watchdog table and two others were corrupted. He used phpmyadmin to repair the tables.

HTH.

Vancouver

Group organizers

Group notifications

This group offers an RSS feed. Or subscribe to these personalized, sitewide feeds: