I’ve been testing with DPL and deleted the database quite often in the process. After each database deletion, I need to set ambiguity resolution again, which I consider an unnecessary pain in the neck.
Proposal
Create a possibility to select the module in DPL’s settings/preferences
in addition to what already exists.
a) Ambiguity resolution settings/preferences precede DB-entries.
b) Settings must survive a database delete.
It’s a related topic, whatever the implementation might be. Note that “ignoring” a module should also disable the warning that can appear when exporting starts.
