Should I use MS or not (9 posts)

  1. Zachary Russell
    Posted 3 years ago #

    I am a web designer who is going to be starting a huge project on wordpress.

    I am going to be managing websites for about 500 real estate agencies across the United States. My question is would it be smart for me to install and use the multisite feature so I can gave administrative access to all of my clients, or should I keep all of my sites separate, and then log in individually.

    They will all be sharing the same general things such as plugins (IDX Integration, Yoast, and the like) They will however have different domain names, logins (for my clients) and unique content)

    I will be starting this project soon and I just want to make sure i'm doing this the right way so I don't cause myself any unnecessary confusion.


  2. shirazdrum
    Posted 3 years ago #

    Before even asking this question, you should ask yourself what kind of hosting you can offer. 500 sites on a single install will slow down the hell out of everything if your host can't keep up.

    Do these clients share the themes? If not, a separate installs on separate accounts would be the best way to go since you can modify each account the way you like it. This gives the clients the freedom of doing their own modifications as well. Also if anything goes wrong, all your eggs are not in one basket so you don't have to deal with 500 down sites at one time.

    I'm assuming you have a team of 50 people working on this project otherwise it will take a a century to finish.

  3. Zachary Russell
    Posted 3 years ago #

    Ok I guess your right. I should just do separate installs. As far as hosting what to you recommend for a project of this scale? I obviously don't want a Shared hosting account as I'll get flagged for usage abuse very quickly with that many sites, That leaves me with 3 options Dedicated Server, VPS, or a Dynamic Cloud Server. I am really liking the idea of a dynamic cloud server, because I can increase the processor, storage and ram at any time, which makes it scalable. What do you recommend?

  4. shirazdrum
    Posted 3 years ago #

    Minimum VPS but I would go with DS. I don't have much experience with cloud hosting so I can't comment on that but as far as a good host goes, I use Inmotion Hosting for all my clients and my own sites. With a volume like this, you want the best customer service you can get and Inmotion in my opinion is the best to go with. Of course you can check out the "Official affiliate hosts" listed here: http://wordpress.org/hosting/ as well.

    Stay the hell away from GoDaddy if you value the hair on your head.

  5. Do these clients share the themes? If not, a separate installs on separate accounts would be the best way to go since you can modify each account the way you like it.

    You can still modify each theme for each client how you want with Multisite, actually. And if you use an edit CSS plugin, they can tweak the CSS locally, though not the main theme.

  6. shirazdrum
    Posted 3 years ago #

    For example, I like to modify the login page of the WordPress to match the site. I do that by using the function.php and no plugin. This only works for one theme at a time. Many other modification to the theme individually can't be done only for one site on a network when many other sites use the same theme.

  7. Without knowing what you put in your functions theme, shirazdrum, I can't speak for that, but I know you can style your login page on Multisite :)


    (there's no real diff between a function.php tweak and a plugin, when you get down to it)

  8. shirazdrum
    Posted 3 years ago #

    well this is an example for my own site at http://dreamdare.org/wp-admin

    function change_login_css() {
      echo '<style type="text/css">
        h1 a {
          background-image: url('.get_template_directory_uri().'/images/login-logo.png) !important;
    	  height: 142px !important;
    	.login #login a {
          color: #CCC !important;
        .login #login a:hover, .login #login a:focus {
          color: #FFA500 !important;
        #loginform label {
          color: #CCC!important;
        #loginform input:focus {
          border: 1px solid #FFA500!important;
    	body.login {
    	background: url('.get_template_directory_uri().'/images/darkhive-bg.png) repeat;
    	.login h1 a {
    	padding-bottom: 55px;
    	#login {
    	padding: 84px 0 0;
    	.login form {
    	border: 1px solid #333!important;
    	-moz-box-shadow: none!important;
    	-webkit-box-shadow: none!important;
    	box-shadow: none!important;
    	.login #nav, .login #backtoblog {
    	text-shadow: none!important;
    function change_login_url() {
      echo home_url();
    function change_login_title() {
      echo get_option('blogname');

    the reason I said that is that I like to make themes as light as possible. I don't like function heavy themes, arsenal of plugins and user interfaces for adding header images, or modifying simple things.

    I like to hard-code everything inside my themes so they are unique and not usable for other sites right out of the box, yet they perform as fast and efficient as I like them to be.

  9. shirazdrum - You're definitely one end of the use-case spectrum :) You're not doing anything wrong, but your way is not the only way, and it's best to offer up the multiple paths to possible happiness :)

Topic Closed

This topic has been closed to new replies.

About this Topic


No tags yet.