Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with HTTPS or Subversion.

Download ZIP

Loading…

Unable to process request, please try again #872

Closed
pglewis opened this Issue · 11 comments

3 participants

PG Lewis solaris76 hembo
solaris76

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

solaris76

ajaxurl is not defined in jquery.pods.js

solaris76

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

To my template file.

hembo

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

PG Lewis pglewis was assigned
PG Lewis
Owner

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...

PG Lewis
Owner

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.

PG Lewis
Owner

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.

solaris76

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

PG Lewis
Owner

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

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

PG Lewis
Owner

Excellent news, thanks for your patience!

PG Lewis pglewis closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.