-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Undefined array key "storage_string_id" at /apps/files_sharing/lib/SharedStorage.php#483 #50235
Comments
Maybe it is caused by this change: 926b9d3 Edit: Reverting this change seems to solve the problem, but I don't know if this will break something other elsewhere. |
This comment has been minimized.
This comment has been minimized.
I literally have thousands of errors since updated to 30.0.5. All migrations and complementary db operations have ben ran. |
This is my report
|
Same here |
Bug description
After updating from 29.0.10 to 29.0.11.1, I got lots of errors in the Nextcloud logfile, all of the same kind for a WebDAV PROPFIND operation with different filenames.
Steps to reproduce
Expected behavior
No errors in log
Nextcloud Server version
29
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
Apache (supported)
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Updated from a MINOR version (ex. 28.0.1 to 28.0.2)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
The code at the error position is this:
I tried to find something, but the $node there does not contain the key storage_string_id, it looks like there are only the columns from the filecache table, so only the numerical storageid is there. I don't know where this is generated / comes from, the $this->getShare() returns a IShare supershare attribute, which is set via $arguments in the constructor, so I don't know how to fix it.
The text was updated successfully, but these errors were encountered: