Common settings are not stored (if not exist already) #340

This is a new bug, not what code changes caused this, I first suspected the conversion of settings to html but the code in the older settings dialog is similar. The settings in account >> common are not stored unless there exist default settings in the configuration database. The workaround is to load account settings into the common settings page. Apparently when opening the dialog it should generate a bunch of default settings in the configuration database:

extensions.smartTemplate4.common.fwd
extensions.smartTemplate4.common.fwdhead
extensions.smartTemplate4.common.fwdheader
extensions.smartTemplate4.common.fwdhtml
extensions.smartTemplate4.common.fwdmsg
extensions.smartTemplate4.common.fwdnbr
extensions.smartTemplate4.common.new
extensions.smartTemplate4.common.newhtml
extensions.smartTemplate4.common.newmsg
extensions.smartTemplate4.common.newnbr
extensions.smarttemplate4.common.rsp
extensions.smarttemplate4.common.rsphead
extensions.smarttemplate4.common.rspheader
extensions.smarttemplate4.common.rsphtml
extensions.smarttemplate4.common.rspmsg
extensions.smarttemplate4.common.rspnbr

these are used when changing any checkboxes / editing text in Account templates / Common and will be used by any account that has the option "use common" activated. However the dialog actually creates a bunch of settings without the "common":

extensions.smartTemplate4.fwd
extensions.smartTemplate4.fwdhead
extensions.smartTemplate4.fwdheader
...etc.

you can also see errors when it tries to write the user's changed settings to the missing defaults above.

To fix this problem, the correct defaults must be created first.