search

octopress / asset-pipeline

Adds your local CSS, Sass, Javascript and Coffeescript files to Octopress Ink's asset pipeline.
MIT License
4 stars 3 forks source link

asset-pipeline breaks jekyll-monthly-archive-plugin #4

Closed rbeeger closed 9 years ago

rbeeger commented 10 years ago

I use https://github.com/shigeya/jekyll-monthly-archive-plugin to create monthly archives of my posts. With asset-pipeline 1.0.3 this plugin doesn't work anymore. It still generates the files for the monthly archives, but they don't contain the links to the posts of the month.

I can make it work again by removing 

gems:
  - octopress-asset-pipeline

from my _config.yml.

Data that is set in the plugin seems to become unavailable as soon as the asset-pipeline is active.

I was able to reproduce the problem on a minimal site generated by "octopress new". I cannot tell whether this is a problem of Octopress or if the plugin does something it shouldn't which would make it break in other circumstances. But as it might hint at some bigger problem in Octopress, looking at this is probably a good idea.

imathis commented 10 years ago

I've looked through their code and I don't see what they could be doing wrong. I'll see what I can figure out. What's an easy way for me to replicate this? Do you mind throwing up a minimal test site for me to play with?

imathis commented 10 years ago

I've uploaded a test site and as far as I can tell, there's no negative interaction between the two plugins. If you clone this you should be able to bundle install and run jekyll build and see monthly archives being generated. It works fine for me.

If you're able to get it to break, please submit a pull request to that test repo with what I need to make it fail.

rbeeger commented 10 years ago

It's been late yesterday. So I didn't realize what specific feature provokes the failure. I've sent a pull request to your test site. It's replacing the CSS with a SCSS. Sorry, if you spent much time trying to find the problem.

rbeeger commented 10 years ago

This is fixed in version 1.0.4