Default Calendar module frequently refreshes

DarrenO 0

@sdetweil said in Default Calendar module frequently refreshes:

@DarrenO-0 I rejected your post w the log entries, see the notification message I sent

The calendar entries for the logs were unique.
I removed the true component of the email address prior to the “@” and replaced them with calendaruser1… calendaruser4

Incidentally, i’ve been back through the config.js file for the default calendar and found that I had specified tableClass= twice.
The fIrst instance had a value of “small” with the bulk of the other options.
The second instance had a value of “xsmall” and was between the customEvents[] and calendars[] arrays.

I removed the second instance and changed the value of the first to “xsmall”.
Saving the config automatically restarted MM and it appears to have resolved the matter as it hasn’t repeated the issue in the last hour, but i’ll continue to monitor over the next couple of days.
Not sure how that one line could have caused the issue… Any ideas???

DarrenO 0

@sdetweil
one thing i’ve now noticed since removing the duplicate tableClass entry in the calendar module’s config, when i now run :
pm2 logs --lines=15
i am now seeing the Broadcasting ### events entries calendars update on the scheduled intervals.

Prior, while i was having the issue, i would see a constant updating of the live view of pm2 logs.

michaelarnauts

@sdetweil

That makes sense, but I see a lot more updates then what you describe here.
I’ve added a screenshot of the updates I get to my github issue, and I’ve added it here as well. (note that all the messages have the same length, and some are a few seconds apart.

I’m not sure how to proceed in troubleshooting. When I enable debug logging, it is outputting a LOT (the whole ics file contains data from years ago).

sdetweil

@DarrenO-0 sorry, not quite sure what you’ve said here

You specified tableClass twice in the config of a single calendar module declaration?

JavaScript should take the second, and ignore the first
JSON.parse() should overlay the first w the second

And tableClass is only used in the presentation of the events long after the broadcast message is sent

sdetweil

@michaelarnauts For the log output, we were looking for the broadcasting xxxx events messages entries
But note they have the full URL string , which you shouldn’t post on the forum