• Hello! I’m in the process of migrating the contents of our current server to a new server, and this includes several WordPress sites. I’ve been trying to figure out from the documentation if it would make sense to install multisite or if it is better to use separate WordPress installations. Here are some examples of paths that currently have WP installed:

    /encompass
    /dps/creu/plhg
    /dps/projects/dig_ped
    /dps/projects/dorr
    /dps/publications/sbg
    /fhertr

    Would this be possible/practical to do as a multisite, the fact that installations of WordPress exist at different directory levels? Additionally, there are users that we would want to give access only to the back end of /encompass, only to the back end of /dps/publications/sbg, etc. Or is it best to keep these as separate installations?

    Thank you!

Viewing 6 replies - 1 through 6 (of 6 total)
  • If I understand you well, You are currently running 6 different installations of WordPress on a single domain for different projects. The installations are at different directory levels. You are wondering if you can have multsite and have specific users access specific sites. The answer is all this is possible and you will end up saving lots of resources. But since WordPress has a dubious habit of depending on URLs to resources it needs you will have to do some database clean up as you are going to end up with a few dead links. If you would like, feel free to read : WordPress Multisite vs. Multiple Sites

    Thread Starter rmaxfiel

    (@rmaxfiel)

    Thank you! I’m not sure I follow your explanation of the downsides, can you explain? I also looked at the link you posted. I see that as a downside it says that access to plugins cannot be restricted, but is it possible to activate them on one site but not another, even if the site where I don’t want it to be active has access to the plugin files? I also don’t follow disadvantage #1 about needing to use third party plugins to assign roles.

    I appreciate the help!

    The plugins can be installed across the network but activated on ONLY the site that requires it. It does not have to be activated where you do not want to use it. Same for Themes.

    I just switched from multiple single-installations to a multisite. So maybe i cann tell you my view as a multisite-newbee.

    For me personally the biggest point, which i would consider “negative”, is the more complex administration.

    There are for example some network-wide settings, which don’t look so nice anymore how they did back in the single-site-installation. It’s also sometimes more difficult to keep he overview over .htaccess-settings and -redirects, if you’ve got to include multiple urls into one .htaccess-file.

    But if you’ve got multiple sites, which have a similar theme/plugin-structure and maybe even share editors – then i think a network is easily worth all the potential hassle.

    Thread Starter rmaxfiel

    (@rmaxfiel)

    Hi! I’m working on installing this now, as a multisite, but was wondering what I need to do to install the core files in /wordpress while having the different sites at the locations I described before. It would definitely be convenient not to have the core files cluttering up the root folder, but I would like to be able to keep the sites at their locations of /encompass, /dps/publications/sbg, etc. Thank you!

    Thread Starter rmaxfiel

    (@rmaxfiel)

    Any advice? ??

    I’m also currently not able to access the dashboards for either of the test subsites; I get a redirect loop. I had tried editing wp-config.php to define WP_HOME and WP_SITEURL per advice elsewhere, but nothing changed, so I commented it out.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Multisite: why or why not’ is closed to new replies.