Skip to content
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

Non wp_ table prefix -> user relation by role broken #2306

Closed
canonex opened this issue Jul 28, 2014 · 3 comments · Fixed by #2385
Closed

Non wp_ table prefix -> user relation by role broken #2306

canonex opened this issue Jul 28, 2014 · 3 comments · Fixed by #2385
Assignees

Comments

@canonex
Copy link

canonex commented Jul 28, 2014

Hi,

got two fresh installations of Wordpress.

If prefix table is the standard wp_ everything is working.

If prefix table is something else (ex. bwp_ or wpk_ ...):
->new field
->select relation
->select users in the correlation dropdown
->in the additional field options pick one ore more role to limit the available users

the filtered list is always empty.

Thank you,
Rickyx

ps. this issue is somewhat related to http://pods.io/forums/topic/user-dropdown-by-role/ but this is a brand new installation and no other plugins are present.

@kadamwhite
Copy link

This is occurring for me as well.

@Shelob9
Copy link
Contributor

Shelob9 commented Jul 29, 2014

I can reproduce as well.

I also get this error 3 times:
Notice: like_escape is deprecated since version 4.0! Use wpdb::esc_like() instead. in /srv/www/wordpress-trunk/wp-includes/functions.php on line 3201

Testing with Pods 2.4.3 and WordPress 4.0-beta2-20140725, but updating pods_sanitize_like() to use the new wpdb::esc_like() doesn't resolve the issue.

@kadamwhite
Copy link

❤️

@sc0ttkclark sc0ttkclark self-assigned this Dec 29, 2015
@sc0ttkclark sc0ttkclark removed Status: Help Wanted We have not prioritized this yet, but you can help make it happen to speed it up Status: Need Research labels Dec 29, 2015
@sc0ttkclark sc0ttkclark modified the milestones: Pods 3.1, Pods 3.0 Dec 29, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants