file_public_path is causing me some huge issues

I've just setup a new site but I'm having a really really strange issue that I honestly have no idea what's causing it.

I've found that when I go into my settings.php, if I leave the $settings['file_public_path'] set to default of commented out, I get the message "The website encountered an unexpected error. Please try again later." I get the same thing if I leave the path as 'sites/default/files'

D8 - Registering Event Subscribers Programmatically

I have a class which implements EventSubscriberInterface. It is registered in the services.yml of my module. From a function in this class, I want to be able to add a different class implementing EventSubscriberInterface as a subscriber.

I've tried using the following:

$dispatch = new EventDispatcher();
$dispatch->addSubscriber(new MyOtherClass());

That doesn't give me any errors, but it doesn't seem to do anything.
Can anybody help me?

TIP: Drupal6/7 permissions setup compatible with DSO (mod_php) 'nobody' web server mode on CentOS+WHM/cPanel under Drush maintenance

Some context

So why might you, if you are operating a cPanel-based VPS for your own Drupal sites, want to consider switching from suPHP to DSO ?

"Your Drupal site got hacked ? Well it's entirely your own fault ! You should always do your updates ! You've only got yourself to blame (and don't dare blame the security holes in that older Drupal code) !!!"

SECURITY CONCERN: reference links: suitability for Drupal CMS of Apache+cPanel+suPHP on single user system (VPS or Dedicated)

First a clear statement; there is absolutely no doubt (based on both personal experience with a compromised pre-Drupal-7.32 site and on a review of literally 100s of discussions of this matter both on and wider WWW) that running suPHP (which forces the web server to run PHP script as cPanel/filesystem user) has serious security implications for all PHP-based CMS systems, including Drupal.

Policy on the inclusion of Migrate in Core for 8.0.0

When the decision was made at DrupalCon Prague to remove the major version (D6/7 => D8) upgrade path in lieu of using Migrate for major version upgrades, we agreed that we were not going to hold up Drupal 8's release on Migrate being supported.

This document provides clarification around this policy. See original discussion at


Finally for some QA. Let's check that our module works as expected by writing a few tests of our own which can be run via Drupal itself.



namespace Drupal\loremipsum\Tests;

use Drupal\simpletest\WebTestBase;

* Tests for the Lorem Ipsum module.
* @group loremipsum
class LoremIpsumTests extends WebTestBase {

   * Modules to install
   * @var array
  public static $modules = array('loremipsum');


Subscribe with RSS Subscribe to RSS - Drupal 8.x