I am trying to get Drupal 8.1.6 running on my Fedora 22 Linux system and am seeing a problem that I have never run into before.
I have been through both Drupal 6 and Drupal 7 on this same machine and they both installed as expected. After a long break I came back tonight and wanted to just blow everything else away and install Drupal 8 so I:
I'm hoping someone can help me with my Drupal 7 clean URL issue. I've spent hours trying various things from the forums with no luck. Hopefully someone can tell me the problem.
I have a subdirectory multisite. Clean URLs are working fine so that an href="2" html will take me to /site/node/2, etc. And as I select various navigation menu tabs, I'm properly routed to the various /node/id pages.
I have migrated a Drupal 7.x install from a hosted environment to an self hosted environment. Drupal version and Mysql version have been confirmed to be the same.
When I try to access the config page from within the admin menu as well as the database update page after updating the modules, I get a blank page.
We've started a new open source initiative Docker4Drupal.org. As you can tell from its name the idea is to help developers adopt docker containers. The GitHub repository contains docker compose file that can be used to pull and run containers. All containers use public images (official or forks) and pre-configured to work with Drupal.
I had version 7.44 running on my Drupal testbed Web site. I was using PHP version 5.4 and My SQL version 5.5.48-37.8.
When I got the notice that 7.50 was available, I performed the upgrade in the standard way (deleted all files and directories in the public_html directory except for the sites directory and then uploaded all the new files and directories except the sites directory).
I was getting 500 errors when I pulled the site up with my browser.
Last week I got a dedicated server and prepared an openvz container to be ready for Drupal 8 (MySQL + Apache2 + PHP). The idea was 50 jailed users could access remotely and install Drupal 8 via Drush simultanously and browse their Drupal websites.
What happened was a bad user experience caused by server overload. Server specifications are: Debian 8 (openvz container), 12 GB RAM and 8 cores.
The funny thing is that similar configuration for Drupal 7 goes like a charm.