A thousand Child-Blogs, getting some posts from the parent blog
Permalink
Allright guys, I have a pretty nasty thing to solve right now.
The agency I'm working at made a somewhat huge project (Huge from my point of view, as a developer and webdesigner).
About 600 blogs at Wordpress, plus 300 more are to be deployed on the next month(s). But wordpress isn't being able to handle that. Multipost already needs more memory, and anyone can predict things tend to get worse when all the 800 blogs are up and running.
So we're all right now trying to find a better way. One guy thinks Python is the best option, let's re-build everything from scratch before it's too late.
I, on the other hand, am a bit skeptical of developing something totally new.
So I wanted to ask, do any of you guys know if C5 will be able to handle the load? I've used C5 for every project I did, and this would be the best opportunity ever for me to make people in the agency start using it. I think it could be a good idea, but I don't know if the load will be too much, on the database, and on the server, meaning, will the PHP be able to hande it?
Basically we need around 1000 (One thousand) blogs, for starters, all reporting to one single main blog. We also need users that can edit just one of those blogs, and a main User that can post on all of them, including the main blog, and make the multi-post available on all blogs.
I'm not afraid of having to develop a plugin, or a dozen plugins, or whatever to make this work, as we're not afraid of spending some money with it, but I don't know that much about the C5 Structure and the PHP. Is it possible to make this work?
An just incase that you guys need a bit more info, WordPress multipost makes new tables (9 of them, more precisely) for every single new child-blog. It also has to write the post (Copying it) on the table of every single blog when you post to all child-blogs. So the load is too much, plus there's a lot of needless replication of content. It started to break.
What would you guys advise me to do?
Thanks in advance,
Fernando Cordeiro.
The agency I'm working at made a somewhat huge project (Huge from my point of view, as a developer and webdesigner).
About 600 blogs at Wordpress, plus 300 more are to be deployed on the next month(s). But wordpress isn't being able to handle that. Multipost already needs more memory, and anyone can predict things tend to get worse when all the 800 blogs are up and running.
So we're all right now trying to find a better way. One guy thinks Python is the best option, let's re-build everything from scratch before it's too late.
I, on the other hand, am a bit skeptical of developing something totally new.
So I wanted to ask, do any of you guys know if C5 will be able to handle the load? I've used C5 for every project I did, and this would be the best opportunity ever for me to make people in the agency start using it. I think it could be a good idea, but I don't know if the load will be too much, on the database, and on the server, meaning, will the PHP be able to hande it?
Basically we need around 1000 (One thousand) blogs, for starters, all reporting to one single main blog. We also need users that can edit just one of those blogs, and a main User that can post on all of them, including the main blog, and make the multi-post available on all blogs.
I'm not afraid of having to develop a plugin, or a dozen plugins, or whatever to make this work, as we're not afraid of spending some money with it, but I don't know that much about the C5 Structure and the PHP. Is it possible to make this work?
An just incase that you guys need a bit more info, WordPress multipost makes new tables (9 of them, more precisely) for every single new child-blog. It also has to write the post (Copying it) on the table of every single blog when you post to all child-blogs. So the load is too much, plus there's a lot of needless replication of content. It started to break.
What would you guys advise me to do?
Thanks in advance,
Fernando Cordeiro.
ProBlog is currently being used for a parent and child blog intranet for over 600 employees, each with their own user blog, and it's performing very well.
We created an "extended" package called "user blogs" that extends ProBlog to automatically set up user specific blogs with a front-end single page profile page for blog management at the user level.
This keeps the site design integrity safe(no page edit mode), while allowing users to manage their blog content.
It really depends on what you want to hassel with? page design permissions? just adding/editing the "content"? Dashboard access?
If you want to chat more, I'd be happy to show you what we have.
UserBlogs is not commercially available yet, and will not be for a very long time. This first enterprise deployment is sort of the proving grounds of usability. So far so good.
Both ProBlog and UserBlog are 5.5 compatible.
The biggest problem in the end, is the search index in my opinion. It's going to get unmanageable. Searching, filtering, tags, and all attributes are fetched via the index. So in your specific case, there will quickly rise a need to keep that lean.
This is a feature absent in the core in my mind. A simple method to shift old index data to a secondary index table. the search block would then be amended to include a "search archived indexing" option, as would the page_list model...ect.
C5 doesn't currently have any solid "archiving" object.
ChadStrat
We created an "extended" package called "user blogs" that extends ProBlog to automatically set up user specific blogs with a front-end single page profile page for blog management at the user level.
This keeps the site design integrity safe(no page edit mode), while allowing users to manage their blog content.
It really depends on what you want to hassel with? page design permissions? just adding/editing the "content"? Dashboard access?
If you want to chat more, I'd be happy to show you what we have.
UserBlogs is not commercially available yet, and will not be for a very long time. This first enterprise deployment is sort of the proving grounds of usability. So far so good.
Both ProBlog and UserBlog are 5.5 compatible.
The biggest problem in the end, is the search index in my opinion. It's going to get unmanageable. Searching, filtering, tags, and all attributes are fetched via the index. So in your specific case, there will quickly rise a need to keep that lean.
This is a feature absent in the core in my mind. A simple method to shift old index data to a secondary index table. the search block would then be amended to include a "search archived indexing" option, as would the page_list model...ect.
C5 doesn't currently have any solid "archiving" object.
ChadStrat
Thanks for the quick reply guys.
I'm considering building a new block for this purpose, setting up one single posts page to avoid the replication issues, and pinpoiting by another mean which posts should appear on which blogs. For this project it seems like the best idea, so we can keep track of everything.
I'll PM Chad and come back when I have more news on the matter.
I'm considering building a new block for this purpose, setting up one single posts page to avoid the replication issues, and pinpoiting by another mean which posts should appear on which blogs. For this project it seems like the best idea, so we can keep track of everything.
I'll PM Chad and come back when I have more news on the matter.
http://chadstrat.com/blog/technology/help-me-clean-out-the-dev-shed...