-
Notifications
You must be signed in to change notification settings - Fork 59
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
NoMethodError thrown when running jekyll serve --incremental #89
Comments
hmm... with the incremental documents may not have a defined The error is being thrown from here. Relativize urls is being called on a document with a Any chance your jekyll project is accessible and on github? I'd be happy to clone it down and debug it further. |
Yes, sure, many thanks! |
So this is going to be embarrassing to admit... I haven't done ruby development in awhile, and I have a new computer. I've been meaning to get my ruby environment setup, so I figured I'd get my dev environment setup quickly so I could debug your project. At this point I've spent four hours trying to get If you have suggestions on good ruby development setups, I could use the advice. |
Are you seeing the |
😃 no worries, its working anyways. It happens only with |
Just had this same issue after installing polyglot.
Once I ran just |
Had exactly the same error as you, only just starting using However, removing However, when I run doctor I get this notification.
Not sure if relate d(or how to fix this! |
same issue with 4.0.0 of Jekyll |
I can reproduce it with any of my Jekyll projects. Would in For instance: def relativize_urls(doc, regex)
return if doc.output.nil?
doc.output.gsub!(regex, "href=\"#{@baseurl}/#{@active_lang}/" + '\1"')
end
def relativize_absolute_urls(doc, regex, url)
return if doc.output.nil?
doc.output.gsub!(regex, "href=\"#{url}#{@baseurl}/#{@active_lang}/" + '\1"')
end |
yeah, this is a bug with incremental builds. Incremental builds use existing cached content that isn't available on the language forks for each build, when the site is fresh. This is a bug I keep punting on. It has a workaround: Just run one -sam |
@alexanderadam with your contribution merged in I cut a minor release. would you please try out version 1.3.3 and confirm noMethodError is still thrown on |
@untra I just tested it and this error is fixed with I don't believe that this was the only thing necessary for incremental support, but it fixed at least this little error. 😉 |
I run
bundle exec jekyll serve --incremental
and get the following:The text was updated successfully, but these errors were encountered: