@theaddies said in Nextcloud calendar error: maximumEntries: 5, if you try 100 instead of 5 does it make a difference?

@KristjanESPERANTO we dont test with uplevel npm. and try to stay in sync w the level of node we test on this just adds to the complexity of support

hey @sdetweil I realized my raspberry pi was going to sleep so I turned it off and I think it works now. Thank you for your help

@det I have the same problem.

@BKeyport i know, didn’t want to go down that rat hole i proposed some module standards, (based on that experience) no minified code, so that bad actors cant hide. there are currently only 7 modules w minified code, but they were all generated from typescript source. so minified in that case is unimportant. we dont have a way to enforce any such standards makes me think of some vault to keep things from disappearing too

@rkorell i didnt introduce it, in html [image: 1743359737608-img_0895.png]

@Scott-M woohoo… thanks…

@Kelemvor pastDaysCount is an advisory to other modules. they dont have to honor it we send all the events, there was a bug in clipping, i ‘fixed’ for 2.30, but made it worse. the temp fix removes clipping on past events maximum days sets the range to view in cal, default 365 days

@nowayto if pm2 is being used, its JOB is to keep the app running so the pm2 restart seems odd as if the app was ended , ctrl-q pm2 would do restart already

@karsten13 i guess i haven’t looked at the sample in a while

@rkorell yes, he ran some setup/installer code that isn’t saved locally

@sdetweil said in Restore script cannot create Backup folder?: thanks so much for the trouble report… fixed Dear Sam, you’re REALLY (!) welcome! Thanks to YOU for all of your effort! Ralf

@Kelemvor see this topic https://forum.magicmirror.builders/post/125106

Does it go here? [image: 1742999644575-7ce9109b-c466-46b3-a184-55439baa4205-image.png] If so, it didn’t seem to help.

@dphotograph you can use that module again now in the MMM-Config folder do git pull then restart MagicMirror

@PGP_Protector awesome!!

@ChanceTime you edited in config.js, right? never edit the module source

To answer myself: I cleaned the array using: const mplayerArgumentsArrayFilter = mplayerArgumentsArray.filter(discardEmptyArgument); function discardEmptyArgument(value, index, array) { return value != ''; } Then spawned using that array: // Spawn a new mplayer process const env = { ...process.env, DISPLAY: ':0' }; const mplayerProcess = spawn(`mplayer`, mplayerArgumentsArrayFilter, {env: env}); Now it is working correct.

@com1cedric awesome!

@mart11 This should be fixed since we released version 3.0.0 😀 Please update and check.