Plugin Author
mtilly
(@mtilly)
MyCurator creates a draft post when the article is made live. At that point it is a standard WordPress post and when you Publish it, it is not under control of MyCurator. I would check with the authors of Publicize to see what may be happening as I don’t know how Publicize works. If they have some information that we can add to MyCurator to help, I can work on that.
Hi @mtilly!
I work on the Jetpack team, and I’d like to find out more about the conflict and see how we can solve it.
Could you tell me more about how the posts are created by MyCurator? Do you use something like wp_insert_post()? Could you also let me know what post_status MyCurator posts have once you create them? If you use the future Post Status, how are the posts published later on? Do you use something like wp_schedule_event() to publish the posts?
Thanks!
Plugin Author
mtilly
(@mtilly)
We use wp_insert_post() to add an article to the posts section. We use a status of Draft as default, though there are options to use a status of Publish. We do not schedule any posts.
If you would like, we could continue directly by sending me a Contact Us from our website which I will get.
If you would like, we could continue directly by sending me a Contact Us from our website which I will get.
I think we’re good here, if you don’t mind. This way @trigger61 can follow our conversation!
We use a status of Draft as default, though there are options to use a status of Publish.
Is that a user option? @trigger61 What option do you use when creating posts? Are the posts created as Drafts, or as Published posts?
Plugin Author
mtilly
(@mtilly)
Update: It turns out we use wp_update_post() (which uses wp_insert_post) when we make a post draft or publish. The post is already stored as a custom post type (‘target_ai’) and we change the post type to ‘post’ as well as update content and tags/categories. We also set the date to ‘immediate’ as a default though they can use an option to keep the original date when we found the article.
Saving as Draft or Publish is not an option but is available based on how they make the curated article ‘live’ from our custom post type training page.
The post is already stored as a custom post type (‘target_ai’) and we change the post type to ‘post’
I think that’s what’s causing the issue here.
@trigger61 You could try to add Publicize support to that Custom Post Type and then run some tests. You can do so by adding the following code to your theme’s functions.php file:
add_action('init', 'trigger61_target_ai_publicize');
function trigger61_target_ai_publicize() {
add_post_type_support( 'target_ai', 'publicize' );
}
I can’t guarantee that this is going to work, though, as I don’t know how the CPT URLs are built.
Let us know how it goes.
I’m sorry I’ve been away from this project due to medial reasons. I really don’t get the above. Has there been a resolution to this problem? Surely I’m not the only user of MyCurator wanting to post curated articles to Facebook?
Have you tried to add the code I mentioned above to your theme’s functions.php? Did it help?
I haven’t. I don’t get what this is doing but I’ll give it a try now.
OK I did that and the client went into the front end and got the following:
Warning: Cannot modify header information – headers already sent by (output started at /home2/trigger9/public_html/rod-fly-fishing.com/wp-includes/functions.php:1) in/home2/trigger9/public_html/rod-fly-fishing.com/wp-includes/pluggable.php on line 1179
I tried it and got the following:
Warning: Cannot modify header information – headers already sent by (output started at /home2/trigger9/public_html/rod-fly-fishing.com/wp-includes/functions.php:1) in /home2/trigger9/public_html/rod-fly-fishing.com/wp-content/plugins/wp-super-cache/wp-cache-phase2.php on line 62
Thinking it was something to do with caching it turned caching off and the error message disappeared for me but not him. We are both using chrome. I’ve tried explorer on my machine no error.
That error is indeed a common WordPress issue. You can read more about it, and how to solve it here:
http://codex.wordpress.org/FAQ_Troubleshooting#How_do_I_solve_the_Headers_already_sent_warning_problem.3F
If that code appears when you try adding the code I mentioned above, it’s most likely because you didn’t add the code in the right place (maybe after the closing ?> tag in your theme’s functions.php file?)
Could you give it another try, while making sure you don’t add any extra space or code before or after php tags?
Let me know how it goes.
I’m not sure what you mean by this
Publicize support to that Custom Post Type
By default, Publicize only works with blog posts. It won’t be triggered for Pages, or for other specific Post Types like the one created by the MyCurator plugin, target_ai.
You can, however, use code to enable Publicize for specific Post Types, using the code I posted above.
Let me know how it goes.
OK we are making some progress. Posts seem to be made on Facebook now but I’m not sure that it’s treating the Featured Image correctly. I’ll have a bit more of a play around with it.
I’m not sure that it’s treating the Featured Image correctly
When you share a post on Facebook, or when Jetpack Publicize publishes a post to your Facebook page, Facebook crawls the page and looks for Open Graph meta tags in the head to build a complete post preview (with an image, title, description, …).
Jetpack automatically creates these Open Graph Meta tags for you unless you already use another Open Graph plugin, in which case we let the other plugin handle things.
I would consequently suggest that you check what Facebook sees by entering one of your posts’ URLs in Facebook Debugger:
https://developers.facebook.com/tools/debug
This way you’ll make sure that you correctly provide an image tag with the Featured Image so Facebook can build its post previews.
