By standardhuman on

I'm building a community site for my co-workers of the company I work for. Constructing one site for one store location is no problem, but we have about 90 stores nationwide and each really needs their own. Ideally the site would have all of the following features:

A single common front page containing public info (no login required) and login fields.

Upon logging in, users would be directed to the site of the store at which they work.

About 90 individual full sites with identical structure but unique content.

Each of these sites are accessible only by the employees of that store.

Each store would have it's own site moderator (of course).

I would be able to admin all sites as well as individual sites from one location.

Is this possible without any custom scripting and 90 separate installations?
This would be huge leap in fostering community and organization amongst us workers.

Many thanks in advance!

⋅ Categories: Drupal 5.x

Comments

dman’s picture

dman commented

That's what multisites are for.

You probably want to go even further than that and figure out which elements you want to be common across them all. It will look a bit complicated, but you can use table prefixing to maintain seperate node content and user bases, whilst using a common taxonomy - if appropriate.

Or you can attack it from the other end and try just organic groups to maintain individuality.

Just today I was putting together a portfolio of sites, and wondering what, if any advantage there was of setting it up as multisites when there was zero common elements between them. If you DO have a lot of common needs, then it's the way to go for you.

.dan.
How to troubleshoot Drupal | http://www.coders.co.nz/

.dan. is the New Zealand Drupal Developer working on Government Web Standards

standardhuman’s picture

standardhuman commented

Thanks dman. I was wondering if organic groups would be the way. What's your opinion on using CiviCRM for this purpose?

journaltimes’s picture

journaltimes commented

Starting the multi-site thing, sharing modules and such is opening a BIG can of worms, unless you have a great host, or you know a lot about .htaccess files, configure.ini files, or php.

I ran through every post many, many times on the subject. I went through the handbook, and posted many times.

After much struggling, it comes down to my host's servers not set up properly for symlinks. At least, not a very user friendly way of settin them up.

I gave up, and now I am forced to set up 30 some web blogs with seperate code bases sharing database tables. It is really going to stink upgrading in the future.

aangel’s picture

aangel commented

Hi, jerry.

Just found this: "Multisites for Dummies"
http://drupal.org/node/107347

Andre

journaltimes’s picture

journaltimes commented

I read that thread lots of times.

I ended up in private conversations with CogRusty (the main contributer to that thread). He helped me a lot.

In the end, I found that my host's servers weren't set up well for my symlinks (it's a whole thing:)).

Now my superior's have put the kibosh on Drupal for now (not because of my multi-site issues).

I am going set up my own multi-site privately. I love Drupal, and I am not giving up on it.

Go Drupalers!