I was hit by this in a D7 site. I think we should fix it in Backdrop so that people don't scratch their heads over things like this. This also falls under the "make contrib devs' life easier" umbrella, because the alternative is to have all of them "fix" their projects individually, while we could be handling this in core.
Respective d.org issue against core: https://www.drupal.org/node/1551132
Why do we have this exception? (and in general why does D7 have so much worse handling of things like this??)
the error comes when a user tries to install a module which was previously installed and the .instal chokes simply because the table was already there.. and worse, it kills the process of enabling all the other modules that were trying to be enabled.
pretty sure in D6 we'd just skip this.. why does everything in D7 cause a stupid exception and just bail with a stupid message: "The website encountered an unexpected error. Please try again later. " really? try again later? why? is this magically going to fix itself?
what are we trying to avoid here?
could the existing tables possibly be of an old design and therefore we would need to run updates on them? but can't db code see this and run the updates; most likely the system table entry is still there so we do know what version of schema exists?
are we trying to force module designers to write code in all .installs to first check if tables exist and then handle this in the .install file? why would we want to replicate this code 200 times on a project?? why not have db code handle this?
really tired of seeing these exceptions all the time for no apparently useful reason.
Recent comments
Hello, @aubergine! Thanks a lot, I got it, all sorted out.
How to get the current page language?
In addition to what @findlabnet has said, you possibly want to be looking at metatags as you can then tell search engines which page is the canonical source for a given page. In this scenario,...
xmlsitemap module generates wrong links for languages
Not only twice — the number of languages not excluded from the sitemap can be greater than that. This feature is designed according to the corresponding recommendations. So, I can't...
xmlsitemap module generates wrong links for languages