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

Unable to import Members - ENOENT: no such file or directory #13216

Closed
vicky002 opened this issue Aug 7, 2021 · 8 comments
Closed

Unable to import Members - ENOENT: no such file or directory #13216

vicky002 opened this issue Aug 7, 2021 · 8 comments
Labels
bug [triage] something behaving unexpectedly good first issue [triage] Start here if you've never contributed before. help wanted [triage] Ideal issues for contributors to help with stale [triage] Issues that were closed to to lack of traction

Comments

@vicky002
Copy link

vicky002 commented Aug 7, 2021

Issue Summary

I have Ghost Self-hosted.

When I try to import my subscribers from Substack, it shows this error as shown in the image.

I tried searching everywhere but no solution. I also tried to manually create the Members folder on the server but still no luck.
CleanShot 2021-08-07 at 20 42 50@2x

A summary of the issue and the browser/OS environment in which it occurs.

To Reproduce

Go to your Self-hosted Ghost blog

  1. Create a CSV file containing a few emails
  2. Try to import that CSV file

Technical details:

  • Version 4.7.0
  • Environment production
  • Database sqlite3
  • Mail SMTP
  • Server: Azure App Service
@ErisDS ErisDS added bug [triage] something behaving unexpectedly help wanted [triage] Ideal issues for contributors to help with good first issue [triage] Start here if you've never contributed before. labels Aug 12, 2021
@ErisDS
Copy link
Member

ErisDS commented Aug 12, 2021

This is a bug with windows paths. Ghost is primarily written for & tested on unix/linux/mac based environments but we're happy to accept PRs fixing this.

@tawandamoyo
Copy link

tawandamoyo commented Aug 23, 2021

Hi @ErisDS , I'd like to try my hand on this but not sure where to start. Also would I need to be on a Windows machine?

@ZaidYounan
Copy link

ZaidYounan commented Aug 25, 2021

Hi, I think I'm onto a solution but not exactly sure how to implement it within your code. The top comment on this stackoverflow thread does a good job of describing it.

https://stackoverflow.com/questions/25090101/is-there-a-difference-between-and-paths

It seems like there is a disconnect between the path being supplied, and how the path seperator is being interpreted. I can think of a few possible solutions to try because the path module (which you've already imported) provides some methods to get around this, like this one.

https://nodejs.org/docs/latest/api/path.html#path_path_tonamespacedpath_path

Which would return the file path with the appropriate path prefix (i assume this would be C:\\) ONLY for windows machines, and for other systems it would simply not modify the file path. But I'm new and I'm currently unfamiliar with node.js, so haven't yet figured out how to implement that to test it.

@deepto98
Copy link

deepto98 commented Oct 5, 2021

@ErisDS If this issue is still open, can I pick it up?

@ihiteshsharma
Copy link

Hi, I have a self-hosted Ghost blog at ihiteshsharma.com, I did the following steps to reproduce the error:

  1. I downloaded the CSV Template File which Ghost Import Members option has (refer Images below): Members -> Gear Icon -> Import Members
  2. I added 1 email and renamed the file to contain spaces as per windows paths.
  3. The file was detected successfully, with no ENOENT errors

I couldn't help but notice you are trying to migrate the subscribers from Substack. Ghost needs the subscriber data in the format to correctly detect fields. Did you try the approach as recommended by Ghost here and here ?

In case I missed anything, let me know.

image
image
image

danimajo added a commit to danimajo/Members that referenced this issue Dec 22, 2021
refs TryGhost/Ghost#13216

- Fixed CSV User Import on Windows
@danimajo
Copy link
Contributor

See TryGhost/Members#355

@github-actions
Copy link
Contributor

Our bot has automatically marked this issue as stale because there has not been any activity here in some time.

The issue will be closed soon if there are no further updates, however we ask that you do not post comments to keep the issue open if you are not actively working on a PR.

We keep the issue list minimal so we can keep focus on the most pressing issues. Closed issues can always be reopened if a new contributor is found. Thank you for understanding 🙂

@github-actions github-actions bot added the stale [triage] Issues that were closed to to lack of traction label Apr 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug [triage] something behaving unexpectedly good first issue [triage] Start here if you've never contributed before. help wanted [triage] Ideal issues for contributors to help with stale [triage] Issues that were closed to to lack of traction
Projects
None yet
Development

No branches or pull requests

8 participants
@ErisDS @danimajo @vicky002 @tawandamoyo @ZaidYounan @ihiteshsharma @deepto98 and others