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

bug: csv exports fail due to missing directory structure for @medusajs/file-local #7542

Closed
matmar10 opened this issue May 30, 2024 · 2 comments

Comments

@matmar10
Copy link

Bug report

Describe the bug

The download export orders & products as CSV feature doesn't work by default with @medusajs/file-local because the directory structure does not exist by default.

Manually initializing the directories: uploads/exports/products and uploads/exports/orders and setting writeable permissions fixes the issue.

System information

Medusa version (including plugins): "@medusajs/medusa": "^1.20.6", | "@medusajs/file-local": "^1.0.3",
Node.js version: 10.12.2
Database: Postgres 16
Operating system: Mac, Linux
Browser (if relevant): N/A

Steps to reproduce the behavior

  1. Log In
  2. Go to Products or Orders in admin
  3. Click "Export Products" or "Export Orders"
  4. Click notifications in top right
  5. Wait for export to complete
  6. Click download
  7. See 404 error thrown & no file is created
  8. Create empty directories uploads/exports/products and uploads/exports/orders
  9. Set permissions as writeable for these directories
  10. Redo steps 3 through 6
  11. Observe file is now downloadable

Expected behavior

Either:

  1. Directory structure should be auto-initialized in file system -and/or-
  2. Docs should indicate you need to create these & set permissions -and/or-
  3. Error should be generating indicating it needs to be created -and/or-

Additional context

Relates to #7506 & #6282

Copy link
Contributor

github-actions bot commented Oct 8, 2024

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 3 days.

@github-actions github-actions bot added the Stale label Oct 8, 2024
Copy link
Contributor

This issue was closed because it has been stalled for 3 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant