v2.22.0 | default calendar: no symbols with customEvents

[sdetweil]

@kai are they in a different fa group?

did u modify the code to make it work before?
see
https://forum.magicmirror.builders/topic/17495/v2-22-0-font-awesome-fab-icons

new config option

[kai]

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?!?

[JDIBBY]

@sdetweil @kai

Were you guys able to resolve this? I have the same issue immediately after the v2.22.0 upgrade. I’ve tried different combinations of defaultSymbolClassName variables and can not get it to work for any customEvents.

[sdetweil]

@JDIBBY I have not looked at it more. can u say what symbols you used?

the full fontawesome name please.

[sdetweil]

@JDIBBY can you use the link I posted about the dev console and see what symbol class and name was used the those elements?

[karsten13]

there was a change concerning symbols, see https://github.com/MichMich/MagicMirror/pull/2949/files

this should be backward compatible in normal setups but I don’t know how this is compatible with customEvents.

Did you try something like

..., symbol: 'fa-solid fa-megaphone' ... or

..., symbol: 'fas fa-fw fa-megaphone' ... ?

[sdetweil]

@karsten13 but he should not have to use the fa- prefix on megaphone, cause its in the setting

[sdetweil]

@JDIBBY I changed one of my test cal setups to use custom events, copying your data but changing the trigger text

        calendars: [
        {
          url: "http://localhost:8090/modules/default/calendar/woot.ics",
          symbol: "calendar",
          color: "#efefef",
          name: "Rags Calendar",

        }
        ],
          customEvents: [
            { keyword: 'Weekly', symbol: 'file-signature' },
            { keyword: 'Every', symbol: 'champagne-glasses' },
          ],

and see this

[kai]

@sdetweil looks great - that’s the way I’d like to have it. :grinning_face:
So you didn’t specify a symbol class for the customEvents at all? I have had no success with this so far…

[sdetweil]

@kai no, exactly as I posted. are you sure those are the phrases in your calendar subject?

I had a problem once before, and had Two spaces between words in the calendar event, and only one in the events stucture…

[DaveChild]

I’ve been having the same problem. In mine the fas fa-fw fa- prefix was missing, so I changed my config to this:

customEvents: [
    {keyword: "Games", symbol: "dice fas fa-fw fa-dice"},
    {keyword: "Rugby", symbol: "running fas fa-fw fa-running"},
    {keyword: "Guitar", symbol: "guitar fas fa-fw fa-guitar"}
],

I duplicated the “dice” at the start so it keeps working when the bug is fixed. And the icons appear now.

[sdetweil]

@DaveChild hm… that is the symbolPrefix variable in 2.22

[DaveChild]

@sdetweil I’ve not delved far into the code but it looks to me like the symbolsForEvent function in calendar.js is getting the default symbol with the default class, but then overwriting that default with the symbol from customerEvents - but not applying the default class to it.

This might be fixed with applying this.getCalendarPropertyAsArray to ev.symbol in the line symbols[0] = ev.symbol;.

I’d do a PR myself but I have nowhere near enough experience tinkering with MagicMirror to be pushing code to a default module :). But I think that’s where the problem is, and my solution will work around that issue crudely for the moment.

[sdetweil]

@DaveChild cool. I’ll give that a look

[DaveChild]

@sdetweil I did a quick PR anyway, even if it’s not perfect, it’s better there’s a starting point for a fix than make someone repeat tracking it down to where I got to.

[lmhmm]

@sdetweil Yes I’ve got the same issue after upgrading to 2.22 no symbols even trying solution here. Be nice to get this resolved

[sdetweil]

@lmhmm Dave found it and provided a fix for next release. (April 1)

you could look at what he did and change your code,

of git pull and check the develop branch. see the instructions pinned to the top of this topic about testing fixes.

[sdetweil]

@DaveChild awesome. I saw all the GitHub traffic. great work

[lmhmm]

@sdetweil I really don’t understand the answer so will just wait for the next release. Or do I just hit pull the default calendar module? Not sure how to apply fix.

[kai]

Hi @DaveChild, @sdetweil,
thank you very much for your effort and your research!!!
I’ll use @DaveChild’s prefix solution until the next release; the custom icons are now displayed within the calendar.
Many, many thanks to you and all who so tirelessly develop the MM and keep it alive!
May the code be with you
-kai