Hello to all - Such an amazing project this is

[zets]

Hi there. First time I've heard about Habari was when I started using
WP. I wanted to download some plugin and when visited developers site
I found a message, something like; " I won't develop my WP plugins any
more cause I'll be working on Habari project.". Today, I've decided to
install Habari for my personal portfolio (instead WP) because of it's
beautiful and simple interface. I'm a graphic and web designer... and
don't get me wrong, a big fan of WP, WP Multi-User (WPMU) actually. So
I'm here to ask Habari developers to consider developing a Habari
Multi-User version.

I don't plan to stop using WP but I will use Habari more and more.
Keep up the good work.

PS: I hope that you still except logo proposals for Habari

[drzax]

You can already use a single Habari install to manage multiple
websites. See the wiki for more info: http://wiki.habariproject.org/en/Multisite.

[zets]

I will, thanks.

[zets]

Checked it... maybe I misunderstood it but this is not what I was
after. I don't think it is good option for some blog farm (let's call
it that way) to have different themes installed in different
directories (new bleog = new theme/s). Too much space wasted. They
should be placed inside one directory. Top admin should have an option
(through the Administration, of course) to hide/show them to blog/s
owners. I'm not saying that you must agree with me but I think this
sounds logical. Multiple config files also sounds strange to me but
I'm not really a programmer so I want act smart here.

Cheers

[Andy C]

If I understand your requirement correctly, the multi-user support you
require - multiple authors contributing to a single blog - is under
development and scheduled for the 0.6 release.

[zets]

This is the scenario.

1. One Habari installation
2. Multiple 'child' blogs (every blog has it's own admin/owner):
blog1.mysite.com, blog2.mysite.com, blog3.mysite.com...
3. Top Admin with the possibility to (if needed) to moderate all blogs
4. Top Admin decides which plugins, themes... will be available to one
or more 'child' Blogs admins (blog1 admin, blog2 admin, blog3
admin...) to activate/deactivate
5. New users can be assigned (if the 'child' Blog admin allows them
to) to any blog
6. System I'm describing here is something really similar to
wordpress.com or to be more specific - WordPress MU (http://
mu.wordpress.org/)

[Arthus Erea]

We have most of that already. Just follow the Multisite directions.

On Sep 15, 2008, at 8:53 AM, zets wrote:

>
> This is the scenario.
>
> 1. One Habari installation

Yes, one copy of the source code can run many sites.

>
> 2. Multiple 'child' blogs (every blog has it's own admin/owner):
> blog1.mysite.com, blog2.mysite.com, blog3.mysite.com...

Yes, you can do that.

>
> 3. Top Admin with the possibility to (if needed) to moderate all blogs

Not yet, but we might work on it.

>
> 4. Top Admin decides which plugins, themes... will be available to one
> or more 'child' Blogs admins (blog1 admin, blog2 admin, blog3
> admin...) to activate/deactivate

Well you can put certain plugins/themes in place for only specific
sites by putting them in the /user/sites/foo/plugins folder.

>
> 5. New users can be assigned (if the 'child' Blog admin allows them
> to) to any blog

You can create new users on each blog, but you can't "transfer" users.

>
> 6. System I'm describing here is something really similar to
> wordpress.com or to be more specific - WordPress MU (http://
> mu.wordpress.org/)

I understand... we've had some discussions about this before. I think
now that we have an ACL, developing a better multisite system should
be a priority for 0.8.

One thing I don't think we should do is segment into separate
versions, like WordPress has done. There should only be one Habari
version.

[Blake Johnson]

> > 4. Top Admin decides which plugins, themes... will be available to one
> > or more 'child' Blogs admins (blog1 admin, blog2 admin, blog3
> > admin...) to activate/deactivate
>
> Well you can put certain plugins/themes in place for only specific  
> sites by putting them in the /user/sites/foo/plugins folder.
>

Just to be clear I want to point out that any themes placed in /user/
themes are available to all sub-sites in a multi-site install.

>
> > 5. New users can be assigned (if the 'child' Blog admin allows them
> > to) to any blog
>
> You can create new users on each blog, but you can't "transfer" users.
>

Right, and the reason for this is the that the separate blogs in a
multi-site install don't share users. Each site has its own database.
This is something would could look into changing in the future as the
ACL system develops.

--Blake

[zets]

Ok guys, thank you for your explanations. Possible sharing of users
between separate blogs could be a good thing. I'll give you one
situation. Imagine You have a domain called fewmore.com with
subdomains (blogs) sports.fewmore.com, fashion.fewmore.com,
jobs.fewmore.com... In this case, it would be a cool thing to allow
user to participate in any of this blogs. Next logical step (at least
for me) is to share users on differnt domans (habari installs);
fewmore.com, moreandmore.com, smokekills.com...

> Well you can put certain plugins/themes in place for only specific
> sites by putting them in the /user/sites/foo/plugins folder.

Does this mean that blogs sports.fewmore.com and fashion.fewmore.com
will use plugins from same or separate directories? I think that first
option would be better. It was already done before.

I like Habari a lot:)

[Arthus Erea]

Both. Plugins in /user/plugins are available to all installs. Plugins
in /user/sites/sitename/plugins are only available to the site sitename.

>
>
> I like Habari a lot:)

We're glad. :)

[zets]

I'm trying not to be boring but that's the way I am:) I hope that
someone, except me, will benefit from it. Please have in mind that I'm
aware of the fact that sometimes I repeat myself or someone else.Not
on purpose of course

> Both. Plugins in /user/plugins are available to all installs. Plugins
> in /user/sites/sitename/plugins are only available to the site sitename.

My question is; Isn't it possible that all plugins are placed inside /
user/plugins and none inside /user/sites/sitename/plugins (maybe this
folder shouldn't exist)?
In that case, Top Admin would control which plugins will be activated
and available for all (or only some) blogs and Blog Admin would be
able to decide which plugin he will activated. So let's say you have a
plugin called TagFilter. Isn't it better to have it placed in only one
directory and than decide which Blogs (Blog Admins) will be able to
use it (activate it). No need for multiple uploads, especially when
you expect to have 1000 or more 'child' blogs.

That's all for today. Keep on rockin. Cheers.

[Arthus Erea]

Agreed. However, I don't think this is a priority currently.

We just built our ACL system and that is our priority for 0.6 – this
sort of functionality require a powerful ACL system.

Maybe we can make Multisite a priority for 0.8 - focus on implementing
a "real" multisite system where users are shared and permissions can
be assigned to various blogs.

[Rich Bowen]

++1
I totally agree with the point made here.

--
Whatever you do will be insignificant, but it is very important that
you do it.
Mahatma Ghandi