packjazz

But this is about the plugin….I have the plugin installed on WordPress multisite and the emails are being sent to my WordPress multisite subsite users. I’ll contact the regular support, but these seems like a plugin issue to me, because this issue only happened after I updated the plugin.

Okay, thanks for the heads up! I hate to not update since it was a security patch. I may update and then try to manually add the fix and hope they put it inot the 4.4.2 release.

Yeah, the post type is registered in the theme. But thanks for verifying that the code is right, seems it’s just something funky going on with the current theme. I’ll see if I can find another way to accomplish what I’m looking to accomplish. Thanks for your help!

@ryan – Yes, I’ve confirmed that I’m using the right name for the custom post type, dash and ‘s’ included. And we know what I have is at least partially correct because it does infact create a new DB record any time I publish a custom post of that type. The one missing thing is that the post_id is recorded as 0 instead of the actual id of the post that was published.

I tried that simplified version (which I had tried before in a slightly different configuration) and it doesn’t work. It doesn’t even add a new record to the DB.

I’m starting to feel like this is an issue with how the theme is configured (it’s a complicated membership site set-up that I wasn’t involved in). I’m just having a hard time even knowing where to begin to look to figure it out.

I have tried using ID like this:

function on_jobs_publish( $ID ) {
    global $wpdb;
    $wpdb->insert(
        $wpdb->prefix.'_postmeta',
        array(
            'post_id' => $ID,
            'meta_key' => '_yoast_wpseo_sitemap-include',
            'meta_value' => 'always'
        ),
        array(
            '%d',
            '%s',
            '%s'
        )
    );
}
add_action(  'publish_custom-jobs',  'on_jobs_publish', 10, 1 );

But it didn’t work. It didn’t even add a new record into the DB. At least with $post it added a new record…the only problem is the record’s post_id was 0.

Thanks Erin and Ryan!