Skip to content
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

Closed
5 of 8 tasks
Elendiir1970 opened this issue Sep 28, 2024 · 6 comments · Fixed by #48439

Comments

@Elendiir1970
Copy link

⚠️ This issue respects the following points: ⚠️

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
conflict_message

Steps to reproduce

  1. Open Management Seeting
  2. Select Design
  3. Upload a new background image (i tried a 8MB *.jpg)
  4. Error message should appear

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?

  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

@Elendiir1970 Elendiir1970 added 0. Needs triage Pending check for reproducibility or if it fits our roadmap bug labels Sep 28, 2024
@joshtrichards
Copy link
Member

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.

@joshtrichards joshtrichards added regression 1. to develop Accepted and waiting to be taken care of and removed 0. Needs triage Pending check for reproducibility or if it fits our roadmap labels Sep 28, 2024
@Elendiir1970
Copy link
Author

Hi Josh,
you are right. I have upgrade my docker image with the old image set. This did work fine. After the update to version 30 the background image still got displayed.
But now changing the image is not possible anymore. I also tried to delete/remove the old image. This worked as expected. I now have a background consisting out of a single solid color. But I am not able to change the background image. When I do so the error messages appears.
Cheers
Fritz

@Elendiir1970
Copy link
Author

The back arrow does reset the image to default. But still I do get the same error:
conflict_message

@kesselb
Copy link
Contributor

kesselb commented Sep 28, 2024

cc @nextcloud/server

@susnux susnux added 3. to review Waiting for reviews and removed 1. to develop Accepted and waiting to be taken care of labels Sep 28, 2024
@AnonymousX86
Copy link

Issue is still present in this build of 30.0.
Image
I have already tried removing and uploading once more. Even with Nextcloud restart.

@joshtrichards
Copy link
Member

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):

#48452

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants