Hi there,
I am testing 1.5.RC3.14 on WP WordPress 3.0.4.
When I create a form and click the preview button and test the form, on completion it logs me out of my site and returns me to the WP log in screen.
What to do?
Cheers,
Gil
Hi there,
I am testing 1.5.RC3.14 on WP WordPress 3.0.4.
When I create a form and click the preview button and test the form, on completion it logs me out of my site and returns me to the WP log in screen.
What to do?
Cheers,
Gil
Thats very odd, haven't had anyone report this issue. It's possible it is some sort of strange plugin conflict. Try this...
- Deactivate ALL plugins
- Activate Gravity Forms
- Preview a form and see if it still logs you out upon completion
If it doesn't log you out, it could be another plugin causing a strange issue.
- Activate each plugin ONE by ONE
- Preview a form and see if it logs you out after each plugin you activate
If you hit a plugin that causes this behavior to occur, let us know which plugin it is.
Let us know how it goes.
Hi Carl,
No plugins installed. Only Gravity Forms. Using Genesis Framework and Expose theme. I could try Twenty.Ten if you like.
The form does not log me out if I run it from a published post. Only in preview mode.
Cheers,
Gil
Hi Carl,
I did some more testing. I turned off the genesis theme and went to stock Twenty.Ten.
Same thing
Modified the form by adding a field.
Same thing
Tried the preview function from both the Forms List and from the preview option at the end when editing a form.
Same thing
If you would like to log in I can give you a user-name and password to that site.
Cheers,
Gil
Found something interesting.
If I set the form setting for Confirmation to "page" it does not log me out. If I leave it set to text, it does. Hope this helps!
Cheers,
Gil
Done :-)
Good luck LOL!
You know, I just experienced this same thing. I was using 1.5 RC4 and WordPress 3.0.4. I was previewing a form, I test submitted it from the preview, and instead of my text confirmation being shown, I was redirected to my WordPress login. I think I know why though.
It's the difference between http://www.example.com and example.com (with www or without www) and the login cookie. This particular site uses http://www.example.com, and that is where I logged in when I started using the admin. However, after I submitted from the preview page, I received a URL that looked like this and was shown the WordPress login screen:
I think this is because of the new form action that was added recently. The action is action='http://example.com/wp-content/plugins/gravityforms/preview.php?id=25
with no www, but I had logged in at the www site, so the login cookie is invalid, and WordPress tries to reauth and redirect you.
So, where is this non-www URL coming from for the action?
In my General options, I have the WordPress address (URL) and Site address (URL) both set to http://www.example.com
HTH
@illinoisharley I'm not seeing it remove the WWW. The Contact Us form here on GravityHelp.com is running the 1.5 release candidate and it's form action is being set to http://www.gravityhelp.com, it's not trimming the WWW. I tested the frontend as well as the preview in the admin, both include WWW in the form action URL. Can you send us an example that we can look at via our Contact Us form? Thanks!
Sent a WordPress login via contact form just now.
Hellooooooooooo
Any progress on this (not that its mission critical)
Cheers,
Gil
Gil, can you post a link to your form so I can see if the same issue is affecting you that was affecting me? It had to do with the server config and Carl and Alex provided a fix that will probably be rolled into the next release.
As you mentioned, since it affects only the form preview it's not mission critical. But they were able to resolve it within just a few hours after my post. Sorry I did not post that update here.
Hi Illinois,
Actually, on updating to the latest beta yesterday, the problem has gone away!
The site I was testing at is not published. If you need, I'll set it back up tomorrow.
The form was just a test form with a few fields so I don't think it would have been that instructive!
Cheers,
Gil
There will be a fix in the next release. It had to do with a server configuration that required us to change how we get the URL.
Thanks Carl :-)