acegoulet

Sorry, I’m now seeing this is a duplicate of this issue, which has the fix in the thread: https://www.ads-software.com/support/topic/issue-with-last-update-custom-post-types/

Ah I missed this:

Something else to try – the plugin needs to be able to manage postmeta for post types, so you need to register your custom post types with support for custom-fields

Adding that support to the custom post type seems to have fixed the issue.

I have the same error when adding Apple News support to a custom post type. Here is the error from the “copy error” button:

TypeError: Cannot read property 'apple_news_api_created_at' of undefined
    at render (https://local.roadtrippersdev.com/wp-content/plugins/publish-to-apple-news/build/pluginSidebar.js?ver=399a6e300bdaabf151f1faecd2cfb13e:2:34671)
    at we (https://local.roadtrippersdev.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:84:293)
    at zj (https://local.roadtrippersdev.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:226:496)
    at Th (https://local.roadtrippersdev.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:152:223)
    at tj (https://local.roadtrippersdev.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:152:152)
    at Te (https://local.roadtrippersdev.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:146:151)
    at https://local.roadtrippersdev.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:61:68
    at unstable_runWithPriority (https://local.roadtrippersdev.com/wp-includes/js/dist/vendor/react.min.js?ver=16.13.1:25:260)
    at Da (https://local.roadtrippersdev.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:60:280)
    at Pg (https://local.roadtrippersdev.com/wp-includes/js/dist/vendor/react-dom.min.js?ver=16.13.1:61:14)

I also deactivated all other plugins and activated the default 2021 WP theme, and the errors persist for the custom post type.

4.7.6 was also released yesterday and contains the same hardening to $wpdb->prepare() so that’s still the most likely culprit.

It appears the issue is related to 4.8.2 hardening $wpdb->prepare().

$wpdb->prepare() can create unexpected and unsafe queries leading to potential SQL injection (SQLi). WordPress core is not directly vulnerable to this issue, but we’ve added hardening to prevent plugins and themes from accidentally causing a vulnerability.

WordPress 4.8.2 Security and Maintenance Release

Hopefully this will be fixed soon.