This question/problem came up in the Backdrop CMS issue queue. The problem arose when someone was porting a D7 module that stored configurations at the root level of the field instance definition. Those custom configurations did not get saved. Backdrop doesn't allow custom configurations at the root level of the instance - it restricts that level to specific, pre-defined keys, and ignores everything else.
The solution is to modify the custom module to store its custom configurations inside the settings
element of the instance array. Then it will get saved. For example, you could store your settings like so:
$instance['settings']['my_module'] = array('setting_1' => 'asdf', 'settings_2' => 'zxcv');
Recent comments
I did try something similar to this as well, but as far as I can tell, there is no option to set the timezone handling in backdrop's views. :( I can set a different date format, but I cannot...
How to Display Date & Time in Original and Local Time Zones
The preview comment links to the website of an online game.
ERR_HTTP2_PROTOCOL_ERROR in Google Chrome and MS Edge
Being on a vacation, I can't check the option to choose a time zone format in a views block. However, here is another idea: Add the field to a layout. Backdrop allows individual fields to...
How to Display Date & Time in Original and Local Time Zones
With the help of the Backdrop office hours crew, I was able to figure out a solution that works for me. I just added an explicit format setting to the long-text field before saving it,...
Is there a way to programmatically enable CKEditor5?
Have you tried adding a symlink pointing at the new location, within the ROOT/themes folder?
Refactor code