Dizkus

Not all the colours in the $colors array are available in the theme, it seems, notably the background colour ($bgcolor1)
The theme.php define these ones, and others are defined in xaninit.php:

They should translate to tags like this, but some of them aren't valid:

So, Is this a bug, or are there other tag names for these? It wouldn't make sense for them not to match the $colors array, though. Mark's conversion kit has a slightly different listing of colours, but only the ones above are valid. In the meantime, I'll have to hard-code the background colours.

Martin,

I believe that the colors defined in theme.php are the legacy names used by older modules e.g. $GLOBALS['color1'] etc... The Xanthia class assigns the full range of colors available in a a palette in the followig snippet. The keys for the array are the template tags.



-Mark

Thanks Mark, these work:

I had a look through the documentation first, and found no mention of these codes. It talks of how to use the Xanthia colours configuration panel, that's all. The closest I found was the table of commands in your AT->Xanthia Conversion kit, which shows $color1-10 for colours, nothing more (of which the last two don't exist). I assume this was how it was in an earlier build.
Is there a reason other than semantics why the others don't match the $colors array, notably bgcolor, textXcolor, linkcolor, vlinkcolor and hovercolor? They can't be defined global vars, since nothing is returned by the Template for $link, $vlink, $hover, and $background. It's not important as long as the tags are documented somewhere.

I figured the first were for legacy, the confusing part there is that there isn't a direct correlation between the $color vars and the old vars, eg $color1 = $bgcolo2 etc, so it's tempting to put $color4 when you want $bgcolor4, which is wrong. I found this in postnukeblue for instance.

Martin

Martin,

We definately need to include these in the docs...... I've almost certainly made this mistake myself.

-Mark