Can uBlogsy be used in a multi-site environment to allow some sites to have a blog and others not to have a blog. And keep the blog posts separated by site?
Thanks Anthony, Unfortunately I don't think I can have a different tree per site. All of these sites are a group of related agencies that are all in the same business thus they share a good deal of required functionality as well as common web resources. But each site has different ownership. And must be kept completely separated from every other site.
We have 7 live sites now and we have another 8 in the works. And currently they are all in the same tree. How difficult would it be to separate them into separate trees? Does a separate tree mean a separate database?
Anthony, Thank you very much for your help. I really appreciate it.
We currently have 13 active sites in the one umbraco installation. A few of the sites want blogs but not all. We have to make sure the posts are kept separate between sites.
Below is a tree representation of our current set up. I'm not familiar with ublogsy, do I install it into umbraco one time as most of the plugins do? Then how do you set it up so that Site A and Site B have a blog but not Site C. And Site A blog posts don't show up in Site B's blog? I realize "How to do you set it up" is a broad question but any pointers you can give me to save me stumbling around trying to figure it out would be really helpful.
While this will work, note that the urls will still be e.g. /posts/2012/hello-world which means the two can collide. To solve this, put them under a (for example) homepage with the same name as the blog. The only practical difference will be (i think) that now, the urls will be /ublogsy-a/posts/... and /ublogsy-b/posts/...
Content uBlogsy A <- Homepage (empty) uBlogsy A <- Landing page uBlogsy B uBlogsy B
The landing page keeps its url (/ublogsy-a both before and after).
Can this package be used in a multi-site environment?
Can uBlogsy be used in a multi-site environment to allow some sites to have a blog and others not to have a blog. And keep the blog posts separated by site?
If you have a different tree per site in the Umbraco content section then yes.
Thanks Anthony, Unfortunately I don't think I can have a different tree per site. All of these sites are a group of related agencies that are all in the same business thus they share a good deal of required functionality as well as common web resources. But each site has different ownership. And must be kept completely separated from every other site.
We have 7 live sites now and we have another 8 in the works. And currently they are all in the same tree. How difficult would it be to separate them into separate trees? Does a separate tree mean a separate database?
multiple ublogsy's will work if they are roots of different subtrees..
I assume you want this:
content
- main node
- site 1
- ublogsy
- site 2
- ublogsy
that should work just fine.
Anthony, Thank you very much for your help. I really appreciate it.
We currently have 13 active sites in the one umbraco installation. A few of the sites want blogs but not all. We have to make sure the posts are kept separate between sites.
Below is a tree representation of our current set up. I'm not familiar with ublogsy, do I install it into umbraco one time as most of the plugins do? Then how do you set it up so that Site A and Site B have a blog but not Site C. And Site A blog posts don't show up in Site B's blog? I realize "How to do you set it up" is a broad question but any pointers you can give me to save me stumbling around trying to figure it out would be really helpful.
Thanks so much for your help
Your site structure will work fine.
Would like to add, or possibly clarify something.
While this will work, note that the urls will still be e.g. /posts/2012/hello-world which means the two can collide. To solve this, put them under a (for example) homepage with the same name as the blog. The only practical difference will be (i think) that now, the urls will be /ublogsy-a/posts/... and /ublogsy-b/posts/...
The landing page keeps its url (/ublogsy-a both before and after).
Took me a few minutes to realize this :P
is working on a reply...