-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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]: Uploading a new Background Image displays error "conflict between new type (mixed) and old type (string)" #48436
Comments
I suspect this only happens if there was a custom image prior to the upgrade. On a new installation (the handiest test environment I have on-hand), this doesn't seem to be a problem (which make sense given what I understand to be the underlying cause). It's possible a temporary workaround would be to use the back arrow / reset to default and/or trash option for the existing image before uploading a new one. |
Hi Josh, |
cc @nextcloud/server |
Issue is still present in this build of 30.0. |
Well, yeah. Because that's the release with the bug in it. :-) The fix is merged and will be in the next maintenance release (30.0.1): |
Guessing we just got to wait for a maintenance release and we should be good to go? Just found it odd that it was going good until now it suddenly started doing this. |
Bug description
Hi,
several people seem to have problems when changing the background image. See the last comments in #45083.
Since nobody has added the issue to the list I just did it.
After upgrading my docker image to the nextcloud version 30.0 I am not able to change the background image anymore. If I do so the image will be uploaded but is not applied. Instead I do get an error "conflict between new type (mixed) and old type (string)".
A screenshot showing the error from the menu Desgin is attached
Steps to reproduce
Expected behavior
The uploaded image should be used as new background image.
Nextcloud Server version
30
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.2
Web server
None
Database engine version
MariaDB
Is this bug present after an update or on a fresh install?
Upgraded to a MAJOR version (ex. 28 to 29)
Are you using the Nextcloud Server Encryption module?
None
What user-backends are you using?
Configuration report
No response
List of activated Apps
No response
Nextcloud Signing status
No response
Nextcloud Logs
No response
Additional info
No response
The text was updated successfully, but these errors were encountered: