Whenever I look at "Should I use Multi-site?", it always seems to depend on the use case. (I am using Drupal 7)

I have been developing a company's Intranet on a single Drupal install and it is getting larger and larger.

I have about 75 Content Types and over 500 fields.

The reason for the Drupal site having so many Content Types is to give each department access to manage nodes within specific content types. (Using Content Access).

There are also additional Content Types for workflows that are using with Rules.

I feel the greatest performance hit when managing fields on a Content Type. Other than that, the site still runs smoothly.

In a situation like this where there are going to be so many more fields and content types added, does it make sense to use Multi-site instead? Or is it perhaps the specs of my Server that are causing the slowness?

It is convenient having everything on one site since I can have a unified Dashboard, not have to re-make the User groups/roles on multiple sites, etc.

In this use case, is it worth converting my structure to a Multi-site setup?

  • which drupal version you are using? – Yuseferi Feb 24 '17 at 18:44
  • Hi @Pierre.Vriens. Thank you for your response. More information has been added as to why there are so many content types – AndrewMRiv Feb 24 '17 at 19:13
  • 1
    If a rebuild was as option, I'd re-use fields with the conditional fields module and a single pre-populated entity reference back to a home node for each department. Or a full blown Organic Groups solution with the same idea. – Niall Murphy Feb 25 '17 at 17:12
  • 1
    Yeah, in that case, OG is good. I managed to go from around 20 content types down to 3 for my OG content using Conditional fields. (2 of them are very heavy and rarely used). – Niall Murphy Feb 28 '17 at 0:07
  • 1
    I did it by creating one taxonomy vocabulary and many terms for all of the "psuedo content types". Then I referenced the terms in an entity reference field and configured conditional fields. As an extra option, I used drupal.org/project/entityreference_prepopulate and built custom links using tokens/php around my site so teams never even see the entity reference field. – Niall Murphy Feb 28 '17 at 0:13

Another alternative you may want to consider is to start using the Group module, which allows for creating arbitrary collections of your content and users on your site, and grant access control permissions on those collections.

Group is available as of D7, and has a D8 version also. It is designed to be an alternative to Organic Groups. The Group module creates groups as entities, making them fully fieldable, extensible and exportable.

For more details about the various types of roles used by the Group module, refer to my answer to "What are the various roles supported by the Group module?".

And because Group also integrates with the Rules module, you could probably transform your workflows related rules toward Group equivalents.


Not the answer you're looking for? Browse other questions tagged or ask your own question.