In beginning to wet my feet with Drupal8 development I ran into this interesting problem as seen in this screenshot:
Is there some way we remedy this problem, or somehow get more information at the problem at hand to debug and fix it?
If you see this message you might be tempted to try and run: cache-rebuild
drush help cache-rebuild Rebuild a Drupal 8 site and clear all its caches. Aliases: cr, rebuild
But, this was NOT fixing my problem! How vexing!
After some hunting around I found this useful Drupal 8 Settings configuration value for a websites settings.php file:
// Show all error messages, with backtrace information. $config["system.logging"]["error_level"] = "verbose";
There is some additional developer information on the Drupal 8 Site Settings file. Additionally, we can see from this Drupal 8 Update script that we can use keyword level log definitions of: hide, some, all, and verbose.
For a production website I recommend setting this value to hide and using your server side webserver logs to log all PHP errors to a file silently. But, as I note above for a development webserver I recommend setting this value to verbose to gleen as much debug information as possible when developing your Drupal 8 site or modules.
By configuring the system.logging value to verbose and refreshing our page we now see the following output which is 100% more helpful. Happy Coding!
Looking for quality web hosting? Look no further than Arvixe Web Hosting!