Description
⚠️ This issue respects the following points: ⚠️
- This is a bug, not a question or a configuration/webserver/proxy issue.
- This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
- Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
- I agree to follow Nextcloud's Code of Conduct.
Bug description
After the upgrade to NC 31.0.2 (from 31.0.1) several errors of the kind:
Implicitly marking parameter X as nullable is deprecated, the explicit nullable type must be used instead at Y
are logged once when visiting the NC website for the first time. The affected files and line numbers are:
3rdparty/scssphp/scssphp/src/Compiler.php#5366
3rdparty/scssphp/scssphp/src/Node/Number.php#581
3rdparty/scssphp/scssphp/src/Parser.php#143
3rdparty/scssphp/scssphp/src/Warn.php#62
Those log entries are flagged as errors, however, they should actually be only warnings as the functionality of NC is not negatively affected.
(See also #50792)
Steps to reproduce
- Upgrade from NC 31.0.1 to 31.0.2
Expected behavior
No error messages/php files adopted to PHP 8.4
Nextcloud Server version
31
Operating system
Other
PHP engine version
PHP 8.4
Web server
Apache (supported)
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 32.0.1 to 32.0.2)
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response