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

No such file or directory @ rb_sysopen since upgrade to Jekyll 2.5.0 #51

Closed
paulrobertlloyd opened this issue Nov 7, 2014 · 2 comments · Fixed by #52
Closed

No such file or directory @ rb_sysopen since upgrade to Jekyll 2.5.0 #51

paulrobertlloyd opened this issue Nov 7, 2014 · 2 comments · Fixed by #52

Comments

@paulrobertlloyd
Copy link

Since upgrading to Jekyll 2.5.0, I’m now getting the following error on build:

Error reading file /Users/paulrobertlloyd/.rvm/gems/ruby-2.1.4/gems/jekyll-sitemap-0.6.1/lib/sitemap.xml: No such file or directory @ rb_sysopen - /Users/paulrobertlloyd/Sites/paulrobertlloyd.com/source/Users/paulrobertlloyd/.rvm/gems/ruby-2.1.4/gems/jekyll-sitemap-0.6.1/lib/sitemap.xml 

Regardless of this error, sitemap.xml still appears to be generated correctly.

(It seems the path to the Gem and the path to the source directory are getting combined somehow). I also updated the way I require gems, to use the :jekyll_plugins group, but reverting this change makes no difference. Is this a bug introduced in Jekyll 2.5, or have I done something wrong?

@parkr parkr added the bug label Nov 7, 2014
@parkr
Copy link
Member

parkr commented Nov 7, 2014

A bug introduced in 2.5.0! It's very secure, meaning we can no longer create Page's that point to files outside your site's source. It still works because we override the page's read-in content (in this case nil) with the content from the gem. We need to fix this:

site_map = Page.new(@site, File.dirname(__FILE__), "", "sitemap.xml")

@parkr parkr self-assigned this Nov 7, 2014
@paulrobertlloyd
Copy link
Author

I found a bug, yay \o/

I’ve been watching the repo with interest; more secure and faster, by all accounts too. Good stuff.

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

Successfully merging a pull request may close this issue.

3 participants