Plugin static data
When distributing plugins they often require static data to be setup to function correctly. While this can be handled in the postSetup function, it isn'/files/ in its storage directory which are loaded automagically.
So far to big issues arise:
- The order in which the data is loaded is crucial. Mostly this is the order of the modules which is typically dictated by their references. However self-referencing modules also require the order of the individual entries to be correct.
- Figuring out whether the data also already been imported and how to link that to other modules. For example the module create a category to stick in some data, how can it detect on the next run that the category has been created and it should use that one to add its data in.
- An interesting question is whether data that has been updated previously should be "updated" or whether manual changes should get preference. I.e. if the data is different, is that because the new plugin version changed the relevant entries or did the user do it.
Updates (2)
Tuesday 17th of May 2016 at 22:43
:
A simpler approach has been implemented that allows easy importing of a data set. This way the issues can be resolved by custom logic defined by the creator of the plugin.
Tuesday 17th of May 2016 at 22:44
:
Issue updated
Workflow: Open => Closed
Fixed in changeset: 0 => 3874
Workflow: Open => Closed
Fixed in changeset: 0 => 3874
