Unable to process request, please try again #872

Closed
pglewis opened this Issue Dec 14, 2012 · 11 comments

Projects

None yet

3 participants

Issue appears to be a request for this url on submit: http://www.theanglingedge.com/add-catch/&action=pods_admin, that is understandably causing a 404.

Being requested via jquery.pods.js

ajaxurl is not defined in jquery.pods.js

Issue is that ajaxurl only gets defined within wordpress admin. Fixed by adding:

<script type="text/javascript"> var ajaxurl = ''; </script>

To my template file.

hembo commented Dec 14, 2012

good you found the solution, but which template file? pods template? wp templates?

@pglewis pglewis was assigned Dec 15, 2012
Owner
pglewis commented Dec 15, 2012

I'm seeing some weird issues using "status" as the field name in this test. I changed the name of the field to "thestatus" (along with the field name in the shortcode of course) which is clearing part of it up, but I'm running into a new issue. Still digging...

Owner
pglewis commented Dec 15, 2012

I have a couple things ironed out on it now, but I'm getting a message that the current CV is empty even though I uploaded a file. You can rename the "status" field and try the latest commit: http://pods.io/latest to see where things are at.

Owner
pglewis commented Dec 15, 2012

I'm getting an issue with the plupload field, but the latest commit appears to be working for me with the WP Media Library uploader. Can you test and verify that on your end?

I'm going to open new, fresh issues for the "status" field name and pluploader problems and we can close this one if we've got you're original issue ironed out.

Added the ajaxurl declaration to my wp template file. Though I am sure there may be a more elegant solution!

Owner
pglewis commented Dec 15, 2012

Again, I believe this particular reported issue is resolved in the latest commit:

http://pods.io/latest

The latest commit is working for me locally as well for someone else in #856, without the need for an ajaxurl declaration. I have uncovered a couple other issues in the process and created new tickets for them but the "Unable to process request" error appears to be fixed.

hembo commented Dec 16, 2012

Hei, tested the latest commit and now all seems to work. Many thanks!

Owner
pglewis commented Dec 16, 2012

Excellent news, thanks for your patience!

@pglewis pglewis closed this Dec 16, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment