Publicize: Support custom post types

[pippinsplugins]

I'd really, really love to see custom post types (at least public ones) fully supported by by the Publicize module.

Are there any blocking reasons to not support custom post types?

[kraftbj]

I believe you can already do that if the CPT has publicize set to true:

https://github.com/Automattic/Jetpack/blob/master/modules/publicize/publicize.php#L345

[pippinsplugins]

Ah, wasn't aware of that.

Just tested and it does work just fine 👍

[jeherve]

Although it is possible to add the Publicize UI to the Custom Post Type editor, posts won't actually get publicized. We still need to work on synchronizing these posts with WordPress.com to push them to Social Networks.

CPT support in Publicize is a popular request, as you can see in the original trac ticket here:

• http://plugins.trac.wordpress.org/ticket/1893

[jeherve]

Also suggested here:

• http://wordpress.org/support/topic/jetpack-publicize-not-working-with-custom-type-posts?replies=1

[blobaugh]

@pippinsplugins does your solution work for all CPTs? Would you mind sharing it?

[pippinsplugins]

@blobaugh I haven't tested anything yet, on my todo list.

[blobaugh]

@pippinsplugins ah. Your previous post made me think you had.

@lezama created a patch that seems to work. e.g: https://twitter.com/blobaugh_dev/status/423953713670004736. It will be in the beta next week and in the next full release.

[lezama]

Just created the 8-github branch with the patch applied, it should support Publicize for custom post types.

[blobaugh]

Did a final test. Looks great @lezama! Merged into master.

[pippinsplugins]

Awesome!

[mattcleg]

Is CPT support now supported for publicize or is the update still to come? Thanks.

[kraftbj]

Update being released later today.

[mattcleg]

Sweet, thanks kraftbj

[jeherve]

As @kraftbj mentioned we plan on releasing the new version of Jetpack later today, but you can already make the necessary changes to your Custom Post Type to be ready when Jetpack 2.8 comes out. There are 2 ways to add Publicize support to a Custom Post Type:

1 - If the Custom Post Type is declared via a third-party plugin or in your theme, you can use the add_post_type_support function (ref) in a functionality plugin, like so:

add_action('init', 'my_custom_init');
function my_custom_init() {
    add_post_type_support( 'your-custom-post-type-name', 'publicize' );
}

2 - If you created the Custom Post Type yourself, you can edit the CPT declaration to add publicize to register_post_type's supports parameter (ref):

// Register Custom Post Type
function custom_post_type() {

    $labels = array(
        'name'                => _x( 'Products', 'Post Type General Name', 'text_domain' ),
        // Other labels here
    );
    $args = array(
        'label'               => __( 'product', 'text_domain' ),
        'supports'            => array( 'title', 'editor', 'publicize', 'wpcom-markdown' ),
        // Other parameters here
    );
    register_post_type( 'product', $args );

}
// Hook into the 'init' action
add_action( 'init', 'custom_post_type', 0 );

[mattcleg]

Thanks jeherve - so just adding 'publicize' to my 'supports' array in the CPT function in functions.php?

[jeherve]

so just adding 'publicize' to my 'supports' array in the CPT function in functions.php?

That will do it, yes.

[mattcleg]

Hey I have the following custom post type and I've added publicize to the supports array but on my test site subscribers aren't getting email notifcation of this cpt. Am i doing it wrong? Any help really appreciated.

//Call for papers custom post type //

add_action( 'init', 'register_cpt_call_for_paper' );

function register_cpt_call_for_paper() {

    $labels = array( 
        'name' => _x( 'Call for papers', 'call_for_paper' ),
        'singular_name' => _x( 'Call for paper', 'call_for_paper' ),
        'add_new' => _x( 'Add New', 'call_for_paper' ),
        'add_new_item' => _x( 'Add New Call for paper', 'call_for_paper' ),
        'edit_item' => _x( 'Edit Call for paper', 'call_for_paper' ),
        'new_item' => _x( 'New Call for paper', 'call_for_paper' ),
        'view_item' => _x( 'View Call for paper', 'call_for_paper' ),
        'search_items' => _x( 'Search Call for papers', 'call_for_paper' ),
        'not_found' => _x( 'No call for papers found', 'call_for_paper' ),
        'not_found_in_trash' => _x( 'No call for papers found in Trash', 'call_for_paper' ),
        'parent_item_colon' => _x( 'Parent Call for paper:', 'call_for_paper' ),
        'menu_name' => _x( 'Call for papers', 'call_for_paper' ),
    );

    $args = array( 
        'labels' => $labels,
        'hierarchical' => false,
        'description' => 'This is the area for adding a call for papers.',
        'supports' => array( 'title', 'editor', 'excerpt', 'author', 'thumbnail', 'trackbacks', 'custom-fields', 'comments', 'revisions', 'page-attributes', 'publicize' ),
        'taxonomies' => array( 'category', 'post_tag' ),
        'public' => true,
        'show_ui' => true,
        'show_in_menu' => true,
        'menu_position' => 20,

        'show_in_nav_menus' => true,
        'publicly_queryable' => true,
        'exclude_from_search' => false,
        'has_archive' => true,
        'query_var' => true,
        'can_export' => true,
        'rewrite' => true,
        'capability_type' => 'post'
    );

    register_post_type( 'call_for_paper', $args );
}

[kraftbj]

Testing/responding via e-mail in 1749169-t

[mattcleg]

Thanks Brandon, do you need me to do anything - not sure what
Testing/responding means. Thanks for looking at this.

Matt

[georgestephanis]

The issue is on the WPCOM end, I believe -- something changed from when @lezama first added 2abcec5 -- we're tracking it down right now. The good news is that the fix should be purely on our end -- once we've got it fixed, no further changes on your side, and it'll magically start working again.

This needs some unit tests so we can catch if some erstwhile changeset messes with it in the future. 💯

[mattcleg]

Thanks George,

Do you have a rough timeframe for this fix at this point? Not being
pushy, my client is nervous and I want to reassure them if possible.

Thanks again for investigating.

Kind regards,

Matt

On 01/02/2014 01:56, George Stephanis wrote:

The issue is on the WPCOM end, I believe -- something changed from
when @lezama https://github.com/lezama first added 2abcec5
2abcec5
-- we're tracking it down right now. The good news is that the fix
should be purely on our end -- once we've got it fixed, no further
changes on your side, and it'll magically start working again.

This needs some unit tests so we can catch if some erstwhile changeset
messes with it in the future. 💯

—
Reply to this email directly or view it on GitHub
#8 (comment).

[kraftbj]

Please note this is regarding the Publicize feature—the auto-publication to social media.

[kraftbj]

As of version 2.8, if adding the CPT via an add_action onto init, please use a priority level less than 10. The Jetpack hook to determine which CPTs to use is running at priority 10 as well, so the CPTs won't be picked up at default priority.

This was improved in SHA 5870427 to catch anything hooked in via priority less than 999, which will be pushed out in the next release.

[boriskuzmanovic]

Thanks @kraftbj, works like a charm.

[khawir]

CPT publicize still not working for me, even after init priority is set to 0. Help! Im on a deadline...

[jeherve]

@khawir Could you send us an email with more information about your site, your CPT, and how you added Publicize support to that CPT?

Thanks!

[khawir]

issues resolved... Thanks