-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Widget 404 not found #9144
Comments
Some more context: GET /app/@id/__x00__virtual:medusa/widgets/product/details/side/before
If I add widgets: Cannot GET /app/@id/__x00__virtual:medusa/widgets/product/details/side/before |
Updated to preview version 10, no changes (using admin-sdk package). |
I found these error details: 2024-10-07T14:14:22.135453171Z 2:14:22 PM [vite] Internal server error: Failed to resolve import "/src/admin/widgets/product-labels.tsx" from "virtual:medusa/widgets/product/details/before". Does the file exist? It looks as if it tries to import the original component, not the component in the dist folder. Could it be that the original component does not exist when this Vite process runs? Locally it does work as I have the original component in my IDE, but on a remote deployment the original code is not included in the build I believe. |
Bug report
Describe the bug
I added a widget on the product details side section, but it results in a 404 on a production build. On running the dev build, it works fine.
GET https://xyz.abc.nl/app/@id/__x00__virtual:medusa/widgets/product/details/side/before net::ERR_ABORTED 404 (Not Found)
System information
Medusa version (including plugins): 2.0.6
Node.js version: 20.x
Database: PostgreSQL
Operating system: N/A
Browser (if relevant): Chrome
Steps to reproduce the behavior
Expected behavior
Widget should be present and not cause 404
Screenshots
If applicable, add screenshots to help explain your problem
Code snippets
Additional context
Not sure if it matters, but I am using the MEDUSA_BACKEND_URL variable, set to my domain (https://xyz.abc.nl)
The text was updated successfully, but these errors were encountered: