+ [2016-10-15T21:59:28Z] jekyllrb ¯\_(ツ)_/¯
+ [2016-10-15T22:01:02Z] allejo miklb, what clarification do you need?
+ [2016-10-15T22:01:41Z] allejo instead of doing: {{ "/about/" | prepend: site.baseurl }} you can do {{ "/about/" | relative_url }}
+ [2016-10-15T22:03:18Z] allejo and instead of doing something: {{ "/about/" | prepend: site.baseurl | prepend: site.url }} you can do {{ "/about/" | absolute_url }}
+ [2016-10-15T23:56:47Z] miklb allejo my problem is that I have a plugin that caches all links in a post, and it is changing the cache file to use localhost:4000 when I serve the site locally, I need to figure out what I need to change that to always use the actual URL. Unless I have to explicitly serve the site locally as env production. Just seems like an extreme change in behavior

message no. 153429

Posted by miklb in #jekyll at 2016-10-15T02:07:17Z

at first glance, not seeing any docs for the new relative_url/absolute_url on the main site, only in the 3.3 release, and it's a little confusing. Anyone have a pointer to some clarification?
+ [2016-10-16T00:08:04Z] allejo So when you're serving locally, you want the cache file to use the actual URL of your website instead of localhost:4000?
+ [2016-10-16T00:08:13Z] miklb yep
+ [2016-10-16T00:09:08Z] miklb everything worked fine locally before, 3.3 changed this behavior
+ [2016-10-16T04:52:41Z] allejo hmm, then i think maybe the plugin may need to be updated to handle this change in behavior? could also start an issue on jekyll's repo asking about this
+ [2016-10-16T15:44:27Z] nonasuomy_ Hi is there a way to show where liquid failed with a line number while running jekyll, I found this https://github.com/jekyll/jekyll/issues/4431 but not sure where to "set the line_numbers option to true for Template.parse"