vfclists → created an issue.
Can the maintainers kindly apply this patch be applied to the distributed version if it works?
The error message can be disturbing for those end users?
Regards
Thanks.
Can closing this issue wait until I can successfully create another bug report before it is marked Closed?
Thanks for confirming the account.
In relation to the new issue - https://www.drupal.org/project/tsbu/issues/3522340 → , won't it be easier to delete the existing one and create a new one?
I assume that being confirmed it will automatically be visible.
vfclists → created an issue.
You mentioned that you had to install the comment module, but I can see they have the dependency already?
Although the comment module is listed as a dependency of Database Search Defaults the WSOD occurs if it is not installed beforehand. It needs to be installed if the WSOD is not to occur.
The module also requires an Article content type to be present before it works in any case, so its inclusion in Drupal CMS is questionable.
The point here is Drupal CMS is supposed to be a curated set of modules which are expected to work together without causing WSODs.
If Search API is something added to the Drupal CMS distribution rather than something which comes with core, then the Database Search Defaults should be disabled if it is automatically pulled in by the Search API until it is fixed upstream.
You mentioned that you had to install the
commentmodule, but I can see they have the dependency already?
Although the comment module is listed as a dependency of Database Search Defaults the WSOD occurs if it is not installed beforehand. It needs to be installed if the WSOD is not to occur.
The module also requires an Article content type to be present before it works in any case, so its inclusion in Drupal CMS is questionable.
The point here is Drupal CMS is supposed to be a curated set of modules which are expected to work together without causing WSODs.
If Search API is something added to the Drupal CMS distribution rather than something which comes with core, then the Database Search Defaults should be disabled if it is automatically pulled in by the Search API until it is fixed upstream.
You mentioned that you had to install the
commentmodule, but I can see they have the dependency already?
Although the comment module is listed as a dependency of Database Search Defaults the WSOD occurs if it is not installed beforehand. It needs to be installed if the WSOD is not to occur.
The module also requires an Article content type to be present before it works in any case, so its inclusion in Drupal CMS is questionable.
The point here is Drupal CMS is supposed to be a curated set of modules which are expected to work together without causing WSODs.
If Search API is something added to the Drupal CMS distribution rather than something which comes with core, then the Database Search Defaults should be disabled if it is automatically pulled in by the Search API until it is fixed upstream.
You mentioned that you had to install the
commentmodule, but I can see they have the dependency already?
Although the comment module is listed as a dependency of Database Search Defaults the WSOD occurs if it is not installed beforehand. It needs to be installed if the WSOD is not to occur.
The module also requires the Article content type which has been removed from recent versions of Drupal to be present to work in any case, so its inclusion in Drupal CMS is questionable.
The point here is Drupal CMS is supposed to be a curated set of modules which are expected to work together without causing WSODs.
If Search API is something added to the Drupal CMS distribution rather than something which comes with core, then the Database Search Defaults should be disabled if it is automatically pulled in by the Search API until it is fixed upstream.
You mentioned that you had to install the
commentmodule, but I can see they have the dependency already?
Although the comment label is a dependency of the module, the WSOD occurs if the comment module is not installed beforehand.
It also depends on an Article content type which is also not present and will not work without it.
The point here is Drupal CMS is supposed to be a curated system where the recipes and recommended modules are supposed to be tested for compatibility and reliability before being put together, and not cause WSODs as a consequence.
If the Search API and its sample are not installed as a part of core or necessary to evaluate Drupal CMS, then they should be removed from the distribution, and additional documentation created to warn of the possibility of problems with it if installed.
I will raise a bug report on the Search API issue queue if it hasn't been reported yet.