A migration for the Plugin did not occur to populate the initial configuration values. This was causing the configuration to be present, but the values would be null since the fields did not exist in the database.
If a user did visit and save the system configuration of the plugin, then they never received the error and it worked normally.
I was able to test that the migration worked properly by removing the mongo record and then restarting the plugin.
This PR also fixes an issue where when using reloading or loading a saved search in the same window it was resetting the values to what was stored in the configuration instead of using the currently selected value set by the user via the Options Menu. The behavior now works properly and only resets the configuration upon being Dismissed.
A migration for the Plugin did not occur to populate the initial configuration values. This was causing the configuration to be present, but the values would be null since the fields did not exist in the database.
If a user did visit and save the system configuration of the plugin, then they never received the error and it worked normally.
I was able to test that the migration worked properly by removing the mongo record and then restarting the plugin.
This PR also fixes an issue where when using reloading or loading a saved search in the same window it was resetting the values to what was stored in the configuration instead of using the currently selected value set by the user via the Options Menu. The behavior now works properly and only resets the configuration upon being Dismissed.