Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Possible Slim related blog error #1524

Closed
JacksonOfTrades opened this issue May 15, 2015 · 5 comments
Closed

Possible Slim related blog error #1524

JacksonOfTrades opened this issue May 15, 2015 · 5 comments

Comments

@JacksonOfTrades
Copy link

Hello, I recently converted from using simple ERB to style my middleman sites and I now use Slim instead. It was working good for a while, but now I cannot build a certain blog. While when I middleman build I get no error, when I run middleman server I eventually get the error Slim::Engine: Option :Lang is invalid

As I have designed my blog strangely, I manually define each page to have its own layout, even though it is exactly the same one.

In my Config.rb file, I have require 'slim as the only slim related thing there.

Please help, you're my only hope!

@tdreyno
Copy link
Member

tdreyno commented May 17, 2015

Can you describe the actual error? The slim warning is just a warning and shouldn't be influencing anything. Are blog articles missing? Is there a Ruby stack trace?

@JacksonOfTrades
Copy link
Author

In between writing the original post and now, I managed to fix the error. By adding :git => 'https://github.com/slim-template/slim' to the gemfile after require 'slim', adding
set :slim, :layout_engine => :slim
Slim::Engine.set_options :pretty => true to config.rb and changing the default file extension to .slim I managed to fix it.

However, now I'm getting a completely different error. My posts do not build correctly, and don't give any error, instead give off only code See example. If I change the file extension of a post to .html.md then again I get a build error again. In the build directory, what I see are the files, but without an extension (I.E 2015-05-15-grape-surgery instead of 2015-05-15-grape-surgery.html) leading them to be unable to be read,

In the original case, the only error message thrown was an error next to the file when using middleman build.

@tdreyno
Copy link
Member

tdreyno commented May 18, 2015

I'm going to need a copy of your app to diagnose

@JacksonOfTrades
Copy link
Author

Here you go, a good old testing copy. Good luck!

@JacksonOfTrades
Copy link
Author

Sorry, it seems like I linked nothing with my comment. I fixed it.

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

No branches or pull requests

3 participants