Support » Plugin: Publish To Apple News » Issue with last update & custom post types

  • Resolved jeffmcnear

    (@jeffmcnear)


    the most recent update of the plugin seems to do something that blocks access to the editor for custom post types – where a prompt of “The editor has encountered an unexpected error” is received and the options of “attempt recover” “copy post text” “copy error” do not function. However once we rolled back to ver 2.1.3 the editor functioned normally. Our CPT does include the declaration of ‘show_in_rest’ => true,

    The page I need help with: [log in to see the link]

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Kevin Fodness

    (@kevinfodness)

    I’ll take a look at this and see if I can reproduce. However, what would be extremely useful for me is to see the details of the error message. Does the “copy error” button result in copying the error message to your clipboard so you can paste it? If not, can you open the developer console in your browser and copy the error message from there, please?

    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: https://developer.wordpress.org/reference/functions/register_post_type/#parameters

    Thread Starter jeffmcnear

    (@jeffmcnear)

    my apologies for the delay – I am counting on another member of our team to provide this info and will get back to you as soon as I can

    acegoulet

    (@acegoulet)

    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.

    acegoulet

    (@acegoulet)

    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.

    Plugin Author Kevin Fodness

    (@kevinfodness)

    Great, glad to hear it. I will create a GitHub issue to ensure that the editor doesn’t crash if support for postmeta doesn’t exist for a post type, and to instead display a warning message to the user.

    If you’re interested in tracking progress on the issue, you can follow along here: https://github.com/alleyinteractive/apple-news/issues/884

    Thread Starter jeffmcnear

    (@jeffmcnear)

    Just to comfirm – what you’re suggesting is to add this line to the CPT definitions:
    ‘custom_fields’ => true,
    Am I correct?

    Plugin Author Kevin Fodness

    (@kevinfodness)

    Specifically, when you call register_post_type and specify arguments (second parameter), under the supports key, you need to include custom-fields. For example:

    
    register_post_type(
        'my-post-type',
        [
            'show_in_rest' => true, // Required for Gutenberg.
            'supports' => [ 'author', 'custom-fields', 'editor', 'excerpt', 'revisions', 'thumbnail', 'title' ], // This is a pretty reasonable set of supports, and must include custom-fields for postmeta.
        ]
    );
    
    Thread Starter jeffmcnear

    (@jeffmcnear)

    Yes! that did it!

    Plugin Author Kevin Fodness

    (@kevinfodness)

    Great – glad we got it resolved!

Viewing 9 replies - 1 through 9 (of 9 total)
  • You must be logged in to reply to this topic.