CB

MR !323 is a proposed easy fix for this.

However I'm not sure why you got this as default config should be set on fresh installs, and on existing installs, that setting should be there imho.

So leaving this as only half resolved and leaving assigned to Kyle for closing comment.

Looks like config was never saved in any case. Config basically has the same limits of CBSubs except output the benefit of using getter/setter so you end up with errors like that if config is never saved. It should be saved at least once or the usages of the config global should do isset checks. One option is to load the config XML during install and save it to ensure defaults are stored, but unsure if we'd want to go that approach as by 2.1 we should be using proper config object with getter/setter.

This can be avoided by having the installer check for missing keys using the defaults from XML. Implement this when implementing the other plugin migrations to the installer.

Fixed in MR !336