2.32.0 Calendar module limitDays and excludedEvents stopped working

AndyHazz

@sdetweil yep that’s what I’ve got, copying below in case I’m missing something …

I’ve also added your debug messages back in and changed Log.debug to console.log (as I still can’t get any debug logs from docker but I do get console.log messages from other modules) but nothing comes out in the console log - seems odd that all these changes have had zero effect, am I missing something that might be needed to get these changes to kick in?

        shouldEventBeExcluded (config, title) {
                let result = {  // CHANGED
                        excluded: false,
                        until: null
                };
                for (let f in config.excludedEvents) {
                        let filter = config.excludedEvents[f],
                                testTitle = title.toLowerCase(),
                                until = null,
                                useRegex = false,
                                regexFlags = "g";
                        if (filter instanceof Object) {
                                if (typeof filter.until !== "undefined") {
                                        until = filter.until;
                                }

                                if (typeof filter.regex !== "undefined") {
                                        useRegex = filter.regex;
                                }

                                // If additional advanced filtering is added in, this section
                                // must remain last as we overwrite the filter object with the
                                // filterBy string
                                if (filter.caseSensitive) {
                                        filter = filter.filterBy;
                                        testTitle = title;
                                } else if (useRegex) {
                                        filter = filter.filterBy;
                                        testTitle = title;
                                        regexFlags += "i";
                                } else {
                                        filter = filter.filterBy.toLowerCase();
                                }
                        } else {
                                filter = filter.toLowerCase();
                        }
                        console.log("should be excluded ", testTitle, filter, useRegex, regexFlags)
                        if (CalendarFetcherUtils.titleFilterApplies(testTitle, filter, useRegex, regexFlags)) {
                                if (until) {
                                        result.until = until;  // CHANGED
                                } else {
                                        console.log("event should be excluded = true,", testTitle )
                                        result.excluded = true;  // CHANGED
                                }
                                console.log("filter applies result =", result)
                                break;
                        }
                }
                console.log("filter applies returning =", result)
                return result;  // CHANGED
        },

p.s. just spotted comment on line 12 😅

TODO This seems like an overly complicated way to exclude events based on the title.

sdetweil

@AndyHazz note that the excluded events is an ARRAY (so for loop to look thru them )
test ALL til find one that is true (CalendarFetcherUtils.titleFilterApplies returns true) , or not

AND the item in the array can be an object with more specific controls, or a string

MM doc entries on separate lines

[
'Birthday',     // text 
'Hide This Event',    // text 
{filterBy: 'Payment', until: '6 days', caseSensitive: true},  // complex, but text
{filterBy: '^[0-9]{1,}.*', regex: true} // complex, uses regex
]

AND the list/array can be a MIX of those things,

and the string test is the test string is SOMEWHERE in the title, doesn’t have to BE the entire title

AndyHazz

@sdetweil fair enough, complexity no doubt warranted!

Perhaps is there any reason why shouldEventBeExcluded function might not be getting called at all for me? I’m stumped why after making all these changes including console.log messages, nothing is appearing any different -

sdetweil

@AndyHazz can’t think of any, MM is case sensitive, some times people get the case wrong and we don’t report unexpected parms or missing parms…

but you’ve been using that so, it doesn’t shouldn’t be an issue for you

sdetweil

@AndyHazz I copied your post in exactly, i reverted back to 2.32 original first

and got the right debug and results

[2025-07-09 16:27:38.473] [DEBUG] Processing entry…
[2025-07-09 16:27:38.473] [DEBUG] title: Dad’s Birthday
[2025-07-09 16:27:38.473] [LOG] should be excluded dad’s birthday birthday false g
[2025-07-09 16:27:38.473] [LOG] event should be excluded = true, dad’s birthday
[2025-07-09 16:27:38.473] [LOG] filter applies result = { excluded: true, until: null }
[2025-07-09 16:27:38.473] [LOG] filter applies returning = { excluded: true, until: null }

sdetweil

@AndyHazz and

the fetcherutils processes this exclude list very early after getting the events parsed

                // loop thru the parsed data, one event at a time
		Object.entries(data).forEach(([key, event]) => {
			Log.debug("Processing entry...");

			const title = CalendarFetcherUtils.getTitleFromEvent(event);
			Log.debug(`title: ${title}`);

			// Return quickly if event should be excluded.
			let { excluded, eventFilterUntil } = this.shouldEventBeExcluded(config, title);
			if (excluded) {
				return;
			}

AndyHazz

@sdetweil should I see a console message from loader.js about calendarfetcherutils.js being loaded?

I see

Load script: modules/default/calendar/calendar.js
Load script: modules/default/calendar/calendarutils.js

but no mention in the console of calendarfetcherutils.js

sdetweil

@AndyHazz no.

AndyHazz

@sdetweil I’ve no idea then, but if you were able to reproduce the issue I had, and then fix it on your end, I probably just messed something up somewhere and without any access to logs on my docker setup that may remain a mystery … I’ve just had another go at trying to figure out what that may be, no luck.

No rush at all but I guess if you’re happy with the fix it’ll show up in a new MM version at some point and I’ll update to that.

sdetweil

@AndyHazz next release isn’t til Oct 1