DocPad fails to serve files after the initial generation once the docpad configuration file has been modified #811

Closed
balupton opened this Issue Feb 21, 2014 · 1 comment

Projects

None yet

2 participants

@balupton
Member

Found this a while ago when developing interconnect.

@ahdinosaur also is experiencing it at docpad/docpad-plugin-livereload#17

@balupton balupton referenced this issue in docpad/docpad-plugin-livereload Feb 21, 2014
Closed

reload not working #17

@balupton balupton added a commit that closed this issue Feb 21, 2014
@balupton balupton Fix #811
Turns out that resetCollections was setting docpad.generated to false.
But our docpad.generated = true assignment would only fire if
opts.initial was true. However, that would not be true if we are a
non-initial reset generation.

I’ve moved the reset task to be the first, and moved the opts
assignment after it. So that opts can be assigned based on their
correct values which can be determined after the reset tasks fires or
doesn’t fire.

I’ve also added a check for this invalid state in case it ever occurs
again.
b3402ab
@balupton balupton closed this in b3402ab Feb 21, 2014
@balupton balupton added a commit that referenced this issue Feb 21, 2014
@balupton balupton v6.63.7. Bugfix.
- v6.63.7 February 21, 2014
	- Fixed IE9 and below not understanding the charset we send
		- Thanks to [Eric Vantillard](https://github.com/evantill) for [issue #801](#801)
	- Better debugging for invalid watch states
		- For more information see [issue #792](#792)
	- Fixed DocPad failing to serve files after the initial generation once the docpad configuration file has been modified
		- Thanks to [Michael Williams](https://github.com/ahdinosaur) for [issue #811](#811)
	- Updated dependencies
1868381
@ahdinosaur
Member

livereload of ahdinosaur/init.docpad is now successful. thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment