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

The tag stylesheet on line 10 in blog/404.html is not a recognized Liquid tag. #55

Closed
whoyawn opened this issue Feb 22, 2017 · 5 comments

Comments

@whoyawn
Copy link

whoyawn commented Feb 22, 2017

I am trying to use the blog as a subdirectory to my normal website. I have the structure like this:

screen shot 2017-02-22 at 2 56 47

and my _config.yml is as follows:

name: Huyanh Hoang
paginate: 25
paginate_path: "/posts/page/:num/"
url: https://huyanhhoang.co
baseurl: /blog
blog_theme: light # Or use dark

Am I not setting any paths correctly? I keep getting emailed that error from Github and I'm not sure what to change. I want to be able to run my site normally then go to MYURL/blog to access the home page of Chalk, but it gives me a Github 404.

@nielsenramon
Copy link
Owner

nielsenramon commented Feb 22, 2017

@HuyAnhh Chalk does not support default jekyll hosting on GitHub Pages, it requires the project to actually be build and deployed to a branch on github. Stylesheet not being a recognised tag is about jekyll-assets gem that is missing probably?

@nistara
Copy link

nistara commented Feb 22, 2017

@nielsenramon , I got a similar error when I tried to deploy it as a page:

The tag asset_path on line 1 in _posts/2016-10-15-chalk-sample-post-with-all-elements.md is not a recognized Liquid tag.

So Chalk can be deployed as a jekyll site hosted off github (e.g. username.github.io), but not as a page (username.github.io/chalk). Did I understand correct? Thank you!

@whoyawn
Copy link
Author

whoyawn commented Feb 22, 2017

screen shot 2017-02-22 at 12 14 30

@nielsenramon All of the jekyll-assets gems have been installed, is this what you're talking about?

@nielsenramon
Copy link
Owner

@nistara You can but you need to put the source files on another branch: for example: website.
Deploy your changes to that branch and run bin/deploy then you can use a github.io page.

@HuyAnhh where did you get that error? Via mail from github?

@whoyawn
Copy link
Author

whoyawn commented Feb 22, 2017

@nielsenramon I found out what the error was. I was trying to push it manually to a gh-pages branch, but it worked once I used bin/deploy on a separate repository.

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

No branches or pull requests

3 participants