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

Server error msg is not properly rendered when emptying recycle bin #17909

Open
kristofferwebmind opened this issue Jan 8, 2025 · 2 comments

Comments

@kristofferwebmind
Copy link

Which Umbraco version are you using? (Please write the exact version, example: 10.1.0)

13.5.2

Bug summary

When emptying the recycle bin, an error message popup was displayed, but the expressions themselves are rendered rather than the expression results, making the error messages obscured:

image

Specifics

After the popup was closed, the process of emptying the recycle bin looked like it was continuing (however, there is no easy way to know whether it is actually working or if it is just the GUI that looks that way). After a while, the Umbraco Identity session timed out (site is running on Umbraco Cloud). After logging in again, the recycle bin was empty. There are no errors visible in the log viewer.

image

image

Steps to reproduce

Not sure...

Try and force an error in the empty recycle bin code

Expected result / actual result

The result of expressions like {{model.error.errorMsg}} should be rendered in the popup rather than the expressions themselves.

Copy link

github-actions bot commented Jan 8, 2025

Hi there @kristofferwebmind!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

  • We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
  • If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
  • We'll replicate the issue to ensure that the problem is as described.
  • We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂

@Migaroez
Copy link
Contributor

Hey @kristofferwebmind, I was able to trigger something similar by making part of the authorization pipeline crash as described in the linked PR

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

No branches or pull requests

2 participants