multisite

Hopefully i am not repeating a question, but i have not found this same issue in my searches thus far.

The site in question is live, it is set up as multisite but we are only using one domain. Since everything worked well on my local installation and the testing server, I saw no reason to change the setup.

I have done a bunch of research but could use some advice on whether a multisite installation or the Domain Access module is more appropriate for my needs.

I am setting up two sites for a public school and the grassroots nonprofit that raises money to support the school. They will need the following capabilities: (My impression of whether this tips the scale one way or the other is in parentheses - feel free to correct me)

I have investigated Drupal and multisite capabilities through numerous sources and experienced users of Drupal. At all turns, I am told Domain Access is the module we need to use to meet our needs.

Our needs are basically this:

(1) we want a single code install of Drupal (don't have the resources to keep multiple copies up-to-date and in sync with each other)
(2) we have shared server running nearly 100 websites and web apps of varying sizes and complexities
(3) some of the ~100 sites will get converted into Drupal for better CMS capabilities

I am looking at creating several mostly-unrelated sites using Domain Access. (The reason to use DA rather than core multisite is mainly to minimize admin overhead.)

I would like each site to have a separate feed. I'd also like to have a combined feed from all the sites, displayed as a block on each site.

Is this something I can do with DA?

I am using FeedBurner. Does that add any problems/complexity?

Hi,

Want to use multisite with some control panel on low-memory VPS, ok, lets say any server, wich has some kind of hosting control panel like Plesk, CPanel, Directadmin or any other. Prefer CPanel, but as I am using ~10% of it's features, almost any decent one is ok. The onli administrative person will be me.

I've got a site that I just ported from a local environment to a remote testing server. Everything is working fine except that an image that I put in a block does not show up! I have checked the path; all seems correct, and the permissions on that folder are 755 and 777 for the image itself.

The only way this site is different from others I am working on is that it is set up as a multisite.

I have my path set up as "sites/domain.com/files/image.png" (where it is), with all spelled correctly.

Hi,

I am hoping you can help me. I work for a university and have recently been assigned to a project working with on-line community portals built using Drupal. I am trying to set up a sandbox system that I can play with, so that I don't mess up the actual sites. The problem I am having is setting up multisites using the same code base. I can get a single site set up and running just fine, however every time I try and set up multisites everything stopes working. I have followed all the instructions I can find on-line including these from the Drupal site:

I have a question about a multi-site folder setup, and bazaar workflow.

I'm thinking of setting up a bzr repository for each individual site, and then a repository for the sites/all folder, plus one for core. Does this sound like an acceptable way to do it?

Then, onto the symlinks:

Firstly, is it best practice to store each individual site folder as a symlink?

For example, say this is my sites folder:

sites
-all
-default
-site1.com
-site2.com

I am currently using git to manage my site-specific projects, e.g. code that lives under /sites in a multisite (single core) scenario.

However, I find myself needing to work on two things that will require a separate repository tracking the Drupal core: 1) one-off core patches, and 2) install profiles.

I can't think of a better title sorry...

I'm using the (excellent) Domain Access module. One thing I'm doing is aliasing sites. As an example.co.uk is aliased to example.com. So going to example.co.uk/foo is identical to going to example.com/foo.

However, there are one or two pages (in a large site) which I want to be different. So example.co.uk/contact would go to a different page than example.com/contact.

The "easiest" way (if horrendous in some respects) seems to be to add code (to theme_preprocess_page? to settings.php? custom_url_rewrite_inbound?) that says: