Jonathon Wardman

Hi Jonathon,

This looks like a great plug in – but before I download and donate – please can you let me know it will do the following (sorry, I can’t dechire an explicit answer from your notes):

I run one wordpress CMS which contains a blog as well as several pages, and is hosted with Go Daddy on a share server. If I want to replicate this site (using exactly the same theme), x ten but don’t want to have to add/copy and paste, the same new blog post each time to the nine new sites. Will Synidcate Out allow me to authmatically ‘push’ a new post out the other nine new blogs automatically and is it possible to configure it so that the format is exactly the same for each site?

Please clarify – many thanks in advance.

Hey Jonathan, great plugin!
The issue I have had is
If I have a blog with a post in:
Computers > Games
and a second blog which it sends to, with 2 categories:
Games
Computers > Games
The article ends up in Games and NOT Computers > Games

Secondly another really useful function would be that if it cannot find a category for the post in the receiving site, then the post is NOT submitted to the second blog.

Are these two possible to add/fix?

Another issue, I have just noticed is that the article is posted by the user account associated with the Syndication plugin, rather than the original. Is this a limitation of wordpress/xmlrpc? A workaround I used was to create an additional field, and enter the author name there (and use the get_post_meta). It might be a case that the only way round this is to have a plugin on the receiving wordpress blog! Not sure if this may be a little bit off the original intention of your plugin tho. I have an example plugin for the receiver end that I found on another website if it is of interest to you.

Any chance to get this working in WPMU? I am kind a noob but what url do I use? .com/xmlprc.php? or?

Hi Jonathon,

Is there anyway to configure this plugin to post an excerpt and a link back to the original site of publication, rather than just repostint the entire original post?

Thank you for creating such a handy plugin!

I have a suggestion for a feature that stems from my particular use of Syndicate Out, but others may find it helpful as well.

I have two blogs; the first was created on WordPress.com, the second is self-hosted and is now my primary blog.

Since my blog on WordPress.com still gets a few hits and I’m reluctant to orphan that blog completely, I’d like to syndicate articles originating from the new self-hosted primary blog to my WordPress.com blog, but not in their entirety.

My suggestion would be to have an option in Syndicate Out that will publish to the destination blog just an excerpt of the article, and a modified “Read more” break that links back to the source blog.

If an excerpt does not exist, one is dynamically generated according to the first “X” number of words as specified by the user.

I’m currently accomplishing the above task by using an intermediate aggregate blog which formats the incoming articles in the manner specified above (using an RSS plugin with the above described feature) before passing them on to the WordPress.com blog using Syndicate Out.

If Syndicate Out incorporates this feature, I could eliminate the intermediate aggregate blog altogether and syndicate straight from the source/primary blog to the WordPress.com blog.

Hello! What you need to add a script that, when Crossposting remained a link to the original post?

Hi Jonathan,

thanks for your great plugin, which we are testing right now pushing posts to a Drupal based xmlrpc.php.

I have a question about the categories: We need to transmit values from a “custom field” in WordPress, which we are using to identify / categorize the post on the remote site.

In our RSS Feeds we just used e.g:
$key=”BANANA-ID”; echo get_post_meta($post->ID, $key, true);

Do you know, how resp. where i have to modify the code to get this done with your plugin ?

Thanks in advance,

MCm

It isn’t working with WP MU subdomains. Example:

a.bcd.com and b.bcd.com

I added a.bcd.com and then checked with a test post. It worked. Now I add b.bcd.com and put up a new post. The post got syndicated to b.bcd.com and failed at a.bcd.com.

I do not understand what problem this is.

Hi Jonathon,

I am using this on WP multisite 3.0 and it seems to work perfectly. The only issue I am having is that when I click the button to add a new server, nothing happens except a message that says “settings saved”. I can add groups no problem, just not new servers to an existing group. Any ideas?

Hi, Looks like a useful plugin – thanks for posting it. You say you “Reworked the decision making logic around new and edited posts” – could you clarify this area. Is there a way to make it syndicate old posts, and what happens if I edit a post. Thanks

Hi, Is this supposed to work with the latest wordpress? (3.1)? I have the latest install on both blogs and cannot get this to work. I have tried putting in FTP information, administrator info, and author info, or all at the same time. Nothing I do works. Any suggestions?

hi,Jonathan.i like your plugin.but does it can sync comments such like xpost plugins do?i have try the xpost plugins,it can sync the comments,but it can’t working like your plugins do that A-category to A blog,B-category to B blog.can u explore the sync comments?thanks and sorry my poor english

Hi Jonathan. Great idea for a plugin! I was searching for a way to do exactly this for WP multisite, so I could set up a blog to use as a search engine for the site members. However, there’s some things I need it to do, such as being WP 3.1 compatible and syndicating pages, comments and pretty much anything else that can be synced 🙂 My project has a budget so next time you go to do enhancements, I’d like to talk to you about supporting your work on the new features. You can email me at my antispam address and I’ll reply with a regular one 🙂
Just FYI, re Ming’s question about comments, I found they are supported under XMLRPC as of WP 2.7 – https://core.trac.wordpress.org/ticket/7446.

Thanks for making this!
David

Hi Jonathan!
This seems like a great plugin and I am pleased to tell you that it works with WordPress 3.2. Thanks for your efforts!
However, I am having problems getting this plugin to push out posts that are created with either WP-O-MATIC, WPeMATICO, WP-ROBOT, or others.
It will push out posts that are fetched (from feeds) manually, but not on a cron job. If you could give me some guidance as to where to look, I might be able to fix this, since I can code in php.
I’m really not even certain if the problem lies with yur plugin or the others and how they create posts.
Thanks in advance,
Brian

Thanks for your reply Jonathan! I think trying it with wp-o-matic would be the best bet since it is so popular (although not really supported by the author anymore). And wpematico is, supposedly, based on wp-o-matic, according to the author, but he’s storing his data in the wp-options table, which wp-o-matic doesn’t do.
I’m wondering if it has something to do with a user with posting privileges being logged in, since all posts get published via a cron, but only the posts that are manually fetched in admin are pushed out via rpc.
Thanks for your help on this, Jonathan.

I probably should have explained my scenario. I am trying to fetch and post articles from one “dummy” server to another “live” server. I am doing this because of memory/processing constraints. This is for a non-profit charity (Mohandas Gandhi’s family) and they have financial constraints, so a dedicated server/virtual private server is not an option. I hope that makes sense. This works well this way, but not using cron.
I hope that this makes sense. Yours is the only WordPress plugin that I could find that even approached what I need.
Thanks again!
-Brian

Hi Jonathon,

I’d first like to echo how thankful I am to you for making this plugin. There just isn’t anything else like it.

I can confirm what Dr. Brown mentioned about the plugin not pushing out certain types of posts. Basically, anything published by any other means than the “regular” way of creating posts won’t get syndicated. For example, a post scheduled to publish at some point in the future, or a post created by another plugin.

If a post created by a plugin is created to be in “draft” status, and you then manually change the status to “published” in the admin, the post is syndicated upon the status change. So that’s a bit of a workaround – just create posts in “draft” status and then manually edit the status in the admin. However, as I mention above, it only works for posts that will go live as soon as they are published – not scheduled posts.

So if scheduled posts could be syndicated when they are created, that would get you very far down the right road, I think. Then, the remote blog would publish them at the proper moment.

As to the question of a user being logged in, I don’t believe that helps. I’ve been logged in on both blogs and the posts are not pushed out.

Thanks again for all your work on this great plugin!

jonathan, great plugin. is there any way to make WP’s “Read More” link to the originating blog?

In other words, we’re trying to cross-post just the intro text from one blog to another. We want the ‘read more’ link in a post to point to the origin blog. make sense?

Jonathan,

This plugin rocks – quick question. Syndicate out seems to only work when the user at the remote blog has the role of administrator. Is there a way to make it work with lesser user roles as to let post get reviewed at the target blog before actually being published?

Hi Jonathan –

I like you plugin a lot and have used it for a while now. There is only one thing missing: the possibility to add a line at the bottom after the content where one could fill free text or code (like a copyright line with a link to the original post). If you could build that into the next update, that would be really great and I would appreciate it! (I honestly hope there will be more updates after all this time!)

By now I add that line manually at the receiving blog each time after a post is made. However, every time an update is made to the original posting, the line is gone again…

Can you help?