Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
On a Debian 10/Apache 2.4 server I created a drupal 8 multisite with several subdomains defined with a distincts databases in sites/subdomain/settings.local.php
Every subdomain works fine but they all access to the same default database defined in sites/default as if sites/subdomain/settings.local.php files are not read.
I may add that I have others drupal such multisite installs that do work fine.
I was looking to install Drupal on a Bluehost managed hosting account that I have. I created a MySQL database and user, and gave it the correct permissions. I got the screen to fill in the database information, and proceeded with the install. Then, prior to the configure site screen being displayed, I encountered a white screen. Then, when I tried to access the website via the domain name in my browser, I saw the following error on top of a white screen: "The website encountered an unexpected error. Please try again later.".
I'm relatively new to Drupal but have a lot of experience with Wordpress and Expression Engine.
I'm running 2 servers with Drupal 8 for testing. One is a 'test' (TEST) instance and one is a 'production' (PROD) instance. I’ve been using Composer to install updates. They are running on Windows Server 2016 using IIS. I copied composer.json and composer.lock from TEST over to PROD. They were installed using the version 8 recommended project.
I have a content A that references a content B and the content B references a content C. I need a block on content A that lists the content B which it references, that much I've done. But I need the block on A which lists the content B to also list all other content B which has the same reference to content C.
I have a Content Type for "Events", which have a Taxonomy for "Locations". I am defining a layout for single "Events", which should show the field from the "Location" Taxonomy next to the event.
The idea for this is simple: the locations will be used over and over again, and the Taxonomy contains details like GPS coordinates, driving instructions etc. -> all things we typically do not want to have to re-enter for each and every event being loaded into the system.