-
-
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] [25.0.0RC4] Custom background doesn't stay (404) #34596
Comments
how can getUser() be null ? is there an issue with the lifecycle ? |
I've done further tests and directly after setting the background, I see background.jpg appearing in appdata under the "theming" app but as soon as I shift+refresh, that file disappears maybe the migration code / cron (ajax cron on local env) is wrongly deleting the file. Ref: #34587 |
@blizzz FYI |
it's not the migration job, when commented out a shift+refresh (at most 2x) will delete "background.jpg". not sure if it's the null user or something else at play |
also note, I have custom theme colors set, in case it matters:
|
it's not the "/background" endpoint, I tried refreshing it in a separate tab and background.jpg does not get deleted maybe it's the settings page that resets it upon reload? |
ok, we found the issue, it has multiple layers:
|
Fix is here: #34599 |
I do not believe this is fixed. I just upgraded from NC 24.0.5 to 25.0.0 (stable) and the background image disappeared. The previously-set background image caused 404s (I did not immediately notice it after the upgrade due to client-side caching, I assume). But today, it resulted in 404s for the background image, and in the admin panel the background image was also empty. |
I just upgraded from 24.0.7 to 25.0.1 and the custom theming was not applied. This affects the background, as well as the custom logos. |
Same here. Upgraded two NextCloud instances to 25.0.2 and both of them have no background images now. One of them had a custom logo as well which is also gone now. Logs on both instances show this:
Or in raw:
|
And I think the issue is this line: This should probably be $this->jobList->add(self::class, ['stage' => self::STAGE_EXECUTE]); |
hi, this error shows up on my new 25.0.2 install, and I haven't even set a custom background. the error shows up when I try to manually run cron.php (which I have to do in order to troubleshoot cron, because the cron job just isn't working for some reason) |
I'm exactly on the same page as @jdkruzr here. I launched cron.php manually once to test, and subsequent runs show this error.
|
@Draluy I have since gotten it working, although I couldn't tell you exactly how. But, maybe of some note: my installation isn't even Dockerized and we had the same issue. |
Just saw that error in the snap when upgrading from v24 to v25. Something seems to be broken, but whatever it is only seems to happen on upgrade-- works fine once the upgrade is done. Maybe a left-over queued job from v24 with a different argument than expected in the v25 codebase? |
Bug description
Getting a 404 on a custom background:
GET https://.../index.php/apps/theming/background
file "background.jpg" is missing on disk in "data/appdata_*/theming/alice"
Steps to reproduce
Expected behavior
Background appears and exists on disk
Installation method
No response
Operating system
No response
PHP engine version
No response
Web server
No response
Database engine version
No response
Is this bug present after an update or on a fresh install?
No response
Are you using the Nextcloud Server Encryption module?
No response
What user-backends are you using?
Configuration report
No response
List of activated Apps
Nextcloud Signing status
No response
Nextcloud Logs
Additional info
No response
The text was updated successfully, but these errors were encountered: