Skip to content

[bug]: Setting Cover Images Fails Without Error #6083

@GlitchWitch

Description

@GlitchWitch

Is there an existing issue for this?

  • I have searched the existing issues

While it is possible this is a duplicate of #5817, we are not experiencing the other issues noted by that user and can upload photos in all other areas of the application without issue.

Current behavior

When attempting to set a cover image, such as on a project or your own profile, the image does not actually get set.

Steps to reproduce

As an example, when saving my profile the following request body is sent.

[...omitted for brevity...],
"avatar_url":"/api/assets/v2/static/redacted/","cover_image_url":"https://images.unsplash.com/photo-1721332154373-17e78d19b4a4?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3w2NzgxMTB8MXwxfGFsbHwxfHx8fHx8fHwxNzMyMjM1NzYyfA&ixlib=rb-4.0.3&q=80&w=1080",
[...omitted for brevity...]}

However, the following response received shows that the cover_image_url along with other fields such as the "Role" are not actually saved by the application.

{
    [...omitted for brevity...]
    "cover_image": null,
    "cover_image_asset": null,
    [...omitted for brevity...]
}

The video below shows the issue. In the video I attempt to set a new cover image via upslash, I update the project, and then refresh the page. I repeat this again to show the error remains.

Screencast.from.2024-11-21.18-51-17.webm

Environment

Production

Browser

Google Chrome

Variant

Self-hosted

Version

v1.4.0 with prime-cli v1.7.0 a18c053

Additional Notes

This is a freshly installed environment setup less than 24 hours ago. The issue persisted before upgrading to Pro. prime-cli healthcheck shows all clear.
image

Metadata

Metadata

Assignees

Labels

🐛bugSomething isn't working

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions