search_api_db_defaults_requirements is not doing it right

Sorry, but this bug report is pretty unhelpful in its current form. Do you have any suggestions for how to improve this situation? For instance, do you suggest documenting that the module shouldn’t/can’t be used as part of an install from config, or is there some better way to prevent that?

@drunken monkey - this module is really a recipe :) if it was converted to that then no one would ever try to install it as part of an install from config or something else.

However in order to turn this into a recipe we need to sort out how a recipe can determine the sort of preconditions you've got going in the install requirements. I think we already have an issue for this - I'll link this with that when I have a moment.

OK, thanks, that makes sense. I’ve adapted the issue title and description accordingly.

Will it still be possible (or can we make it possible) for less experienced users to install this directly on their site via the UI? Otherwise it would still seem like a regression, even though it might be an improvement for a certain segment of medium-experienced users.