New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Queries without a connection type no longer work #131
Comments
scribu
added a commit
that referenced
this issue
Mar 21, 2012
scribu
added a commit
that referenced
this issue
Mar 21, 2012
scribu
added a commit
that referenced
this issue
Mar 21, 2012
Was going to say that connection types without an explicit name no longer work either, but that's not true: they get assigned a hash, which is then passed to 'connected_type'. |
dbernar1
pushed a commit
to dbernar1/wp-posts-to-posts
that referenced
this issue
Oct 1, 2014
dbernar1
pushed a commit
to dbernar1/wp-posts-to-posts
that referenced
this issue
Oct 1, 2014
dbernar1
pushed a commit
to dbernar1/wp-posts-to-posts
that referenced
this issue
Oct 1, 2014
dbernar1
pushed a commit
to dbernar1/wp-posts-to-posts
that referenced
this issue
Oct 1, 2014
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Furthermore, they throw an obscure warning:
http://wordpress.org/support/topic/plugin-posts-2-posts-update-to-116-causing-error-in-wp-version-331
It should be handled better.
The text was updated successfully, but these errors were encountered: