Closed dmark closed 8 years ago
Workaround: Disable the pelican_comment_system feeds while developing.
pelicanconf.py
: PELICAN_COMMENT_SYSTEM_FEED = None
publishconf.py
: PELICAN_COMMENT_SYSTEM_FEED = 'feeds/comment.%s.atom.xml'
The problem is that if pelican runs in autoreload mode it does not reinitialize everything. (does not send signals.initialized
)
And therefore the pelican_comment_system uses the writer
of the previous run (which then complains that it overwrites stuff)
To fix this we probably need a new signal in Pelican.run
so plugins can reinitialize if needed.
This is a new pelican 3.6.3 installation, with content files migrated from an older installation. If I edit any of my content files after having run "develop_server.sh start", I get the error below. If develop_server.sh is not running, there are no errors after manually running pelican.