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

Page build warning #52

Closed
misaelljr opened this issue Feb 8, 2018 · 4 comments
Closed

Page build warning #52

misaelljr opened this issue Feb 8, 2018 · 4 comments

Comments

@misaelljr
Copy link

Dear,

I uploaded the project to github pages and am getting the error:

The page build completed successfully, but returned the following warning for the master branch:

You are attempting to use a Jekyll theme, "type-on-strap", which is not supported by GitHub Pages. Please visit https://pages.github.com/themes/ for a list of supported themes. If you are using the "theme" configuration variable for something other than Jekyll theme, we recommend you rename this variable throughout your site. For more information, see https://help.github.com/articles/adding-a-jekyll-theme-to-your-github-pages-site/.

How can I solve this?

@sylhare
Copy link
Owner

sylhare commented Feb 8, 2018

Hi !

Go to your _config.yml and then comment this line:

   theme: type-on-strap # If using the theme as a jekyll theme gem

That way github won't try to download the gem. (Only a few gems are accepted on github page, this line is when the theme is used with the gem).

However this does not prevent Github to load the theme in the github page, it is more of a warning than an error

@misaelljr
Copy link
Author

Good, this solved.

Sometimes I have a problem when I update the files. The page opens as if it did not find the .css. What is the cause of this?

@sylhare
Copy link
Owner

sylhare commented Feb 8, 2018

Allo,

I think you should edit your config.yml file, make sure to follow the steps in the readme. Seems like you didn't populate the url or base url with your information (github page url). It's at the beginning.

Let me know if that fixes it. If not, you can open a new issue with some screenshot and I will look into it 😉

@sylhare sylhare closed this as completed Feb 8, 2018
@misaelljr
Copy link
Author

It worked correctly. I think it takes a while for github to process changes or update content.

Thanks
Regards

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

2 participants