@MarcLandis can you retest at your convenience

git pull and npm run install-mm

@calimero glad you got it going.

as for your delayed posts

everyone with reputation below 2 has their posts reviewed. this to stop all the junk posts

i review every such post, and occasionally sleep! lol

please don’t double post

@bumrocks they CAN be altered, but are not there by default… yes, you have to discover them , if u have the need

as for the issues and vulnerabilities, they are not in the MM code, but code it uses and that those use… where the MM owners have little to no control (or exposure to the problem)

but many of the issues you present are why I built up the installer and updater scripts, to get you up and running, regardless of your platform choice

this remains a volunteer project, where, if u are interested you can contribute. It is NOT a ‘product’

@dmstansbury and, if u had used my upgrade script, it would have done all that for you!

https://github.com/sdetweil/MagicMirror_scripts

@gonzonia weird… how did you upgrade to node 21?
apt or nvm?

@hco125 said in MMM-GoogleTasks not compatible with MMM-pages, MMM-Carousel, or MMM-ModuleScheduler:

TypeError: Cannot convert undefined or null to object
at Function.keys ()

bug…

missing data, when display is requested

do this

edit MMM-GoogleTasks.js

change line 37
from

		this.tasks;

to

		this.tasks= {};

@mumblebaj yes, was trying not to add too much extra as there is already a terminal window open for running MM with the modified module

@awwbaker ps: i don’t accept coffee etc. i do this because i truly enjoy it.
i love the challenge, the great people here, and the fascinatingly huge amount of differences among all your designs.

@diccon yes, a module is missing a required library , you need to run npm install in the module folder for the specific module

this is version 2.28, latest is 2.29, we have added code to catch these failures and continue running, where before we crashed.

@togletree93 thats outside our app…

can you try in server mode and

npm run server
then open browser to http://localhost:8080

this turned out to be a permissions problem. the folder was created w the synology user, but the container is running as user 1000

@Bimtronic ignore the audit reports, nothing you can do about them. part of the reason request is deprecated.

@Bimtronic in the MagicMirror folder

@bugsounet you should make it normal, like the rest of the modules…

@Bimtronic can you show me the config.js, xxx out any apikeys or private info

@canlio weather is done all in browser, so open the developer window, ctrl-shift-i, select the console tab, put weath in the filter field.

openweather has changed their business model, the apikey is backed by a credit card

@canlio cool, but, its not supposed to work. they told us publicly 2.5 was supposed to stop working in October… hmmmm

@cgillinger This is one place where the inherited module functions are not so good

getTranslations()

happens WAY before any code is run so you can’t adjust its response based on other info the config might have provided…

and we don’t expose any functions to do the work not related to the files returned from that function

but your code could do the translations BEFORE giving the content to MM… so there would be nothing to translate

@redfishbluefish
apply this fix
see
https://forum.magicmirror.builders/topic/19282/version-2-30-0-calendar-fix-for-clipping-broadcast-events

after installing Jan 1 2025 MM version, events broadcast to MMM-CalendarExt3 are clipped incorrectly

apply this fix (til next release)

cd ~/MagicMirror
git fetch origin pull/3679/head:_fix_clipping
git switch _fix_clipping
npm run install-mm
# if you get an error error, rm package-lock.json
# and repeat the git switch
restart MM

this fix has been accepted and added to the next release

you can use that package instead
see https://forum.magicmirror.builders/topic/14327/testing-new-fixes-or-solving-current-problems-with-next-release-code
to get the develop branch
#NOTE: using develop requires a new

npm run install-mm

absolutely my fault… BUT
this release has been stable and in test since October… but clearly not enough tested it.