Quote from Experimental modules in Drupal 8:
Drupal 8 core introduces the concept of experimental modules. These are modules that are provided with Drupal core for testing purposes, but that are not yet fully supported. Experimental modules are included in the Core (Experimental) package on the Extend page of a Drupal site (
I do understand what "testing purposes" means, and I'm aware of best practices like having a Dev / Staging / QA / Prod configuration.
But when using Drupal 8 in a Prod environment, I'm looking for a way to ensure to a site owner something like "
You can be 100% that there is no way that any of these experimental modules can ever be enabled in the prod version of your site.". Imagine it's about a business critical Drupal site where "testing in production" is not ever allowed.
So what options do I have in Drupal, apart from hacking core (which is not an option), to be 100% sure of this? And so that:
- It applies for "everybody" (any user), so even
user/1should not be able to do so if (s)he'd be tempted to do so.
- It doesn't matter if you're using the Admin UI, Drush, Console or anything similar
There are some D8 core issues about these experimental modules, which IMO are either related, or contains some inspiring comments for finding a possible solution (work around?):
- Remove experimental modules from core (or treat them like first class modules).
- [meta] No definition of "Experimental" & not nearly enough warning, with proposed solutions detailed in these related issues: