WordPress.org

Forums

[resolved] Aggregating Multisites (24 posts)

  1. tjasko
    Member
    Posted 4 years ago #

    I know this has been discussed before, but I am looking to aggregate content from one site onto the other. I would like to take all the content from one site and all the content with the other, and create one nice page out of it.

    I've heard of some plugins that'll do this, but quite honestly, I'd prefer to do it in my custom theme than anything else.

    I saw some old posts on this topic (http://mu.wordpress.org/forums/topic/18271), but nothing seemed to work correctly, as pagination didn't even work.

    Does anyone have some recommendations to some code on how to get this done?

    I'd appreciate any help!

  2. I've heard of some plugins that'll do this, but quite honestly, I'd prefer to do it in my custom theme than anything else.

    You don't want to do that. Why? Becuase WordPress multisite was designed to be separate sites like WordPress.com, and once you start making cross-site calls, you will make your server work far harder than it should.

    You want the Sitewide Tags plugin. No foolin. It's the easiest and safest way to do it.

  3. Roy
    Member
    Posted 4 years ago #

    I use this plugin to cross-reference all over the place. New posts in all the subpages sidebars, recent comments and even a newssection with a newsfeed for the entire website. Works perfectly.
    http://wordpress.org/extend/plugins/diamond-multisite-widgets/
    (Don't be fooled by by the name, it's a lot more than widgets in the current version.)

  4. tjasko
    Member
    Posted 4 years ago #

    You don't want to do that. Why? Becuase WordPress multisite was designed to be separate sites like WordPress.com, and once you start making cross-site calls, you will make your server work far harder than it should.

    You have a very very good point. I typically try to code everything myself and to not use plugins, but I see your point on this one.

    WordPress makes quite a bit of SQL by itself, but having it take two tables and combine them together, sort them, and the create the pagination would be tough work on the server... can't agree any more.

    You want the Sitewide Tags plugin. No foolin. It's the easiest and safest way to do it.

    Essentially, it'll just duplicate the posts while linking to the other site... that'll work just fine for me then!

    I use this plugin to cross-reference all over the place. New posts in all the subpages sidebars, recent comments and even a newssection with a newsfeed for the entire website. Works perfectly.

    As Sitewide Tags looks to be more updated than Diamond MultiSite Widgets, I'll take a look at Sitewide Tags then!

    Thanks so much for your help guys! This is exactly why I stick to using WordPress; the community is amazing!

  5. They both work fine :) But Sitewide tags is less server intensive on a big install vs DMW, which is the only reason I suggest it more often.

  6. tjasko
    Member
    Posted 4 years ago #

    I'll use Sitewide Tags then. Since I'm running on a VPS, I for sure have the power, but I don't want it to use too many resources. Thanks so much!

    You know though, this should really be built into WordPress. That would be quite the feature.

  7. Possibly, but I think most people who use MultiSite don't need it, so adding it in would just add feature bloat. Better as a plugin :)

  8. tjasko
    Member
    Posted 4 years ago #

    Trying to set up Sitewide Tags right now... somewhat odd on how it works. Trying to get my posts from blog ID #2 to the homepage on my main blog...

    Hmm.

  9. The folks what wrote and support it are offline right now, but I've tagged this so they can see it when they get back.

    I do know that the 'get all the old posts' feature doesn't work quite right, but it should work for new posts.

  10. tjasko
    Member
    Posted 4 years ago #

    Thanks for tagging the post!

    Hmm, I'll take a look and see if it'll work for new posts. I do need it to transfer every single post over though.

    Essentially, I won't be using the tags page feature, but instead the "post to main blog" feature.

  11. Yeah, that's what most people do ;)

  12. Ron Rennick
    MultiSite Guru
    Posted 4 years ago #

    Download the development version if you want to populate using the existing posts.

    @Ipstenu- Tks :)

  13. tjasko
    Member
    Posted 4 years ago #

    The populating posts feature is taking quite a bit of resources on my server. Ron, is there any easier way to get this done?

    It's using 100% RAM and quite a bit of CPU. :S

  14. Ron Rennick
    MultiSite Guru
    Posted 4 years ago #

    If you turn javascript off in your browser then you can manually click the next button at a slower interval which will reduce the load on your server.

    Another thing you could do is turn off all unnecessary plugins while you are doing the populate. You could have a plugin issue that is pegging the CPU.

  15. tjasko
    Member
    Posted 4 years ago #

    Agh, I'll disable JavaScript and disable all plugins then. Thanks, Ron! I don't see why it should use that much resources in the first place.

  16. Ron Rennick
    MultiSite Guru
    Posted 4 years ago #

    On testing on my dev server it didn't. That's why I thought to add the note about turning off the plugins.

  17. tjasko
    Member
    Posted 4 years ago #

    Turning of the plugins did it... I also updated PHP and Apache because it needed to be updated...

    Yeah, the plugins need to be turned off. Maybe put it in red text in the plugin. It's actually propagating right now and it's going by much faster.

  18. at least you only have to populate exisiting post once. :)

    After that, every time you make a new post they will automagically get sent to the main site.

  19. Ron Rennick
    MultiSite Guru
    Posted 4 years ago #

    Good to know that worked. I'll make a note about adding a note to the populate page.

  20. tjasko
    Member
    Posted 4 years ago #

    @Andrea_r Ha, good point! It was quite the load on the server, but all of them transfered.

    @Ron It worked out very well. One thing to mention, most of the posts it was importing did not add in the permalink custom field data correctly. For the permalink, it included my main domain and not subsite.maindomain.com.

    I was able to fix it by just running a SQL command in the database (replacing "http://maindomain" to "http://subsite.maindomain").

    The propagation worked for a few posts, but the majority were wrong. If there's any more information you'd want, I'd be more than happy to help.

  21. Ron Rennick
    MultiSite Guru
    Posted 4 years ago #

    One thing to mention, most of the posts it was importing did not add in the permalink custom field data correctly. For the permalink, it included my main domain and not subsite.maindomain.com.

    That's odd b/c it runs in the local context of the sub site. I'll see if I can reproduce the issue.

  22. tjasko
    Member
    Posted 4 years ago #

    It is odd. I propagated it again and it added in the permalink custom field this time... very weird.

  23. Ron Rennick
    MultiSite Guru
    Posted 4 years ago #

    Yes, the permalink to the original post is stored in the post meta. The ones you saw may have been from the propagate in the released version which ran in the context of the main site.

  24. dallasm
    Member
    Posted 4 years ago #

    I've seen this issue of the posts not keeping the subdomain permalink prefix, so that a post subdomain.domain.com/examplepost appears on the main blog with a permalink domain.com/examplepost.
    I'm pretty sure it still exists at subdomain.domain.com/examplepost
    As tjasko noted I've seen this feature go away again: maybe its just the propogated posts?

Topic Closed

This topic has been closed to new replies.

About this Topic