You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have a Fieldmanager_Datasource field which refers to an object that has since been deleted, the post will not save, indicating that the user cannot edit the object.
if ( ! current_user_can( 'edit_post', ... appears in a couple of places. It's possible for that to not be the capability to edit a post, if a post type has custom capabilities set. This should be loaded dynamically (see below for demo code), and a code audit should be done to ensure that all could-be-modified capabilities are loaded dynamically.
Came across two permission issues today:
If you have a Fieldmanager_Datasource field which refers to an object that has since been deleted, the post will not save, indicating that the user cannot edit the object.
if ( ! current_user_can( 'edit_post', ...
appears in a couple of places. It's possible for that to not be the capability to edit a post, if a post type has custom capabilities set. This should be loaded dynamically (see below for demo code), and a code audit should be done to ensure that all could-be-modified capabilities are loaded dynamically.Edit: turns out core does this mapping automatically.
The text was updated successfully, but these errors were encountered: