You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The product must be included in the store’s logistics settings. This means that all settings for inventory, loading docks, carrier, weight, dimensions, etc, must correspond to the product in question.
Current behavior
Currently, the 404 page component only validates if the url exists, but it should also validate the product information.
Steps to reproduce
A step-by-step on how to reproduce the bug behavior.
You need a product that has no price or stock.
Then access the PDP in Faststore.
It will show you a product without price or stock.
Possible Solution
Maybe the error should be addressed from two points:
Describe the bug
Faststore shows the PDP of products with no associated price, stock, or logistics in the backend.
Expected behavior
The PDP should not be displayed if the product does not meet the conditions of the documentation:
Why is the product not visible on the website?
The product and its SKUs must be in the Catalog with all the details filled in correctly, as explained in the Adding products tutorial.
The product must have a price associated with it.
The product must be included in the store’s logistics settings. This means that all settings for inventory, loading docks, carrier, weight, dimensions, etc, must correspond to the product in question.
Current behavior
Currently, the 404 page component only validates if the url exists, but it should also validate the product information.
Steps to reproduce
A step-by-step on how to reproduce the bug behavior.
Possible Solution
Maybe the error should be addressed from two points:
ErrorBoundary:
.faststore\src\sdk\error\ErrorBoundary\ErrorBoundary.tsx
And the PageProvider:
node_modules@faststore\core\src\sdk\overrides\PageProvider.tsx
Additional context
Add any other context, screenshots, or comments about the problem.
The text was updated successfully, but these errors were encountered: