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
Thanks. I'll have another play.
Import Existing Site using Feeds
Responding without having tested this. I think this is because of the format of your dates in the CSV file. It has to match that of the column. For nodes, the created and changed date columns use...
Import Existing Site using Feeds
HMmm... The CSV file looks like this: The mapping looks like this: The eventdate doesn't import: and the datepublished doesn't seem to work either: I'm obviously not getting it quite right but...
Import Existing Site using Feeds
Hi 1. No. It's a Bolt site. Each content type is in one table. The Feed module seems to cope reasonably well as a first stab at it (accept the defaults and see what happens) but I'm looking to...
Import Existing Site using Feeds
Hello Mike. I'm a bit unclear about some details in your question. 1. Are you trying to import content (nodes) from a Drupal 7 site into a Backdrop site? The columns you list look like the origin is...
Import Existing Site using Feeds