Error specifying source in config #653

Closed
OliverJAsh opened this Issue Oct 11, 2012 · 10 comments

Comments

Projects
None yet
4 participants
@OliverJAsh

I am getting this error when my _config.yml is outside of the source folder:

Configuration from /Users/Oliver/Development/Personal/oliverash.me/_config.yml
Building site: ./source -> ./site
/Library/Ruby/Gems/1.8/gems/jekyll-0.11.2/bin/../lib/jekyll/convertible.rb:81:in `do_layout': undefined method `name' for #<Jekyll::Post:0x10d6cd668> (NoMethodError)
    from /Library/Ruby/Gems/1.8/gems/jekyll-0.11.2/bin/../lib/jekyll/post.rb:189:in `render'
    from /Library/Ruby/Gems/1.8/gems/jekyll-0.11.2/bin/../lib/jekyll/site.rb:193:in `render'
    from /Library/Ruby/Gems/1.8/gems/jekyll-0.11.2/bin/../lib/jekyll/site.rb:192:in `each'
    from /Library/Ruby/Gems/1.8/gems/jekyll-0.11.2/bin/../lib/jekyll/site.rb:192:in `render'
    from /Library/Ruby/Gems/1.8/gems/jekyll-0.11.2/bin/../lib/jekyll/site.rb:40:in `process'
    from /Library/Ruby/Gems/1.8/gems/jekyll-0.11.2/bin/jekyll:250
    from /usr/bin/jekyll:23:in `load'
    from /usr/bin/jekyll:23

My _config.yml:

source: ./source
destination: ./site

server: true
markdown: rdiscount
future: false

If I remove the source, place _config.yml inside of the source, and then run jekyll from inside there, it works fine.

@mattr-

This comment has been minimized.

Show comment Hide comment
@mattr-

mattr- Oct 12, 2012

Member

With current master, I don't see this error. I created a directory named sandbox and put a source directory and a site directory inside of the sandbox directory. _config.yml is in the sandbox directory. I copied your _config.yml verbatim. I stuck a post in sandbox/source/_posts. I then ran jekyll from inside the sandbox directory:

Configuration from /home/matt/Code/jekyll/sandbox/_config.yml
Building site: ./source -> ./site
Successfully generated site: ./source -> ./site
[2012-10-11 21:54:48] INFO  WEBrick 1.3.1
[2012-10-11 21:54:48] INFO  ruby 1.9.3 (2012-04-20) [x86_64-linux]
[2012-10-11 21:54:48] WARN  TCPServer Error: Address already in use - bind(2)
[2012-10-11 21:54:48] INFO  WEBrick::HTTPServer#start: pid=2011 port=4000

Any other hints or ideas that would help troubleshoot this?

Member

mattr- commented Oct 12, 2012

With current master, I don't see this error. I created a directory named sandbox and put a source directory and a site directory inside of the sandbox directory. _config.yml is in the sandbox directory. I copied your _config.yml verbatim. I stuck a post in sandbox/source/_posts. I then ran jekyll from inside the sandbox directory:

Configuration from /home/matt/Code/jekyll/sandbox/_config.yml
Building site: ./source -> ./site
Successfully generated site: ./source -> ./site
[2012-10-11 21:54:48] INFO  WEBrick 1.3.1
[2012-10-11 21:54:48] INFO  ruby 1.9.3 (2012-04-20) [x86_64-linux]
[2012-10-11 21:54:48] WARN  TCPServer Error: Address already in use - bind(2)
[2012-10-11 21:54:48] INFO  WEBrick::HTTPServer#start: pid=2011 port=4000

Any other hints or ideas that would help troubleshoot this?

@OliverJAsh

This comment has been minimized.

Show comment Hide comment
@OliverJAsh

OliverJAsh Oct 12, 2012

Here’s my setup: https://github.com/OliverJAsh/oliverash.me

If I move _config.yml outside of source:

mv source/_config.yml _config.yml

Then run jekyll ./source ./site from the root directory:

jekyll ./source ./site 

That’s when I got the error.

Here’s my setup: https://github.com/OliverJAsh/oliverash.me

If I move _config.yml outside of source:

mv source/_config.yml _config.yml

Then run jekyll ./source ./site from the root directory:

jekyll ./source ./site 

That’s when I got the error.

@mattr-

This comment has been minimized.

Show comment Hide comment
@mattr-

mattr- Oct 12, 2012

Member

If you specify

plugins: ./source/_plugins

in your configuration file, you'll be able to work around this issue for now.

I have a patch for this that I'll add as a pull request (since I don't have commit access to the main repository) in a few hours.

Member

mattr- commented Oct 12, 2012

If you specify

plugins: ./source/_plugins

in your configuration file, you'll be able to work around this issue for now.

I have a patch for this that I'll add as a pull request (since I don't have commit access to the main repository) in a few hours.

@OliverJAsh

This comment has been minimized.

Show comment Hide comment
@OliverJAsh

OliverJAsh Oct 12, 2012

Thank you very much!

Oliver

On 12 Oct 2012, at 23:13, Matt Rogers notifications@github.com wrote:

If you specify

plugins: ./source/_plugins
in your configuration file, you'll be able to work around this issue for now.

I have a patch for this that I'll add as a pull request (since I don't have commit access to the main repository) in a few hours.


Reply to this email directly or view it on GitHub.

Thank you very much!

Oliver

On 12 Oct 2012, at 23:13, Matt Rogers notifications@github.com wrote:

If you specify

plugins: ./source/_plugins
in your configuration file, you'll be able to work around this issue for now.

I have a patch for this that I'll add as a pull request (since I don't have commit access to the main repository) in a few hours.


Reply to this email directly or view it on GitHub.

@parkr

This comment has been minimized.

Show comment Hide comment
@parkr

parkr Dec 8, 2012

Member

Can we close this? :)

Member

parkr commented Dec 8, 2012

Can we close this? :)

@mattr-

This comment has been minimized.

Show comment Hide comment
@mattr-

mattr- Dec 8, 2012

Member

The pull isn't merged yet, so no.

Member

mattr- commented Dec 8, 2012

The pull isn't merged yet, so no.

@parkr

This comment has been minimized.

Show comment Hide comment
@parkr

parkr Dec 8, 2012

Member

The pull in 654 is separate, no? i.e. if it stays open, then we won't forget, right? So closing 653 is fine because 654 will be open?

Member

parkr commented Dec 8, 2012

The pull in 654 is separate, no? i.e. if it stays open, then we won't forget, right? So closing 653 is fine because 654 will be open?

@mattr-

This comment has been minimized.

Show comment Hide comment
@mattr-

mattr- Dec 8, 2012

Member

I'd like to keep them together for now. Ideally, I would have just converted this issue into a pull request, but, ironically, you have to have push access to the main repo in order to do that.

Member

mattr- commented Dec 8, 2012

I'd like to keep them together for now. Ideally, I would have just converted this issue into a pull request, but, ironically, you have to have push access to the main repo in order to do that.

@parkr

This comment has been minimized.

Show comment Hide comment
@parkr

parkr Dec 8, 2012

Member

Oh, the irony! Here's hoping @mojombo hears the prayers of his minions.

Member

parkr commented Dec 8, 2012

Oh, the irony! Here's hoping @mojombo hears the prayers of his minions.

@parkr

This comment has been minimized.

Show comment Hide comment
@parkr

parkr Jan 30, 2013

Member

Going to accept your PR soon - just closing this for housekeeping.

Member

parkr commented Jan 30, 2013

Going to accept your PR soon - just closing this for housekeeping.

@parkr parkr closed this Jan 30, 2013

parkr added a commit that referenced this issue Feb 26, 2013

Merge pull request #654 from mattr-/issue-653
Look for plugins under the source directory. Fixes #653.

@jekyllbot jekyllbot locked and limited conversation to collaborators Feb 27, 2017

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.