Nearly every contrib module I have installed recently on Drupal 8.0.5 has resulted in a common error, two of which I have posted below:
Symfony\Component\Routing\Exception\RouteNotFoundException: Route "colorbox.admin_settings" does not exist. in Drupal\Core\Routing\RouteProvider->getRouteByName() (line 191 of /srv/bindings/0525bb0972474be1853f53b3bf4b631e/code/core/lib/Drupal/Core/Routing/RouteProvider.php).
Symfony\Component\Routing\Exception\RouteNotFoundException: Route "m4032404.config" does not exist. in Drupal\Core\Routing\RouteProvider->getRouteByName() (line 191 of /srv/bindings/0525bb0972474be1853f53b3bf4b631e/code/core/lib/Drupal/Core/Routing/RouteProvider.php).
I have had no problem installing these same modules on my local environment before pushing them to the development Pantheon server. I have experienced the same error with search404 and pathauto. In the case of search404, it has seemingly affected functionality of the module, though no other contrib modules have so far experienced any adverse effects from what I can tell.
There is a similar issue posted to the Drupal Sitemap module which is quite
similar to mine and has not yet been resolved:
https://www.drupal.org/node/2601676
Also, glancing at response #3 in the following:
https://www.drupal.org/node/2588511 I wonder, is it possible that the
module expects a different path than is being provided on the Pantheon
environment? Perhaps the error stems from an invalid path structure which
lacks a forward slash or something trivial like that? Maybe this is an
issue which module developers should be made aware of, or which Pantheon
can reasonably accommodate? Just speculation, but I can't imagine what else
could be different in the Symfony routing between my local dev and Pantheon
dev environments.
CASE #58266
Nearly every contrib module I have installed recently on Drupal 8.0.5 has resulted in a common error, two of which I have posted below:
I have had no problem installing these same modules on my local environment before pushing them to the development Pantheon server. I have experienced the same error with search404 and pathauto. In the case of search404, it has seemingly affected functionality of the module, though no other contrib modules have so far experienced any adverse effects from what I can tell.
There is a similar issue posted to the Drupal Sitemap module which is quite
similar to mine and has not yet been resolved:
https://www.drupal.org/node/2601676
Also, glancing at response #3 in the following:
https://www.drupal.org/node/2588511 I wonder, is it possible that the
module expects a different path than is being provided on the Pantheon
environment? Perhaps the error stems from an invalid path structure which
lacks a forward slash or something trivial like that? Maybe this is an
issue which module developers should be made aware of, or which Pantheon
can reasonably accommodate? Just speculation, but I can't imagine what else
could be different in the Symfony routing between my local dev and Pantheon
dev environments.
CASE #58266