Change WordPress user roles and capabilities › Forums › Bug Reports › Conflict with Oasis Workflow? › Reply To: Conflict with Oasis Workflow?
I found that “Advance Custom Fields” plugin stores its custom fields data as the custom post type ‘acf-field’. This may be a problem, why some of revisioned values of such fields were not available when URE applied edit restrictions by the list of the post ID, as ‘acf-field’ custom post type was not included into the list of records available for the current user.
I added ‘acf-field’ custom post type to the arguments list of the code at your functions.php file:
$posts = get_posts(array( 'numberposts' => -1, 'post_type' => array('tribe_events','page','revision','acf-field'), 'post_status' => 'any', 'meta_query' => array( 'relation' => 'OR', array( 'key' => 'analytics_group_name', 'value' => $ag, 'compare' => 'IN', ), ), ));
As you use revisions, I added revision post type too and replaced post status to ‘any’ (revision has ‘inherit’ post status’).
Restricted user sees the latest content now at my test site. Make a new test at your own.