Syndicate Out 0.9

Post length: 204 words, almost 1 minute.

More than a year after the previous release of Syndicate Out, this weekend I pushed version 0.9 to the WordPress plugin repository.  Work on this version started in January 2015 and it includes a range of improvements and bugfixes which have been the highest priority requests including transmission of featured images and fixes to improve the syndication of custom meta added by other popular plugins. The full changelog is as follows:

  • Added syndication of featured images (díky Jan at lwd.cz for the majority of this).
  • Added syndication of custom post types & new filter ‘syndicate_out_post_types’ (thanks Martin Burchell and Aptivate).
  • Bug fix to prevent old custom meta data being transmitted (thanks again to Martin Burchell and Aptivate).
  • Fix for API authentication failure when corrections are needed to remote site URL (thanks Brandon).
  • Made some improvements to error reporting when API authentication fails.
  • Added ability to rename syndication groups for greater clarity.
  • Squelch error in new post page for groups with no servers.
  • Made improvements to custom meta transmission to hopefully improve syndication of SEO etc. data.

As always I value the community’s feedback, so please do let me know any problems you encounter or future feature requests in the comments below.

Posted on Monday 11th January, 2016 at 8:04 am in Syndicate Out.
It was tagged with , , , .

23 comments

Is the ability to syndicate out to draft available or on the roadmap? Love the plugin but definitely need to be able to sent these to the other sites draft category so they can be customized before posting.

Posted on 16th Feb 2016 at 9:25 pm by Garret Cleversley.

Currently it only syndicates posts when they are published as published remotely. Is your request to syndicate posts when they are published on the source site as draft on the remote site? If so I already have a feature request for this (here) but have not addressed it. I’ve bumped the issue to look at in the more immediate future. Thanks!

Posted on 17th Feb 2016 at 1:39 pm by Jonathon.

Hello Sir,

All of a sudden the plugin does not authenticate the other blogs. I don’t understand why. I get following error message :
Authentication: Failed.
Unknown.

Could it be a conflict with another plugin ? But I don’t recall having installed a plugin lately.

Thanks for your feed-back.

Jacques

Posted on 15th Mar 2016 at 5:16 pm by Jacques TEVOEDJRE.

Did your blogs update recently? I’m not aware of it not working on recent WP releases, but it’s a possibility.

Posted on 17th Mar 2016 at 5:06 pm by Jonathon.

Hello! I like your plugin, but there is one question: how can I delete the slave site’s posts when I delete the main site’s posts immediately?

Posted on 25th Mar 2016 at 1:20 am by kkmir.

I’m afraid this isn’t currently possible. I started adding this functionality but as yet it’s not complete. See here: https://github.com/confuzzledduck/syndicate-out/issues/26

Posted on 6th Apr 2016 at 9:17 am by Jonathon.

Will be great if there’s a text field to specify the target category to post to.

As of now, it can only work when both source and destination category names are exactly the same? This creates problems when there are more than 1 destination blogs using the same category name (eg. ‘Blog’).

Posted on 15th Apr 2016 at 2:44 am by sylloh.

I like that idea, I’ll add it to my request list. Thanks for your input!

Posted on 19th Apr 2016 at 7:15 pm by Jonathon.

Hello,

It’s cool plugin.

I have a one question!

How to use set tags to slave sites?

Thank you.

Posted on 7th Sep 2016 at 3:44 am by Amumu.

Hi, and thanks. If I understand correctly you’re having trouble transmitting tags from the master to the slave. I think this will be to do with a bug which I have just fixed and pushed to the GitHub Repo.

It will be a few weeks before I push this as an update to the plugin but if you want to implement it yourself it’s quite easy. Find the following line (around line 420) if ( $postTags = syndicate_out_get_tags( $postId ) ) { and replace $postId with $postMetaId. That should resolve your problem!

Posted on 17th Nov 2016 at 4:57 pm by Jonathon.

Great Plugin!

As an FYI, tags were not transmitting between sites for me. I took a look at the code, and found that the call to syndicate_out_get_tags (line 419) was using $postId instead of $postMetaId like everything else in that section. Changing this fixed the issue. Didn’t know if you have a spot for bug reports.

Posted on 17th Nov 2016 at 2:08 pm by Damon Null.

Thanks! It’s much appreciated. There have been a couple of people who have asked why tags aren’t working and I’ve not had the chance to look into it (for almost a year!). I’ve rolled your change into the GitHub Repo so next time I make a release (over Christmas?) that should work out of the box.

Posted on 17th Nov 2016 at 4:53 pm by Jonathon.

Just wondering if this plugin is still supported / being developed?

Looks like just what I need, but no luck trying to set it up. Any sites I add all fail authentication… I tried a few different servers… so I’m thinking maybe a recent WP update has broken it?

Any suggestions on where to start trying to debug … of if I should just skip it for now… would be much appreciated!

Thanks

Matt

Posted on 28th Feb 2017 at 9:02 am by Matt.

It’s still being passively developed. I have a couple of things I was intending to roll out over Christmas but didn’t get the chance. I’ll try and break out my dev environment for this again and give it a spin to see if there’s anything obvious which has broken it.

Posted on 2nd Mar 2017 at 2:05 pm by Jonathon.

Great plugin. Unfortunately it stopped working as of WP 4.7.2.
Authentication failures do not seem to be the main problem.
Mayby xmlrpc has to be addressed differently?

Posted on 8th Mar 2017 at 9:17 am by Horus.

I’m going to take a look at testing it with new versions, so thank you for your report.

Posted on 13th May 2017 at 1:06 pm by Jonathon.

Is there any way to set the URL for images from the WP media gallery that are referenced within the post content to reference the destination blog’s base URL instead of the source blog’s base URL?

i.e. the URL of media reference in the post content should have a URL like:

src=”http://DESTINATION-SERVER.com/wp-content/uploads/2017/03/my_image.jpg

instead of:

src=”http://SOURCE-SERVER.com/wp-content/uploads/2017/03/my_image.jpg

It seems the Featured Image does this as one would expect (i.e. points to destination blog), but the inline images within the post content do not (still point to source blog URL).

Can an enhancement to the plugin be made to achieve this? Or is there a filter or hook I could use to do it myself?

Thank you in advance.

Posted on 13th Mar 2017 at 5:23 pm by Frankie.

Good question, thanks for that. Featured images are handled in a different way by WP, so that explains why it works in that case. I’ll have to take a look at attachments and inline images and see if there is something I can do.

That said, it might be tricky given it’s WP which writes links into the HTML and the sending site (where SO is installed) doesn’t know the URLs of the new site in order to change them. Still, I’ll have a think and see if there’s anything which can be done!

Posted on 13th May 2017 at 1:11 pm by Jonathon.

Seeing a weird behavior where the post slug is being changed from main site to slave site.

For example, I create a post titled “Dog helps with homework” which on main site has a default generated slug of “dog-helps-homework”.

When I publish it, it syndicates to slave site with same title but the slug is changed to “dog-helps-with-homework”. The original post in main site is unchanged.

Any ideas what could be going on here?

Posted on 5th Apr 2017 at 4:50 am by Damian.

Hello
Thanks for your GREAT plugin
i’m using this plugin but i have a problem
the Tags did not add to remote wp
can you help me in this case?

Regards

Posted on 8th Apr 2017 at 8:31 am by Christ.

Hi again
i found my answer in comments
Regards

Posted on 8th Apr 2017 at 8:36 am by Christ.

Following up on my post from April 5th.

The issue seems to be tied to Yoast plugin, or more correctly, changing the default generated slug to something else. If I do that through Yoast as part of SEO tuning or directly in the WP editor, the original default slug is syndicated to the child site. The new modified slug is kept on the parent site.

Wish I could help research myself but I’m very green WP developer so not sure I can spot anything in plugin code.

Hopefully you get a chance to look into it, or maybe display my post and see if a more experience developer can take a look.

Posted on 24th Apr 2017 at 5:26 pm by Damian.

Apologies for the delay.

That’s very interesting. Thanks for your research so far. I know Yoast’s plugin does remove common words from the slug to help with SEO. I’ll take a look, but just to be clear: you want the same SEO tuned slug to be the one the remote site uses?

Three things spring to mind: firstly I’m not sure how the Yoast plugin changes the slugs. If it’s on the fly it might be harder to deal with than if it just saves it. Secondly I suspect the receiving site would handle it’s own slug building, and there are all sorts of different plugins which might modify it so trying to set it might be a bit of a lottery. Finally, I’m not sure if you even can define the slug. I would suspect you can given you can edit it in the default editor, but I’d have to check.

Posted on 13th May 2017 at 1:06 pm by Jonathon.

Leave a comment