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

Getting a liquid exception after bundle installing octopress-linkblog #6

Open
adamstac opened this issue Nov 5, 2015 · 5 comments
Open

Comments

@adamstac
Copy link

adamstac commented Nov 5, 2015

Hey bro, I'm getting this error Liquid Exception: no implicit conversion of nil into String after adding this gem.

I added the gem, added the config details and tried to run Jekyll and get that error on the first post when Jekyll spins up.

Any thoughts on what this might be?

@imathis
Copy link
Member

imathis commented Nov 6, 2015

I'm not sure. I'll try to look into it tomorrow. Thanks for the heads up.

@adamstac
Copy link
Author

adamstac commented Nov 6, 2015

Cool. I can help by troubleshooting more on my side too if need be. Let me know, and I'll be glad to help out.

@iphoting
Copy link

iphoting commented Dec 7, 2015

Would this error be related to the switch from Jekyll v2 to v3? I got the same error once I bumped Jekyll to v3:

 Incremental build: disabled. Enable with --incremental
      Generating... 
       Deprecation: Collection#empty? should be called on the #docs array directly.
                    Called by /usr/local/rvm/gems/ruby-2.2.2@octopress3/gems/octopress-ink-1.2.1/lib/octopress-ink/plugin/bootstrap.rb:163:in `posts?'.
       Deprecation: Collection#select should be called on the #docs array directly.
                    Called by /usr/local/rvm/gems/ruby-2.2.2@octopress3/gems/octopress-ink-1.2.1/lib/octopress-ink/plugin/bootstrap.rb:171:in `linkposts?'.
       Deprecation: Collection#empty? should be called on the #docs array directly.
                    Called by /usr/local/rvm/gems/ruby-2.2.2@octopress3/gems/octopress-ink-1.2.1/lib/octopress-ink/plugin/bootstrap.rb:163:in `posts?'.
       Deprecation: Collection#select should be called on the #docs array directly.
                    Called by /usr/local/rvm/gems/ruby-2.2.2@octopress3/gems/octopress-ink-1.2.1/lib/octopress-ink/plugin/bootstrap.rb:171:in `linkposts?'.
       Deprecation: Collection#empty? should be called on the #docs array directly.
                    Called by /usr/local/rvm/gems/ruby-2.2.2@octopress3/gems/octopress-ink-1.2.1/lib/octopress-ink/plugin/bootstrap.rb:163:in `posts?'.
       Deprecation: Collection#select should be called on the #docs array directly.
                    Called by /usr/local/rvm/gems/ruby-2.2.2@octopress3/gems/octopress-ink-1.2.1/lib/octopress-ink/plugin/bootstrap.rb:171:in `linkposts?'.
       Deprecation: Collection#select should be called on the #docs array directly.
                    Called by /usr/local/rvm/gems/ruby-2.2.2@octopress3/gems/octopress-linkblog-2.0.2/lib/octopress-linkblog.rb:18:in `merge_payload'.
       Deprecation: Collection#reject should be called on the #docs array directly.
                    Called by /usr/local/rvm/gems/ruby-2.2.2@octopress3/gems/octopress-linkblog-2.0.2/lib/octopress-linkblog.rb:19:in `merge_payload'.
       Deprecation: Collection#select should be called on the #docs array directly.
                    Called by /usr/local/rvm/gems/ruby-2.2.2@octopress3/gems/octopress-linkblog-2.0.2/lib/octopress-linkblog.rb:18:in `merge_payload'.
       Deprecation: Collection#reject should be called on the #docs array directly.
                    Called by /usr/local/rvm/gems/ruby-2.2.2@octopress3/gems/octopress-linkblog-2.0.2/lib/octopress-linkblog.rb:19:in `merge_payload'.
  Liquid Exception: no implicit conversion of nil into String in _posts/2007-09-07-Going-On.markdown
jekyll 3.0.1 | Error:  no implicit conversion of nil into String

Hope this helps!

@chrisfinazzo
Copy link

Yeah, just ran into this. Tracing the output gives the following information:

screen shot 2015-12-17 at 12 10 44 pm

See also: Jekyll #4199 for the fix related to the deprecation warning.

@mattrubin
Copy link

I believe this is the issue fixed by octopress/hooks#14.

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

No branches or pull requests

5 participants