-
-
Notifications
You must be signed in to change notification settings - Fork 725
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
Cannot change calculator on existing shipping method #7657
Comments
Is coming up in Bugsnag -https://app.bugsnag.com/yaycode/openfoodnetwork/errors/60a34c07fbf6410007eb6401?event_id=60a34c07007c935b1e800000&i=sk&m=nw I suspect this could be a regression in this release, perhaps to do with adjustments work @Matt-Yorkley ? |
This looks related and perhaps a duplicate of: |
It doesn't seem to be related to adjustments (it's something to do with units and weights), and also doesn't look like it's new in this release... |
Confirmed duplicate of #6300, closing here. |
Description
When a user tries to change an existing shipping method; wants to change calculator from Weights, to Flat Rate, and gets the 'opps, something went wrong' error. Have recreated this in the Aus Demo Hub with same result.
Expected Behavior
Should be able to change the calculator from one method to another method and save with no error
Actual Behaviour
When the user changes the calculator from one method to another method the 'oops, something went wrong' error appears
Steps to Reproduce
Workaround
Create new shipping method and make old shipping method 'display - back office only'
bug-s3: a feature is broken but there is a workaround
The text was updated successfully, but these errors were encountered: