It just hangs after accepting the TOS or subscribing to the newsletter
It seems that this is associated to being behind a firewall or a proxy. You can apply this workaround.
I got “npm ERR! Failed to parse json”
Check your project's
package.json file with JSONLint, to ensure it does not contain any errors, such as missing semicolons, quotes or commas.
I am getting permission errors after I install things
Chances are this isn't a problem within DocPad, but rather one of your node/npm installations. Run the following in Terminal, once done, try your original action again:
sudo chown -R $USER /usr/local ~/.npm chmod -R 755 ~/.npm
If that fails, we'd recommend either:
- Re-Installing Node.js with Bevry's recommended installation instructions
- Asking about it on the Node.js IRC Chat Room (
When I run 'npm install' on windows, I get 'gyp ERR! configure error'
- For Windows XP/Vista/7 Install:
- For 64-bit builds of Nod.jse and native modules you will also need:
- Windows 7 64-bit SDK
- If the install fails, try uninstalling any C++ 2010 x64&x86 Redistributable that you have installed first.
- If you get errors that the 64-bit compilers are not installed you may also need:
- For Windows 7/8:
When I run
docpad run on Windows, it asks me what program I would like to open the file in
It turns out that Windows will prefer to treat the local
docpad.js file as the executable versus the global
docpad.cmd file. To get around this, type
docpad.cmd run instead in projects that have a
docpad.js file. More information here.
Watching doesn't work; works only some of the time; I get
File watching is a pretty timid thing that we are currently working on a lot to make better. There are currently two methods we can watch files,
watch is the default and uses the operating system's watching mechanisms, however sometimes the operating system's watching mechanisms may not be the best. If that is the case, we'd like to switch our watching method to
watchFile which is a slower, but does work when
watch doesn't. To do this, add the following to your docpad configuration file:
watchOptions: preferredMethods: ['watchFile','watch']
Mac OS X users are most likely to encounter this issue.
I got “We couldn't find an existing DocPad project inside your current directory…”
This occurs when you run
docpad run inside a directory that already has existing files, but doesn't have a structure that resembles a DocPad project. We can't directly ask you if you would like to use an existing skeleton for the basis of your new website, as pulling in a skeleton inside a non-empty directory may overwrite your existing files. If would like to still use a skeleton for the basis of your new website, you will have to run docpad inside a new empty directory. If you would like to start your website from scratch (not use an existing skeleton) then you can follow the Getting Started guide. Hope that helps :) If you need more help then check out our Support Channels.
I'm getting “Could not locate git binary”
- Reinstall git and make sure to select the option during installation that asks if you would like to add it to your PATH variable (may also be called, would you like git to be available to the command line)
- Manually add the location your git binary resides in to your PATH variable
I'm getting “EMFILE, too many open files”
As node.js is like an octopus, able to do many things at the same time, sometimes node.js will always try to do too many things than the operating system will let it. In which case, you can increase the amount of files allowed at the same time by running
ulimit -n 8192 in your terminal.
How can I make DocPad go even faster?
There are a few things you can do:
- Move files that you do not reference in content listings to a raw directory with the raw plugin
standalone: trueto the meta data of documents that you regenerate often
- E.g. instead of using sass, use nodesass, stylus, or less
- Help us implement performance optimisations
I upgraded, and it doesn't work
Whenever I output a variable (like
content) it is escaped (
< rendered as
Template engines by default escape all variable output. Escaping is when we turn things like the open bracket
< into it's html entity equivalent
<. This helps prevent malicious code accidentally being injected into your website which can open the door to XSS attacks. As such, we have to use a special syntax to keep the variable unescaped when outputted. The special syntax is different for the templating engine your using, so here are the ways we know:
<%- content %>instead of
<%= content %>
!= contentinstead of
I get a whole bunch of npm / missing module/package / installation failed errors
If you are using Dropbox (an online syncing & backup tool) and your project is inside your DropBox folder, then click the dropbox menu icon and select “Pause Syncing”. Once this is done, try whatever you were doing again, you may need to run
rm -Rf node_modules; npm install as well. Once it's all working, then you're free to resume dropbox syncing.
If you're still experiencing issues, then be sure to post about it on the issue tracker.
The growl notifications aren't displaying?
This means you need to download and install the growlnotify extra from the growl website. What this package does it provides command line applications the ability to call growl which is needed as docpad is a command line application.
The exception raised by the jade plug-in during documents generation makes no sense
The Jade compiler uses the full file content on the disk to show where the parsing error is. But since Docpad strips the meta header before submitting the data to the jade compiler, you must add the number of lines of this header to get the right error spot in your code.