Details
-
Bug
-
Resolution: Won't Fix
-
Medium
-
None
-
4.6.0-beta2, 4.5.4
-
- Varnish
- mysql
- php 7.4
Description
Preconditions:
- In ibexa.yaml file, defined under site siteaccess:
storefront:
catalog:
detault: {catalogName}
Steps to reproduce
- Log in to back office.
- Go to Product-catalog / Catalogs.
- Add a new catalog with the same name as defined in ibexa.yaml (do not change catalog status - leave it as draft).
- Go to /product-catalog page (storefront).
Actual result:
An error 400 bad request occurs when defined in ibexa.yaml catalog has different status than published.
Oops! An Error Occurred The server returned a "400 Bad Request". Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.
Expected result:
Correct information that the added catalog must have a specific status (published).
Edit:
When defined in ibexa.yaml catalog is not added in back office, there is also incorrect information on /product-catalog page (storefront).
The error code is correct 404 Not found but message is not.
Oops! An Error Occurred The server returned a "404 Not Found". Something is broken. Please let us know what you were doing when this error occurred. We will fix it as soon as possible. Sorry for any inconvenience caused.
This might be confused for maintainer / partner. We have to display correct message that catalog with {catalogName} has not been found.
Designs
Attachments
Issue Links
- discovered while testing
-
IBX-5092 As a QA I want to implement test scenarios to coverage storefront
- QA