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

[BUU] Dismissing changes is not working #12473

Open
RachL opened this issue May 14, 2024 · 6 comments
Open

[BUU] Dismissing changes is not working #12473

RachL opened this issue May 14, 2024 · 6 comments
Assignees
Labels
bug-s2 The bug is affecting any of the non-critical features described in S1 and there is no workaround.

Comments

@RachL
Copy link
Contributor

RachL commented May 14, 2024

Description

Some product are in a corrupted states, which prevent from dismissing changes and leaves some product pages stuck at the editing state.

this can be seen as super admin :

  • on page 1 in staging AU
  • on page 2 in staging FR

Steps to Reproduce

, We don't know how these products ended up in that state

Animated Gif/Screenshot

image

Workaround

none

Severity

bug-s2: a non-critical feature is broken, no workaround

@RachL RachL added the bug-s2 The bug is affecting any of the non-critical features described in S1 and there is no workaround. label May 14, 2024
@dacook
Copy link
Member

dacook commented May 15, 2024

With some experimenting I found it's due to the "None" (empty) tax category. Will have a look at what we chagned recently.

Also thinking about how we can surface unexpected errors like this better.

Screenshot 2024-05-15 at 4 19 11 pm

@dacook
Copy link
Member

dacook commented May 15, 2024

Turned this off on au_staging and it now works :D

Screenshot 2024-05-15 at 4 52 04 pm

It was already off on fr_staging. I'm not exactly sure what the problem was.
On p2 there was a variant with "None", so I updated it. 2 errors went to 1. Then I updated it back to "None". 1 error became 0.
So I suspect there was something wrong with two other records, but pressing save on them might have fixed it. I can't find any other pages with errors.

✅ So all fixed on AU and FR staging servers

I've crated a PR to help debug this kind of thing with a row line indicator:
#12479. I'll ask MArio what he thinks about the design.

I also noticed a performance problem due to a recent PR. Will raise an issue I think.

@filipefurtad0
Copy link
Contributor

I wonder if this was not introduced in:
#11369

@dacook
Copy link
Member

dacook commented May 22, 2024

Still a problem, demonstrated in #12486 (comment)

@dacook
Copy link
Member

dacook commented May 27, 2024

I found the second cause of this above issue, described and proposed fix here:

@dacook
Copy link
Member

dacook commented May 28, 2024

Just came across another example of invalid data, in ca_prod: https://openfoodnetwork.ca/admin/products/22100/edit

This product has no producer, but that's not valid. The producer dropdown is not set up to show an empty selection, and so the first option is selected.
The proposed fix will simply highlight this, like so:

Screenshot 2024-05-28 at 10 59 28 am

Some other possible fixes are mentioned on the PR, but maybe this will be enough.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug-s2 The bug is affecting any of the non-critical features described in S1 and there is no workaround.
Projects
Status: In Progress ⚙
Development

No branches or pull requests

3 participants