- warning: this envvar version will not import the old configuration due to the changes, backup before
Concerning this: To update any previous envvars to a new set, some manual hacking is required (sorry for that). But be really careful! This description is for real experts only! You should actually
never-ever edit this file manually. So if you are unsure you better use the envvars settings inside C::B to setup your envvars from scratch! This is most probably the best way anyway.
If you are sure about to be an expert; have no time to setup the envvars from scratch; have a backup in the back-hand and swear you won't blame me, do the following:
- backup your old configuration (default.conf)
- open C::B with the new plugin, switch to the envvar settings in menu Settings -> Environment
- notice it's empty (that's OK for now), click OK and close (!!!) C::B
- open default.conf with a nice editor, you should find a section like this inside:
<envvars>
<ENVVAR0>
<str>
<![CDATA[1|YOUR_VAR_1|YOUR_VALUE_1]]>
</str>
</ENVVAR0>
<ENVVAR1>
<str>
<![CDATA[1|YOUR_VAR_2|YOUR_VALUE_2]]>
</str>
</ENVVAR1>
(...and so on...)
<sets>
<default />
</sets>
</envvars>
Change it to:
<envvars>
<sets>
<default>
<ENVVAR0>
<str>
<![CDATA[1|YOUR_VAR_1|YOUR_VALUE_1]]>
</str>
</ENVVAR0>
<ENVVAR1>
<str>
<![CDATA[1|YOUR_VAR_2|YOUR_VALUE_2]]>
</str>
</ENVVAR1>
(...and so on...)
</default>
</sets>
</envvars>
Notice that the default tag has changed from an empty one (
<default />) to tag with content (inside
<default></default>).
With regards, Morten.