-
-
Notifications
You must be signed in to change notification settings - Fork 10.4k
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
grunt init
bower task fails if space in directory name (and as a result /ghost/signup page appears blank)
#3206
Comments
Man, awesome, thanks for figuring this out. We just had someone come into IRC because their bower init never worked; this was almost certainly the problem. Cheers |
closes TryGhost#3206 - We were escaping paths for the bower commands, but this didn't work on windows - Use the same pattern for the coverage command
I thought we had this fixed, seems it was broken on Windows still. I have a fix which I'm currently testing cross platform. @jamesmartinduffy just an FYI, when raising issues please include details of your environment. To help you know what sort of info to include we have a bug reporting template in the contributing guidelines. |
Sorry – this is running locally on OS X 10.9.4, node v0.10.21, and Ghost 0.4.2. |
This did not fix it for me. Running "shell:bower" (shell) task
Verifying property shell.bower exists in config...OK
File: [no files]
Options: stdout, stderr, stdin, failOnError
Command: /Users/jamesduffy/Dropbox\ (Personal)/_Development/Ghost/node_modules/.bin/bower --allow-root install
/bin/sh: -c: line 0: syntax error near unexpected token `Personal'
/bin/sh: -c: line 0: `/Users/jamesduffy/Dropbox\ (Personal)/_Development/Ghost/node_modules/.bin/bower --allow-root install'
Warning: Command failed: /bin/sh: -c: line 0: syntax error near unexpected token `Personal'
/bin/sh: -c: line 0: `/Users/jamesduffy/Dropbox\ (Personal)/_Development/Ghost/node_modules/.bin/bower --allow-root install'
Use --force to continue.
Aborted due to warnings. Same error. Perhaps its due to having parentheses in the path? I just pulled the latest, last commit is bf3078c, Ghost version 0.5.0-rc2. Again, I'm on OSX 10.9.4. |
I have tested on OSX 10.9.4 and it shows the following output:
But I guess that the brackets are causing another (similar) problem. //cc: @ErisDS Update: confirmed
|
Looks like parentheses do need to be escaped, since running this command works fine:
But I may be in the minority here having that in my path. I have Is there a reason for not just using a relative path instead of |
@jamesmartinduffy Hopefully #3700 will fully resolve the issue for you? (I've tested on win and mac) |
Yes, that resolves it. |
Wooooooooooooooooooooooooooooooooooooo 🎈 |
Hey guys,
Just cloned a fresh copy of the repo to start on some theme development, and ran into this issue. Basically after following the install steps and navigating to /ghost/signup, I was served with a blank page. After looking into it, it appears to be caused by
grunt init
's "shell:bower" task failing due to my local directory having a space in it.After moving the file to a directory with no space,
grunt init
works fine.Not sure if it's within the Ghost team's power to fix or if this is an issue with the bower module, but figured I'd open an issue in case other people are having this problem in the future.
The text was updated successfully, but these errors were encountered: