The Wayback Machine - https://web.archive.org/web/20211013014828/https://github.com/TryGhost/Ghost/issues/13216
Skip to content

/ Ghost Public

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

Jump to bottom

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

Open
vicky002 opened this issue Aug 7, 2021 · 5 comments
Open

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

vicky002 opened this issue Aug 7, 2021 · 5 comments
Labels
bug good first issue help wanted

Comments

@vicky002
Copy link

@vicky002 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
Copy link
Member

@ErisDS 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 tawandamoyo commented Aug 23, 2021 •
edited

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?
@chakrabortysayantan699
Copy link

@chakrabortysayantan699 chakrabortysayantan699 commented Aug 24, 2021

Hi @ErisDS , I'd like to give a try to resolve this issue ,I am a beginner please guide me where to start and I am using windows
@ZaidYounan
Copy link

@ZaidYounan ZaidYounan commented Aug 25, 2021 •
edited

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 deepto98 commented Oct 5, 2021

@ErisDS If this issue is still open, can I pick it up?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug good first issue help wanted
6 participants
@ErisDS @vicky002 @tawandamoyo @ZaidYounan @chakrabortysayantan699 @deepto98