Automatically closed - issue fixed for 2 weeks with no activity.
When no external database driver is enabled and the module is used, it throws an exception leading to a WSOD.
By code.
Maybe redirect to a Drupal error page and stop processing current page.
Todo.
Nope.
And exception thrown will be turned into a page redirection (or it will throw and exception handled by Drupal core by default if it is possible... 'got to check.).
None.
Fixed
1.0
Code
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Automatically closed - issue fixed for 2 weeks with no activity.