Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP

Loading…

Failed to generate site "Currently on renderFiles at 99%" #433

Closed
anasnakawa opened this Issue · 8 comments

2 participants

@anasnakawa

Specifications:

node v0.8.19  <-- same thing happened with 0.8.18
npm 1.2.10
docpad 6.18.0
OSX 10.7.5

Project Code

What I did:

either docpad run or docpad generate --env static

What I expected:

when using docpad run to have the site rendered on the browser
when using docpad generate --env static to see the files of the generated site

What happened:

both ways (dynamic / static), docpad kept telling me this, and nothing changed in the output directory..

info: Currently on renderFiles at 99%
@balupton
Owner

Hey mate, please run docpad run -d and post the output in a gist. That will contain a lot more info for us to debug with :) Not able to check out the repo as our wifi her over the next few days is very dodgy.

@anasnakawa

here you go gist log

@balupton
Owner

Thanks for that. What happens when you upgrade to the latest version of DocPad?

@anasnakawa

to be honest, i don't know how to upgrade to the latest version..
for example I get this in terminal

notice: There's a new version of DocPad available, you should probably upgrade...
current version:          6.18.0
new version:              6.21.10
upgrade instructions:     http://docpad.org/upgrade

but I can't find any information on the upgrade page on how to upgrade from v6.x

also re-installing via npm did not help, as it will install the same version again 6.18.0

@anasnakawa

just updated to version 6.21 and the problem stills..
didn't know I have to run sudo npm install -fg docpad@6.21 to update..

@anasnakawa anasnakawa closed this
@anasnakawa anasnakawa reopened this
@anasnakawa

problem solved once I re-created the project, looks like i was missing up with package.json file

@anasnakawa anasnakawa closed this
@balupton balupton reopened this
@balupton
Owner

DocPad should not do this regardless of package.json or not. Will leave open until we can find a fix within DocPad.

@balupton
Owner

v6.30.5 will create the packge.json file with the no skeleton option, considering that a good enough fix :)

@balupton balupton closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.