Field named "status" can cause issues #877

Closed
pglewis opened this Issue Dec 15, 2012 · 5 comments

2 participants

@pglewis
Pods Foundation, Inc member

I ran into this while researching #872

I'm not sure of the scope of the issue yet... whether it's a public form issue, an issue with relationships named "status", or any field named "status".

A quick search in the issues is turning up a number of open issues with fields named "status".

@pglewis
Pods Foundation, Inc member

There is a package and shortcode from the original WP.org issue report that can demonstrate it quickly:

http://wordpress.org/support/topic/unable-to-process-request-please-try-again?replies=5#post-3578154

Drop the shortcode in a page and visit it, you'll see it choking on the 'status' field.

@sc0ttkclark
Pods Foundation, Inc member

Is this still happening?

@sc0ttkclark sc0ttkclark was assigned Feb 19, 2013
@pglewis
Pods Foundation, Inc member

I'm wondering if this has something to do with the alias 'status' set for 'post_status' in PodsAPI::get_wp_object_fields()

@sc0ttkclark
Pods Foundation, Inc member

Adding a field that has an alias on an object field should be disallowed right now. So if this is on a Post Type, it should warn you and not let it save. Is that not the case?

@pglewis
Pods Foundation, Inc member

It very well could be fixed then. I created this issue back when I was troubleshooting other things for 2.1 and I haven't returned to it to investigate more closely.

The breadcrumb trail in this thread should be able to repro the situation to test, however.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment