Hi @sdetweil,
I’m sorry, I’m being too stupid right now…
The symbols are not in a different fa group - or at least they don’t have to be. :winking_face:
This is the code that previously worked perfectly (with a “global” symbol):
{
module: "calendar",
header: "Abitur",
position: "top_left",
config: {
calendars: [
{
symbol: "graduation-cap",
color: "#00bfff",
url: "<path_to_local_ics_file>"
}
],
colored:true,
dateFormat:"DD.MM.YYYY",
fetchInterval:86400000,
fullDayEventDateFormat:"DD.MM.YYYY",
getRelative:0,
maximumNumberOfDays:180,
showEnd:false,
timeFormat:"absolute",
urgency:0
}
},
I wanted to have some entries with different symbols, hence I changed the code by adding customEvents (before upgrading to v2.22.0):
{
module: "calendar",
header: "Abitur",
position: "top_left",
config: {
calendars: [
{
symbol: "graduation-cap",
color: "#00bfff",
url: "<path_to_local_ics_file>"
}
],
colored:true,
customEvents: [
{ keyword: 'Abgabe', symbol: 'file-signature' },
{ keyword: 'feier', symbol: 'champagne-glasses' },
{ keyword: 'Bekanntgabe', symbol: 'megaphone' }
],
dateFormat:"DD.MM.YYYY",
// defaultSymbolClassName: "fa-solid fa-",
fetchInterval:86400000,
fullDayEventDateFormat:"DD.MM.YYYY",
getRelative:0,
maximumNumberOfDays:180,
showEnd:false,
timeFormat:"absolute",
urgency:0
}
},
This worked fine as well. After having upgraded to v2.22.0 none of the customEvents symbols is displayed anymore. It doesn’t matter if there is an entry for defaultSymbolClassName.
As in most cases, the problem is probably in front of the screen… Maybe I just chose the wrong class?!?
