Though we won't be able to actually do any uninstalling -- because we need the module to do that -- we can at least let the user know that something needs to be uninstalled.
If there is an entry in the file system for a module that is disabled (or enabled but removed) I'd like to show information on the Uninstall modules page prompting the user to add back the missing code, and uninstall properly.
It could be tricky to determine which modules need to be uninstalled (and which don't) but I think it's a worthwhile effort to think about how we might do that.
We could even (possibly?) use the schema_version to determine which version of the module to recommend.
This was spun-off from https://github.com/backdrop/backdrop-issues/issues/541
GitHub Issue #:
3779
Recent comments
The File (Field) Paths module should be able to move existing files. I've not tested it, but the module description says: Retroactive updates - rename and/or move...
Moving from /files into subdirectories
Yes indeed. We are exploring a few other more costly options, but as we are a low-resource start-up, we could save a lot of money by integrating Backdrop, CiviCRM and Ubercart for our membership...
UberPOS for Backdrop?
Hello Chrys.., It looks like it was for Drupal 6, with a Dev release for D7... Never seen it before, but it looks like an interesting module... Do you have an immediate need...
UberPOS for Backdrop?