markb1439

You’ll need something (another plugin) to have the stuff configured for you as multisite does not configure plugins / themes out of the box.

Sorry, I didn’t explain myself fully enough. We will configure the themes, plugins, etc., etc. It will be a carefully created environment.

If you’re offering different servers in different locations, then you *have* to have multiple installs.

Right. If we did the “one big install” we know we’d lose this ability.

We’ve been debating a similar equation:

https://www.ads-software.com/support/topic/scaling-strategy

I think our situation is a bit different in that we don’t know how big the whole conglomeration will be, whereas it sounds as if you might have a more finite number of sites.

Of the plugins Andrea mentioned, I’d highly recommend hers. She and her husband are WordPress/multisite gurus, in case you didn’t know already. ??

Hi Andrea,

We’re definitely going with multisite, as we want to offer themes, plugins and other stuff already installed and configured (especially good for novice users). These clients won’t expect cPanel or anything else like that.

So we’re sold on multisite, just not sure whether to put it all in a big basket or several smaller baskets.

One advantage of separate “baskets” would be that we can offer clients their choice of hosting locations (servers in San Jose, Chicago, New York, London, etc.).

Mark

What sort of features do you want your users to have with their hosting packages?

Themes, plugins, performance (via our servers and LiteSpeed), security, etc.

Define stand alone?

Each user will purchase a hosting package and set up their site (kind of like regular web hosting but with the benefits of multisite…plugins, themes, etc.). Each site will be an individual site, and not linked with the rest of the network in any way.

So, since we don’t need the community part, we wonder if we need to put all the eggs in one basket…or if we should build multiple separate installations.

Saying “Complex, expensive setup (especially since it will take a while to build)” with regards to WP MultiSite strikes me as a bit odd. It doesn’t take any more time to build out 700 sites on MultiSite as it would on Single.

We’re not building all the sites. We’re just providing a place for hosting clients to build their own sites. What I meant was that it might be easier to build and maintain a few separate multisite instances, as opposed to creating one giant installation and dealing with all the complexities involved with that. It’s very easy to set up a single multisite installation on a single server.

But it’s much harder to set up and maintain a giant multisite install that spans multiple servers. There are multiple layers of setup and maintenance required just to make the multiple servers work together, not to mention issues of latency when there are separate database servers and data is being moved all around…not to mention reliability issues because a problem on one server can affect everything.

That’s what I was talking about in regard to complexity. Still undecided though. ??

I don’t know if this will help you, but WordPress.com is running on MultiSite.

Thank you. I thought that WP.com runs with multisite, thanks for confirming. However, we’ll be different in that we don’t need to create a community the way WP.com does. Each site in our system will stand alone, and there won’t be aggregated content on our home page, etc.

So that’s why we’re still debating…it’s not as necessary for us to use one giant multisite installation, although we also see the benefits.

Tough choice…any additional feedback would be appreciated. ??

My apologies, apparently my site had somehow been reverted to a backup using an older version of the plugin. With the current version it seems to work fine so far…the fatal error is gone.

Thanks,

Mark

Is this forum the recommended location for support for this plugin?

@LongTail Video, We’re running a WordPress multisite installation, and for the most part we like the way this plugin works. For example, individual users can upload their own licensed players.

But the skins don’t work for the sub-site users, presumably because of the crossdomain issue. However, we don’t want to add a crossdomain.xml file, as this can open us up to various security issues.

Is there another way the plugin could be set up to avoid this problem? Skins are one of the main features we want to offer.

Thanks,

Mark

It’s actually not so hard if you take a few minutes and look over the suggestions. Most of the settings are ideal out-of-the-box, so you really just have to activate it and turn on the caching.

I’ve seen the button take a long time to load…not just in Digg Digg but in general.

In experimenting, I found that the issue can be solved by a simple modification in the plugin…changing the user level required to display the menu. However I am not near my computer with the code on it at the moment. But if you take a look at that part of the code, it’s probably apparent.

Never mind. The Yahoo button URL was timing out. So I deleted it and replaced it with a Google +1 button. ??

You do have to generate the code for each button (which some users won’t find so simple). Even so, I can’t see anything more than the vertical Tweet button. Nothing else appears.

Donncha, thanks for the reply. I see the domain-mapping.php file, but I’m not sure how to utilize this file or get it to do the pruning. Can you guide me a bit? I had turned on the plugin support for domain mapping in WP Super Cache.

Thanks.