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
Notice: map_meta_cap was called <strong> incorrectly </strong>. The post type jp_sitemap has not been registered, so checking the ability to "edit_post" against such a post may not be reliable.
#177
Closed
rebeccahum opened this issue
Aug 12, 2019
· 1 comment
· Fixed by #178
Describe the bug
When using Jetpack 7.6 and SRM, you see this notice when cron runs:
Notice: map_meta_cap was called <strong> incorrectly </strong>. The post type jp_sitemap has not been registered, so checking the ability to "edit_post" against such a post may not be reliable. Read as <a href="https://codex.wordpress.org/en-US:Debugging_a_WordPress Network"> Debugging WordPress </a> for more information. (This message was added in version 4.4.0.) In in /chroot/var/www/wp-includes/functions.php on line 4773
When jp_sitemap posts get deleted during the sitemap cron, SRM runs a capability check on every post during the save_post event, triggering a “doing it wrong” warning.
The text was updated successfully, but these errors were encountered:
@rebeccahum welcome to Safe Redirect Manager and thanks for the Jetpack feedback and related PR! I've milestoned these for our next release, though that's currently unscheduled but I'll keep you posted as we get through planning and review if there's anything else needed on this issue and related PR.
Describe the bug
When using Jetpack 7.6 and SRM, you see this notice when cron runs:
Stack trace:
When
jp_sitemap
posts get deleted during the sitemap cron, SRM runs a capability check on every post during thesave_post
event, triggering a “doing it wrong” warning.The text was updated successfully, but these errors were encountered: