https://github.com/mstrhakr/plugin-docs/blame/e93ab06a83039fae643936cb3587a0f9a61ff366/docs/core/plugin-settings-storage.md#L100
All the details about defaults is redundant. Saving the default config in the .plg file means that if a new entry is added, or a default changes then the update won't get the new entry because the .cfg file already exists
Handle defaults by having /usr/local/emhttp/plugins/myPlugin/default.cfg
Calling parse_plugin_cfg will automatically handle the merging, so there's never a need to reapply the defaults every single time any script executes. They just call parse_plugin_cfg. And additional entries are handled just by adjusting default.cfg
https://github.com/mstrhakr/plugin-docs/blame/e93ab06a83039fae643936cb3587a0f9a61ff366/docs/core/plugin-settings-storage.md#L100
All the details about defaults is redundant. Saving the default config in the .plg file means that if a new entry is added, or a default changes then the update won't get the new entry because the .cfg file already exists
Handle defaults by having /usr/local/emhttp/plugins/myPlugin/default.cfg
Calling parse_plugin_cfg will automatically handle the merging, so there's never a need to reapply the defaults every single time any script executes. They just call parse_plugin_cfg. And additional entries are handled just by adjusting default.cfg