saltednut
commented
4 years ago Had an epiphany when I ran into this AGAIN while working on something else for Scenarios.
The 'black box' diff between whats in our distro code's config versus what gets overridden when a CDF does an import can be opened.
drush cex the current site configuration. Now look for anomalies.
ack node_type_class shows, even though the df_tools modules that provide them no longer have the config for node_type_class, it's there for both the person and event content type definitions.
The issue I was running into (not being able to do a single config import) is fixed after removing the node_type_class dependency and third party settings from both content types and running drush cim
Fix forthcoming when I have a chance to export a new CDF
Even after removing the module and patching others to explicitly remove any and all dependencies that we can find, CDF exports continue to contain a large number of dependency tree lists that contain
node_type_class- since a large portion of the CDF is base64 encoded, it is difficult to know if the node_type_class dependency is coming from somewhere within that file. It may be that older configuration for content types are persisting. Additional testing needs to be done to determine if the content were rebuilt whether or not that would solve the problem. One can comment out the CDF portion of dfs_one.scenarios.inc and get a 'one' site that is empty. We can test from there.