Multisite

I have a subdirectory multisite.

Subdirectory multisite to access the url is not normal

I can't access subdirectories multisite url path in addition to the frontpage

I can access the frontpage of subdirectory multisite, For example, http://sub.example.com/subsite

But i can't access other url path of subdirectory multisite, For example, http://sub.example.com/subsite/user/login | /subsite/admin/content

When I click login on subdirectory multisite frontpage (http://sub.example.com/subsite) , it shows the page cannot be accessed, it is considered to be the primary site page.

While hosting site with ec2 (aws), the server provides a default Public IPv4 DNS address in the form of i.e.:

ec2-xx-xx-xx-xx.ap-zone-1.compute.amazonaws.com

Now when pointing to this address on a multisite installation, Drupal does not recognize this alias, i.e.

$sites['ec2-xx-xx-xx-xx.ap-zone-1.compute.amazonaws.com'] = 'mysite.com';

and goes to default folder instead.

How to enforce 'mysite.com' in this particular case ?

Right now, more than 700,000 websites are still using Drupal 7. Yet, from November 2021, Drupal 7 and 8 will no longer get updates, bug fixes or security patches. Released in June 2020, Drupal 9 will become the standard platform all organisations must use - but how can you get there?

Join experts from Acquia, Cyber-Duck, SureCloud and The Drupal Association as we talk about the future of Drupal. Discover how, when and why your business should upgrade to Drupal 9. Our webinar will discuss:

Did you ever have a challenge of sharing images between your Drupal sites?

I had a project to do that across Drupal 7 and Drupal 8 sites and came up with idea of building Digital Assets Management platform on Drupal for Drupal. This helps serve images from a single location (can use CDN if needed) and has fluent integration with image styles.

You can see a demo video https://www.youtube.com/watch?v=pKjV7H9GMJM.

Maybe you could be interested in such solution for your sites? Would be happy to share.

Hi,

I would like to introduce Druml (http://www.usedruml.com), which is a Drupal multisite management tool. It simplifies deployments of code and allows to perform various tasks for multiple sites. It can run in multithread mode. It integrates with Acquia. You can also extend it with custom functionality as you want.

I followed this tutorial(Drupal 7) but it not worked for me(Drupal 8):

Multi-site in subdirectories https://www.drupal.org/docs/7/multisite-drupal/multi-site-in-subdirectories

My Drupal is on a Virtual Machine with only access via IP, not hostname.

This is my enviroment:

• CentOs 7 with SELinux(mode: enforcing)
• Varnish 4.0.3
• Apache 2.4.23
• Drupal 8.2.4

I need to create the next structure of sites:

• / <-- First site
• /site2 <-- Second site
• /site3 <-- Third site

In the file sites/sites.php i have:

• $sites['localhost.site2'] = 'site2';

Bonjour,
Ma config sous windows10 avec drupal 7.41 et wampserver 2.5
dans le navigateur lancer "monsite.com:8080" et pas "monsite.com"
sinon erreur "The requested URL monsite.com was not found on this server."

1 - fichier C:\Windows\System32\drivers\etc\hosts

2 - fichier C:\wamp\bin\apache\apache2.4.9\conf\httpd.conf

Hi everyone!,

I'm moving a project from single to multitise configuration (5 sites in total). But now I have to face how manage the configuration in the different sites and at the same time have a maintainable architecture for keep developing new features in the future.

My case is the following:

• Multi-site project where each site have to languages (native one + english)
• Same configuration for all sites (sections, type of contents etc..) But some differences like the language configuration or path pattern for the URLs.

I guess that says it all about the state of Drupal multisite? Disagree?

Or is there some other location where all the action is happening?

I'm curious as to what the best practice recommendations are for maintaining files like install.php, update.php on a multisite server. I'm adding new sites to the installation frequently, but I understand leaving them out there presents somewhat of a security risk that I'd rather not have.

What do others do with these files between site installations?

I'm trying to get a list of user emails that belong to the role 'site administrators' from a remote multisite Drupal environment. When I run the following command:

drush @remote_site sql-query 'SELECT DISTINCT u.mail FROM users AS u LEFT JOIN users_roles AS ur ON u.uid=ur.uid LEFT JOIN role AS r ON ur.rid=r.rid WHERE r.name = "site administrator"'

I'm trying to get a list of user emails that belong to the role 'site administrators' from a remote multisite Drupal environment. When I run the following command:

drush @remote_site sql-query 'SELECT DISTINCT u.mail FROM users AS u LEFT JOIN users_roles AS ur ON u.uid=ur.uid LEFT JOIN role AS r ON ur.rid=r.rid WHERE r.name = "site administrator"'

I've got a multisite installation set up in a subdomain implementation. I've got an SSL certificate on the subdomain and I'd like to make sure all http traffic that comes at the site is redirected to https. My research shows that in normal implementation, an update to the .htaccess file would be the route to go. But since there is a single .htaccess file for the Drupal code, I'm not sure how to make this work only for my subdomain implementation.

Any suggestions?

I'm curious as to whether anyone has set up effective security testing procedures for multisite environments. I'm looking for solutions that will test for malware, penetration, etc. across 50+ Drupal websites. Are there any recommended vendors to work with on this?

I have two existing live sites running drupal 7 (site1.com/en and site2.com/en --> /en automatically selected for english language) and I want to unite them with subdirectory urls with seperate databases. I am following Drupal documentation for installing multi-site#subdirectory. In order to make the symbolic link I need to have ssh access to the server to run the commands. But my hosting service informed me that I am not allowed to remote access. Does anyone know if there is any alternative?

Thanks for the help!

Up to this point the steps I followed:

Hi,

I am maintiaing a multisite setup in Drupal 6. One of the sites in this setup is built in Drupal 7 from start and all content has been migrated in new site.

Now I want to point the site to new Drupal 7 site instead of old one. Drupal 7 setup is not in multisite. How can I do this? Can I just change document root on server ? Will changing that has any impact on other sites? All sites have different vhost files.

Thanks,
Darshi

Is it possible to setup a multisite implementation (either subdomain or subfolder) and then use some sort of redirect to have that content displayed under a different domain name / folder? It's been suggested that I might be able to use .htaccess to do that, but I'm wondering if anybody has any experience in how that might work.

Specifically, I want to build a microsite on site.mydomain.com or mydomain.com/site. But my client's site is theirdomain.com and they want to access the content from theirdomain.com/site. Is this feasible for multisite installations?

I've got to update Drupal 7 core 7.14 to 7.28 for my multisite implementation. I'm currently running about 30 or so sites with a shared code base. I've read the Core Update and the process seems pretty straightforward if I'm doing a single site update. But I've got a few questions for multisite updates:

-- I'm supposed to put my site in 'maintenance' mode prior to copying in the new code base. Does that mean that I have to place each of my 30+ sites in maintenance mode prior to applying the update or is that only required when I run the update.php script for each site?

Hello All,

There is probably a very simple answer to this that I am overlooking; but here goes.

I have taken over managing an existing live site (delucchielectric.com) and need to start working on its replacement.

I've started a hosting account at Arvixe and setup Drupal at a 'dummy' domain and have configured and gotten multisite up and running. A second domain is already running in multisite under that dummy domain.