Replies: 1 comment
-
why not create an PR for it ;) sounds reasonable - but maybe @sc0ttkclark has objections ^^ i solved a issue like that with a custom where |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
This is adding 1 line of code to pick.php around line 2043
if ( ! empty( $params['where'] ) && (array) $options['table_info']['where_default'] !== $params['where'] ) {
since the
@pods
magic tag assumes a global, setting$GLOBALS['pods'] = $pod;
allows this to work.However since im not a fan of blindly trampling over global variables I think
pods_v
should check for another source for the pods object.My use case has been
exchange.ID is null or exchange.ID = {@pods.ID}
to only allow a related item in a relationship to show that matches the current pod item or is not linked to one to prevent "in use" items from showing up in a list. Overall this is highly useful for dynamic where queries with "introspection" without the use of php filters or tag filters.Beta Was this translation helpful? Give feedback.
All reactions