Getting WARN messages due to Hexadecimal color codes in Team Calendars
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
As Confluence administrator, you find numerous WARN entries in the logs related to hexadecimal colors used in Team Calendars
Environment
Confluence 8.X
Diagnosis
In the atlassian-confluence.log files, you will find multiple messages such "setSubCalendarHexColor SubCalendar color value is hex"
Cause
As per Team Calendars data model, the colour is stored in COLOUR column inside table AO_950DC3_TC_SUBCALS. Team Calendars do not keep the colours in HEX code, but with a coding such as "subcalendar-yellow" or "subaclendar-green2"
It is unclear how these color codes were imported into Confluence, as Team Calendars currently does not support custom color codes beyond the predefined ones. There is a suggestion raised about this under
CONFSERVER-51016
-
Getting issue details...
STATUS
Solution
There is no harm in these messages, but it is easy to get ride of them following the steps below.
Run the following SQL statement to see what Team Calendars are the one using this HEX colours:
SELECT "COLOUR","ID","NAME"
FROM "AO_950DC3_TC_SUBCALS"
WHERE "COLOUR" LIKE '#%'For those entries you found, execute the following statement to UPDATE all of them to a colour you choose, in this example, red:
UPDATE "AO_950DC3_TC_SUBCALS"
SET "COLOUR" = 'subcalendar-red'
WHERE "COLOUR" LIKE '#%'- Restart Confluence