this is a “feature” of nodebb since release v3.9.1, nothing we can do.
Read the statement by Michael Teeuw here.
Posts
-
RE: Forum Bug..
-
v2.29.0
https://github.com/MagicMirrorOrg/MagicMirror/releases/tag/v2.29.0
[2.29.0] - 2024-10-01
Thanks to: @bugsounet, @dkallen78, @jargordon, @khassel, @KristjanESPERANTO, @MarcLandis, @rejas, @ryan-d-williams, @sdetweil, @skpanagiotis.
⚠️ This release needs nodejs version
v20orv22, minimum version isv20.9.0Added
- [compliments] Added support for cron type date/time format entries mm hh DD MM dow (minutes/hours/days/months and day of week) see https://crontab.cronhub.io for construction (#3481)
- [core] Check config at every start of MagicMirror² (#3450)
- [core] Add spelling check (cspell):
npm run test:spellingand handle spelling issues (#3544) - [core] removed
config.paths.vendor(could not work becausevendoris hardcoded inindex.html), renamedconfig.paths.modulestoconfig.foreignModulesDir, added variableMM_CUSTOMCSS_FILEwhich - if set - overridesconfig.customCss, added variableMM_MODULES_DIRwhich - if set - overridesconfig.foreignModulesDir, added test forMM_MODULES_DIR(#3530) - [core] elements are now removed from
index.htmlwhen loading script or stylesheet files fails - [core] Added
MODULE_DOM_UPDATEDnotification each time the DOM is re-rendered viaupdateDom(#3534) - [tests] added minimal needed node version to tests (currently v20.9.0) to avoid releases with wrong node version info
- [tests] Added
node-libgpiodlibrary to electron-rebuild tests (#3563)
Removed
- [core] removed installer only files (#3492)
- [core] removed raspberry object from systeminformation (#3505)
- [linter] removed
eslint-plugin-import, because it doesn’t support ESLint v9. We will reenter it later when it does. - [tests] removed
onofflibrary from electron-rebuild tests (#3563)
Updated
- [weather] Updated
apiVersiondefault from 2.5 to 3.0 (#3424) - [core] Updated dependencies including stylistic-eslint
- [core] nail down
node-icalversion to0.18.0with exceptionallow-ghsas: GHSA-8hc4-vh64-cxmjindep-review.yaml(which should removed after nextnode-icalupdate) - [core] Updated SocketIO catch all to new API
- [core] Allow custom modules positions by scanning index.html for the defined regions, instead of hard coded (PR #3518 fixes issue #3504)
- [core] Detail optimizations in
config_check.js - [core] Updated minimal needed node version in
package.json(currently v20.9.0) (#3559) and except for v21 (no security updates) (#3561) - [linter] Switch to ESLint v9 and flat config and replace
eslint-plugin-unicornby@eslint/js - [core] fix discovering module positions twice after #3450
Fixed
- Fixed
checksbadge in README.md - [weather] Fixed issue with the UK Met Office provider following a change in their API paths and header info.
- [core] add check for node_helper loading for multiple instances of same module (#3502)
- [weather] Fixed issue for respecting unit config on broadcasted notifications
- [tests] Fixes calendar test by moving it from e2e to electron with fixed date (#3532)
- [calendar] fixed sliceMultiDayEvents getting wrong count and displaying incorrect entries, Europe/Berlin (#3542)
- [tests] ignore
js/positions.jswhen linting (this file is created at runtime) - [calendar] fixed sliceMultiDayEvents showing previous day without config enabled
-
RE: Experience with MMM-WebUntis?
the
package.jsoncontains"webuntis": "latest"so it will always install the latest version of this dependency.I suspect that there were breaking changes within some versions, you could try an older version (see https://github.com/SchoolUtils/WebUntis/tags).
You have to update
package.jsonwith e.g."webuntis": "2.2.1"and executenpm installin the module folder. -
RE: Fetch Failed with multiple instances across multiple modules (multiple config)
can you provide the logs of system information?
Something like this:
[2024-09-19 21:52:27.750] [INFO] System information: ### SYSTEM: manufacturer: Microsoft; model: Docker Container; virtual: true ### OS: platform: linux; distro: Debian GNU/Linux; release: 12; arch: x64; kernel: 5.15.153.1-microsoft-standard-WSL2 ### VERSIONS: electron: undefined; used node: 22.9.0; installed node: 22.9.0; npm: 10.8.3; pm2: ### OTHER: timeZone: UTC; ELECTRON_ENABLE_GPU: undefined -
RE: iFrame blank when displaing http://<ipaddress LMS server>:9000/material
I won’t stop you from opening an issue …
-
RE: iFrame blank when displaing http://<ipaddress LMS server>:9000/material
@sdetweil said in iFrame blank when displaing http://<ipaddress LMS server>:9000/material:
@stephanvdplas i understand, looks like something changed in 31, which can be a bug as well.
you’ve got a workaround in the near term.
id open an issue on the MagicMirror github page with the error and a link to this topic so we don’t lose it.
finding a test environment will be the tough thingno, we don’t need another issue we cannot solve.
The problem is chromium which is becoming stricter with every release and with every new electron version you get a new chromium version:
electron Chromium 31.4.0 126.0.6478.23 31.3.1 126.0.6478.185 31.3.0 126.0.6478.183 31.2.0 126.0.6478.127 31.1.0 126.0.6478.114 31.0.2 126.0.6478.61 31.0.0 126.0.6445.0 30.1.0 124.0.6367.243 30.0.9 124.0.6367.233 30.0.8 124.0.6367.230 30.0.7 124.0.6367.221 30.0.5 124.0.6367.207 30.0.4 124.0.6367.201 30.0.3 124.0.6367.119 30.0.2 124.0.6367.91 30.0.1 124.0.6367.60 30.0.0 124.0.6323.0Maybe related to this changed in Chromium 125.
We have to deal with this and downgrading chromium (indirect by downgrading electron) is no real solution.
-
RE: iFrame blank when displaing http://<ipaddress LMS server>:9000/material
@stephanvdplas said in iFrame blank when displaing http://<ipaddress LMS server>:9000/material:
I am quite sure about having the config right
sorry, my point is you have to google the error with the keyword “electron” and check if you find something which you can test
-
RE: iFrame blank when displaing http://<ipaddress LMS server>:9000/material
I can only guess without having the debug case …
You can google and try changing
electronOptionsDefaultsand/orelectronSwitchesDefaultsinjs/electron.jsif you find something … -
RE: iFrame blank when displaing http://<ipaddress LMS server>:9000/material
you could try adding
electronOptions: { webPreferences: { webSecurity: false }, },in
config.js -
RE: iFrame blank when displaing http://<ipaddress LMS server>:9000/material
@sdetweil said in iFrame blank when displaing http://<ipaddress LMS server>:9000/material:
@karsten13 maybe has more skill here…
sorry, no. Maybe google has some findings.
-
RE: iFrame blank when displaing http://<ipaddress LMS server>:9000/material
mm has a simple internal cors proxy you could try.
So instead using the
<original-url>in the iframe you could tryhttp://localhost:8080/cors?url=<original-url>.E.g. if your
<original-url>ishttps://example.comtryhttp://localhost:8080/cors?url=https://example.com -
RE: MMM-CalDAV
@sdetweil said in MMM-CalDAV:
@karsten13 is the docker volume for where modules are located mapped read/write?? (the compose file doesn’t say)
see docs
rw: Read and write access. This is the default if none is specified. -
RE: Skip Update, Dismiss updatenotification
you can skip modules (or mm itself) checking for updates, see
ignoreModulesproperty, docs -
RE: Docker install on synology nas
@sdetweil said in Docker install on synology nas:
@karsten13 i think /opt is non existent on synology
but in the container
-
RE: MMM-CalDAV
[ERROR] Error: EACCES: permission denied, open ‘/opt/magic_mirror/modules/MMM-CalDAV/service/.SYNOLOGY_Simon.ics’
how did you start the container? Please provide full
docker run ...command or compose file. -
RE: CALL FOR TESTERS: New install script
I just presented a way to get by without the base64 that others have criticized.
To address me here now as if I was the critic is far-fetched.
If you call for testing here, you also have to be able to deal with criticism - regardless of whether it is justified or not.
-
RE: CALL FOR TESTERS: New install script
@sdetweil said in CALL FOR TESTERS: New install script:
@mumblebaj AND there is no practical need for encoding anything
there was a need for the binary which was removed meanwhile, but not for the text files …
so e.g. this
base64 -d > /tmp/mm-install/xinitrc <<< 'IyEvYmluL3NoCgp4c2V0IHMgb2ZmICAgICAgICAgIyBkb24ndCBhY3RpdmF0ZSBzY3JlZW5zYXZl cgp4c2V0IC1kcG1zICAgICAgICAgIyBkaXNhYmxlIERQTVMgKEVuZXJneSBTdGFyKSBmZWF0dXJl cy4KeHNldCBzIG5vYmxhbmsgICAgICMgZG9uJ3QgYmxhbmsgdGhlIHZpZGVvIGRldmljZQoKaWYg WyAtciAiL2V0Yy9tYWdpY21pcnJvci94cmFuZHJfb3B0cyIgXTsgdGhlbgogICAgICAgZWNobyAi cnVubmluZyB4cmFuZHIgd2l0aCBhcmd1bWVudHMgXCIkKGNhdCAvZXRjL21hZ2ljbWlycm9yL3hy YW5kcl9vcHRzKVwiIgogICAgICAgRElTUExBWT06MCB4cmFuZHIgJChjYXQgL2V0Yy9tYWdpY21p cnJvci94cmFuZHJfb3B0cykKZWxzZQoJZWNobyAibm90IHJ1bm5pbmcgeHJhbmRyIgpmaQoKeHNl dHJvb3QgLXNvbGlkIGJsYWNrCgppZiBbIC1yICIvZXRjL21hZ2ljbWlycm9yL3hfYmFja2dyb3Vu ZF9pbWFnZSIgXSAmJiBbIC1yICIkKGNhdCAvZXRjL21hZ2ljbWlycm9yL3hfYmFja2dyb3VuZF9p bWFnZSkiIF07IHRoZW4KCXhsaSAtb25yb290ICQoY2F0IC9ldGMvbWFnaWNtaXJyb3IveF9iYWNr Z3JvdW5kX2ltYWdlKQpmaQoKd2hpbGUgOjsgZG8gc2xlZXAgMTAwMDA7IGRvbmUKCg=='could be replaced by
cat > /tmp/mm-install/xinitrc <<"EOF" #!/bin/sh xset s off # don't activate screensaver xset -dpms # disable DPMS (Energy Star) features. xset s noblank # don't blank the video device if [ -r "/etc/magicmirror/xrandr_opts" ]; then echo "running xrandr with arguments \"$(cat /etc/magicmirror/xrandr_opts)\"" DISPLAY=:0 xrandr $(cat /etc/magicmirror/xrandr_opts) else echo "not running xrandr" fi xsetroot -solid black if [ -r "/etc/magicmirror/x_background_image" ] && [ -r "$(cat /etc/magicmirror/x_background_image)" ]; then xli -onroot $(cat /etc/magicmirror/x_background_image) fi while :; do sleep 10000; done EOF -
RE: Docker install on synology nas
looks like the volumes on the host were created by
root. The user in the container runs as usernodewith uid/gid 1000.So you can try
a) cd to
/volume1/docker/on the host and runchown -R 1000:1000 ./magicmirror(you have to do this asroot)or
b) run the container as user
root, you have to add--user root \to the
docker run ...command -
RE: Docker install on synology nas
to understand what is happening I need
- the full logs of the container
- the start command (full
docker run ...or compose file)