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

Liquid error: bad component(expected relative path component) #713

Closed
jlafollette opened this issue Jun 6, 2013 · 6 comments
Closed

Liquid error: bad component(expected relative path component) #713

jlafollette opened this issue Jun 6, 2013 · 6 comments
Assignees

Comments

@jlafollette
Copy link

After upgrading from a 2.0.x version of the engine to 2.1.0 I get the following Liquid error displayed on our locomotive-enabled site:

Liquid error: bad component(expected relative path component): https://com.citrrus.locomotive.s3.amazonaws.com/sites/51970154b5dd470002000004/theme/stylesheets/bootstrap2.css

This occurs when I use the following tag in a snippet:
{{ 'bootstrap2.css' | stylesheet_tag }}

I've tried deleting and recreating the asset, the snippet that references it, and the page that includes the snippet. Unfortunately none of these steps have any affect.

Hopefully this is user error and not a true bug...

@jlafollette
Copy link
Author

I just did a fresh install of a brand new site and created my .css assets, snippets, and pages from scratch.

I'm getting the Liquid error here too so the whole upgrade portion of my above issue report is extraneous.

I'm deployed on Heroku (just incase that variable is important)

Perhaps this is just a bug for 2.1.0?

@relu
Copy link

relu commented Jun 7, 2013

I'm experiencing the same issue.

@did
Copy link
Member

did commented Jun 7, 2013

hey guys, we are working on it right now. Hope to get a patch pretty soon. Stay tuned.

@ghost ghost assigned did Jun 7, 2013
did added a commit that referenced this issue Jun 7, 2013
@did did closed this as completed Jun 7, 2013
@relu
Copy link

relu commented Jun 7, 2013

Thank you @did! It works fine now :)

@jlafollette
Copy link
Author

Yes! Working perfectly for me too.

Thank you @did for the fix.

@nonfungibletunji
Copy link

thx again, works on heroku great, thx

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

No branches or pull requests

4 participants