confuzzledduck

To address the points from your seconds post (as I see you realised your error from the first):

1) Are the posts saved on the receiving blog with the date they were syndicated rather than the future date set in the source blog? (While I know it doesn’t solve the problem with the plugin, you could always change the schedule for each post on the receiving blog which has an incorrect date so you don’t have to remember to publish them.)

2) I’ve not had any reports of tags not being copied if posts were. I’m not sure why that would be.

3) There is currently no way to syndicate old posts. This is a popular feature request but has not yet been implemented. (https://github.com/confuzzledduck/syndicate-out/issues/8)

With regard to the SEO data: I’m pretty sure this is because these plugins use additional metadata which isn’t getting transmitted. I need to look into this further and have it on my todo list (https://github.com/confuzzledduck/syndicate-out/issues/13). While these things are high on my list, I’m afraid I don’t have a timescale for them as I have to fit maintaining and developing this plugin in to my own time and I don’t get any compensation for doing so.

It should do. Do you know if the taxonomies and tags already exist on the target blog, or if they should be created? Do you have any other plugins installed on either blog which might do things with taxonomies and tags?

There have been some other people who seem to be having problems with this too, so you’re not alone, but I’ve not managed to reproduce the problem myself and it’s hard to fix without being able to test it!

I’m not aware of any problems specifically relating to WordPress 3.9, so I believe it should!

abisoman: Do you mean all your posts end up on the remote blog as drafts rather than as published posts, even when they are published on the source blog?

dmkjr: On the other hand a few people have asked for posts to be pushed as draft regardless of the status on the source blog. I do intend to add an option to allow syndicated posts to be either the status they are on the source blog OR something specified in the plugin settings.

I am also sad there aren’t any other plugins — means more work for me! And of course a bit of competition is healthy ??

I want to address the media syndication issue in the next release, but thanks for the bump ??

The plugin shouldn’t be syndicating pages at all. Can you check the latest release of the plugin (released today) as there are some changes to the syndication algorithm which might address the problem. If not then I’ll take a look!

It should be working by default, but it’s possible there’s a bug which is preventing the data going with the post (someone commented on this with regard to another plugin not so long ago). I’ll check this out.

Thanks for the feedback. I’ve released a new version just now which is worth giving a try, although I’m not aware of having addressed that issue.

If the problem is still there, can you check the date of the posts on the remote site, please? Does that reflect the future date, or the point at which it was syndicated.

I don’t see any reason why it wouldn’t work with sub domains, but I’ve not tested that specific implementation. I’ll give it a try and if I can reproduce the problem try and figure out a fix. Thanks for reporting it.

Good to know, thanks for testing it out. I’ll push those changes to the plugin repo shortly.

You just need to put the main website address — in this case mrdad.com — and the categories will behave as set up in the plugin itself (ie. will be transmitted or not).

There currently isn’t a way to have posts arrive as drafts on the recieving blog, but it’s certainly something I’d like to implement on a server-by-server basis in the not-distant future.

I think I found the bug — nesting issues with the array sent to the remote sites.

Can you download and install the version of the plugin from here: https://github.com/confuzzledduck/syndicate-out/archive/efa89c4edfcd7510eaed364362f133984d03c2d1.zip and let me know if that has fixed the problem for you, please?

The plugin should be installed on the sites which SEND the posts. The servers you then add to the plugin configuration are the sites which you want to RECEIVE the posts.

Therefore in your case you’d need the plugin installed on both talkingaboutmenshealth.com and parentsatplay.com with the details of mrdad.com in the configuration of them both. This would mean that specified posts on each of those sites would get sent to the mrdad.com site as you want.

I am planning to overhaul the readme, help and instructions for the plugin as I’m aware they are currently a little lacking. In the meantime if you have any other questions then do let me know.

Thanks for reporting that. I’ll take a look and let you know what I can find.

If it stopped in the first day or so of this year it’s probably a bug which got introduced with the latest update. Sorry!

If you click the “Save settings” button right at the bottom while you have some of the rows’ check boxes selected, those servers should be deleted.

It’s not clear so I’ll look at making it a bit more obvious what to do in a future release. Thanks for asking the question ??