May 17, 2012, 11:08:40 AM *
Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
News: Become a Bigace 3.0 beta tester
 
   Home   Help Search Login Register  
Pages: [1]
  Print  
Author Topic: Multi-site separation  (Read 2875 times)
0 Members and 2 Guests are viewing this topic.
akke
Newbie
*
Posts: 3


« on: January 11, 2011, 11:48:19 PM »

Hi,

I'm coming from cms made simple, and bigace looks like a great cms with smarty and multi-site/language support.

I have a couple of questions regarding multi-site:
Can the other sites be totally invisible to each sites admin/user? So I'm like a "super admin" seeing all sites?
Are there one template per site per extension/module?

Thanks
Logged
Dragonslayer
Team
Bigace Expert
*****
Posts: 376


WWW
« Reply #1 on: January 13, 2011, 07:44:04 AM »

Hi Akke..

There is one "Super-admin" in each community (site)
use this to create other user/admin of your liking

when you install a template or module this is installed to the current community and a "local reposotory"
other community then can install from this to therir community and edit as wanted.. not affecting other communities

i have about 10 communities on my small server
http://dragonslayer.se
Logged

akke
Newbie
*
Posts: 3


« Reply #2 on: January 13, 2011, 11:48:12 AM »

Sounds good!

So if I update a module, this is done to all communities/sites?

The whole idea for me is easy maintenance of cms and a lot of sites with different module setup. Is there a limit besides server HW how many communities you can make in one bigace cms installation? And are the other communities invincible for a lower level user? (Content provider)

Thanks

Logged
Dragonslayer
Team
Bigace Expert
*****
Posts: 376


WWW
« Reply #3 on: January 13, 2011, 04:01:06 PM »

since the communities are seaparated, only the current site and the "local repository" is updated
modules & templates are customizeble per community.
(I'm not sure how addons work)

Other communities is viewable from a "super admin" or a user that have the following rights:
Quote
community.admin: Allows to edit the Community-Domain Mapping for all Communities.
community.deinstallation: Allows to deinstall Communities. SECURITY WARNING!
community.installation: Allows to add new Communities to this installation.
community.maintenance: Allows to edit the Website Maintenance State and Message

Logged

Kevin
Global Moderator
Bigace Guru
*****
Posts: 3045



WWW
« Reply #4 on: January 13, 2011, 09:55:36 PM »

Hi akke,

thanks for evaluating Bigace Smiley and here is my input:

1. There are resources that are shared throughout communities and resources that are community specific. Like Dragonslayer said, a Module is communiyt specific. A template is community specific. Plugins are not, they are stored in a global directory for all communities. Sometimes you have extensions that have both, community specific and unspecific resources.
To answer a question you did not ask: Updating bigger extensions sometimes requires you to update it in all communities. Depends on how it was developed and what has changed.

2. Modules are community independent. Modules could use smarty, but most don't, they just "spit out" plain html.

3. The amount of communities is limited by the maximum amount of an integer on your system. I don't believe that you will ever manage to create so many communities. But to be honest, I never tried to create more than 20 communities in a system. It might result in a performance issue running 200 communities, each of them with approx. 100 user and 15000 pages... as I said, I never tried to find out. Technically there is (beside the max amount of an integer in your Mysql) no limit.

4. I do not understand the question regarding Content provider and an invincible community. But there is nothing like a community that is available to all user. Neither in the frontend nor using the PHP Api. You could indeed query the database directly using plain SQL.
But I am not sure if that is what you were asking Wink

5. Again as Dragonslayer said, the "super admin" of each Community sees all other installed Communities within the administration. He cannot access their database/contrent/users/..., but each of the super-admins can install and delete a Community. This is either a bug or a feature by-design - decide for yourself  - and hey, I am honest here, I hope you do appreciate that  Grin
In most cases you do not want to give away the super-user account. You want to create regular administrator accounts that do not have permissions to access the community administration.

6. You can have as many templates as you want. Each page has its own layout (template) assigned (and inherited from its parent during page creation).

I hope I could help you and would like to welcome you in the Community!

Regards
Kevin
« Last Edit: January 13, 2011, 09:58:37 PM by Kevin » Logged

akke
Newbie
*
Posts: 3


« Reply #5 on: January 13, 2011, 10:29:10 PM »

Thanks for your replies Dragonslayer and Kevin. Got all my questions answered, and then some Smiley

I will install bigace on my testserver and try creating some modules and plugins. About smarty, I really love the clean separation of data and design, but maybe the setup is a bit different than cmsms.

Logged
Pages: [1]
  Print  
 
Jump to:  

Powered by SMF | Simple Machines LLC