-
Notifications
You must be signed in to change notification settings - Fork 38
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
Error with img Tag #4
Comments
Do you have the |
yes that file exists. |
I can confirm the site builds perfectly on my FTP server. So this is just a Github Pages issue. We can close this since I have a work-around for now. |
I'm having the same issue when trying to use Github Pages. Is there any incompatible plugin? Or is it a configuration issue that can be worked around so as to use github.io ? |
I actually use github page as well for delightfuldev.com. can you show me the markdown post that causing this error so I can try it? |
The page build failed with the following error:
|
Ok, I think I know what happened. Did you guys add Gemfile with the following content?
and There are two problems here:
So what I propose is:
|
Thanks for the help! This seemed to work, as github does not report any errors, but I'm guessing it is not picking up the plugins, showing just the raw html. (You can see it here) |
Apparently I didn't handle if Appolo is not in root url. I'm fixing it but I'll push the update as soon as I get a decent internet connection :) |
I just tried again with the latests commits and I'm still not having any luck with this. |
Yup, that worked! Thank you very much both for the great work you've done and the help! Congrats! |
Hi, First off, thank you for the amazing work. Im still a novice developer so please excuse me,
I get the following error after building the site with github pages:
"Your site is having problems building: The tag img in _posts/2015-12-20-deep.markdown/#excerpt is not a recognized Liquid tag"
So far my research says I should Use "rake generate" and "rake deploy" to fix this problem but I think this is for Octopress sites only. Have you seen this before?
The text was updated successfully, but these errors were encountered: