Color Macros does not work anymore

We previously had 1.1.5 installed and the colour macros (i.e. using red text ) worked perfectly. But somewhere along the way we 'lost' it (meaning that it just displays in normal black color). I thought it would be fixed by upgrading to the latest version of Foswiki which I did this morning. Sadly it was not fixed. Let me explain how I upgraded.

1) Extract new release of 1.1.8 next to current 1.1.5 release.

2) Copy LocalSite.cfg from 1.1.5 to 1.1.8.

3) Use the same foswiki.cfg

4) Rename data and pub folders in new release to NOT use them. Then add symlinks to the current data and pub that remains unchanged from release to release.

5) Start configure and upgrade all the plugins to the latest versions until there are no more errors/warnings.

This works well en everything is working correctly except this darn colors??

I then tried to copy the latest versions of files for data/System to the current data folder but this did not fix anything.

Please help.

Heinrich

-- HeinrichVermeulen - 17 Apr 2013

The color macros are defined in the normal settings / preferences hierarchy. Check the contents of:

DefaultPreferences
SitePreferences
and overrides in Web, User and Topic settings.

Before 1.1.5, colors were set using the font tag: Examples are commented out.

      * #Set RED = <font color="#ff0000">
      * #Set ENDCOLOR = </font>

Sometime after 1.1.5, the color macros were changed from deprecated <font> tag over to <span> tags using CSS Classes. The ENDCOLOR tag needs to be the appropriate closing span or font tag.

      * #Set RED = <span class='foswikiRedFG'>
      * #Set ENDCOLOR = </span>

And the actual color values are in the CSS, in file pub/System/SkinTemplates/base_src.css

.foswikiRedFG    { color:#ff0000; }

You should verify that if you overrode any of this in your Main or Web preferences, that they use the new encoding, that the color and endcolor macros are consistent, and that the css files contain the new css color classes.

-- GeorgeClark - 17 Apr 2013

Thanx! I just needed to update my pub/System folder with the latest version that ships with 1.1.8 (and then set my permissions and rights).

-- HeinrichVermeulen - 22 Apr 2013