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

When save product after modified attribute combination there is a warning. #300

Open
Lurvy opened this issue Aug 5, 2022 · 2 comments · May be fixed by #301
Open

When save product after modified attribute combination there is a warning. #300

Lurvy opened this issue Aug 5, 2022 · 2 comments · May be fixed by #301

Comments

@Lurvy
Copy link

Lurvy commented Aug 5, 2022

When save product after modified attribute combination there is a warning: "You can't edit the product because has been changed. Please refresh page and try to change again". If continue to click save, then "Product attributes" and "Attribute combinations" will could not add new or delete.

  1. Edit product, Click Tab "Inventory", Change "Manage inventory method" to "Track inventory by product attributes", Save it.
  2. Add some "Product attributes" and checked "Allow to use in attribute combinations", add some "Attribute value".
  3. Modify (Add / Delete / Generate / Clear) "Attribute combinations".
  4. Click "Save" or "Save and Continue Edit".
@Lurvy
Copy link
Author

Lurvy commented Aug 5, 2022

New Finding:

After published the fixed patch to production Linux server, I found only Delete "Attribute combinations" still had problem, Add / Generate / Clear are no more problems. Finally I found after deleted, the request of the Attribute combinations List can't got the newest Ticks. Then I click "Clear memory cache" on production site admin panel, and the newest Ticks got.

But When I debug in Windows with VS2022, there are all right.

So there is some problems about caching in Linux? And it is strange that Delete and Clear are use the same method to remove cache, why only Delete has problem?

Most of this issue has been solved, and the rest needs to be tracked.

@Lurvy
Copy link
Author

Lurvy commented Aug 6, 2022

Pushed a new commit, now all are right!

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

Successfully merging a pull request may close this issue.

1 participant