Fehler PHP Using ${var} in strings is deprecated, use {$var} instead at /var/www/nextcloud/3rdparty/scssphp/scssphp/src/Compiler.php#3491
flooded again the logs after Update from NC 26.0.0 to 26.0.1 because the scsphp coming with original 26.0.1 files is still 1.8.x instead of 1.11.1
This issue is closed on github with hint to 1.11.1
Is it a mistake that the 3rdparty folder scsphp still contains the old version?
After changing scsphp 1.8.x to the src files from github (here: https://github.com/scssphp/scssphp/releases/tag/v1.11.0) the errors in log are gone.
Fehler index Exception: Class "ScssPhp\ScssPhp\Block\DirectiveBlock" not found in file '/var/www/nextcloud/3rdparty/scssphp/scssphp/src/Parser.php' line 855
that affects the missing
GET /apps/theming/theme/opendyslexic.css?plain=
I can get rid of those messages by symlinking my default.css to this place.
So i mkdir /var/www/nextcloud/apps/theming/theme
make it owned by www-data by
[PHP] Fehler: Using ${var} in strings is deprecated, use {$var} instead at /var/www/nextcloud/3rdparty/scssphp/scssphp/src/Compiler.php#3491
GET /apps/theming/theme/light.css?plain=0&v=b6692ea5
from LOCAL-IP at 2023-05-28T08:37:28+02:00
are back in the original files of the update to NC 26.0.2
My System is ubuntu 22.04.2, PHP 8.2.6
I still have the …/3rdparty/scssphp/scssphp/src folder of the 26.0.1 in my updater_xxxxx/backups folder.
The error “…Using ${var} in strings is deprecated, use {$var} instead…” leads me to the to this
Thanks for reply, i’ve checked my NC config and found
'loglevel' => 3,
And it seems to be more than a warning. In my logs it is accounted as “Fehler” (means: Error) - in this case concerning PHP.
Never the less i must have overlooked the info that this fix will not be backported to the 26.0.x line.
So i will have to fix it in upcoming 26.0.3+ updates as well until it is worth to change to 27.0.x line.
I think keeping logfiles small / empty of warnings/errors/failures is the purpose, so if someone out there is getting those “errors” and the the change make you get rid of the logmessages - fell free to try the fix
I ran into this too after updating to NC v26.0.2.1 yesterday (more than 3 months after initial series 26 release).
Fehler PHP Using ${var} in strings is deprecated, use {$var} instead at /var/www/nextcloud/3rdparty/scssphp/scssphp/src/Compiler.php#3491
vor 10 Minuten
Fehler PHP Using ${var} in strings is deprecated, use {$var} instead at /var/www/nextcloud/3rdparty/scssphp/scssphp/src/Compiler.php#3491
vor 10 Minuten
Fehler PHP Using ${var} in strings is deprecated, use {$var} instead at /var/www/nextcloud/3rdparty/scssphp/scssphp/src/Compiler.php#3491
vor 10 Minuten
Fehler PHP Using ${var} in strings is deprecated, use {$var} instead at /var/www/nextcloud/3rdparty/scssphp/scssphp/src/Compiler.php#3491
vor 10 Minuten
Fehler PHP Using ${var} in strings is deprecated, use {$var} instead at /var/www/nextcloud/3rdparty/scssphp/scssphp/src/Compiler.php#3491
vor 10 Minuten
TBH it’s a bit frustrating that even waiting for such a long time and choosing a .0.2.1 point release for the first major release update is still no guarantee (no one ever told there is one for FOSS) for not running into issues.
Off-topic: Meanwhile it very often feels like bringing out new major releases in much shorter time with a lot of release announcements has priority over stability - just look at all the apps which simply can’t catch up with the new major release cycles and lack support for new major releases even months after release. So hacking the appinfo.php is one of the most important (and a bit risky) things one should be aware of trying to stay some kind of up to date. Rant over.
In this specific case I don’t get if there’s an actual negative outcome or it’s “just” the log spamming.