+ [2017-06-05T04:40:36Z] jekyllrb Title: jekyll-json/jekyll-json.rb at development · BenRuns/jekyll-json · GitHub (at github.com)
+ [2017-06-05T04:41:41Z] lswart I think I can solve this by ignoring jekyll-json's destination file location in my config for jekyll-serve's autogneration...
+ [2017-06-05T05:14:10Z] lswart I added a fix here: https://github.com/openseattle/openseattle.github.io/pull/39/commits/a93229c31460c4c09db2769e3ceb774179920e86 I think it works!
+ [2017-06-05T05:14:11Z] jekyllrb Title: fix autogeneration by LukeSwart · Pull Request #39 · openseattle/openseattle.github.io · GitHub (at github.com)
+ [2017-06-05T05:24:16Z] allejo wouldn't excluding it mean it won't be moved to _site?

message no. 169413

Posted by lswart in #jekyll at 2017-06-05T04:40:35Z

allejo: Actually, it looks like the "destination" defined in jekyll-json here: https://github.com/BenRuns/jekyll-json/blob/development/lib/jekyll-json.rb#L29 is not referring to jekyll's destination folder (ie `_site`), but it's referring to a destination folder that is specified in the _config.yml here: https://github.com/openseattle/openseattle.github.io/blob/master/_config.yml#L25
+ [2017-06-10T08:30:57Z] azarus Hey guys, I've experienced this error: http://dpaste.de/x1o3 , even though jekyll-archives is installed by bundle, and as a gem.
+ [2017-06-10T08:30:59Z] jekyllrb Title: dpaste.de: Snippet #421940 (at dpaste.de)
+ [2017-06-10T08:31:25Z] azarus I've tried to build using `bundle exec jekyll build`
+ [2017-06-11T03:23:37Z] zmoazeni There's likely a cleaner way to do this, but https://gist.github.com/zmoazeni/4241c4908cb3f9ced40482e100560b6c works for me
+ [2017-06-11T03:23:38Z] jekyllrb Title: duplicate_posts_in_other_versions.rb · GitHub (at gist.github.com)