-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
base_url issue with images #144
Comments
Hi: |
I'll review the comments, try to repro the issue, then test and create PR. Regarding the question:
I think the answer is yes. Your first example uses absolute pathing. The modified example shows relative pathing. I think the answer is to always favor relative (e.g.
|
Agree with @marshallshen's comment. Looks like Given the age and inactivity on this issue, marking as closed for now. Feel free to reopen if you have more information or still need help. |
Hi, I got a same issue but solved it. The reason why BASE_PATH was not extracted is It's bettter to add mention for it to _config.yml . |
Thanks for the update. |
this work fine previously , when I use:
default _config.yaml
root of a http server as my website
now , I decided to use one of the sub-folder of the same website under root, and I already set:
BASE_PATH : http://www.mysite.com/~pings/myblog
but still my image links refers to :
http://www.mysite.com/images/picture.jpg
instead of
http://www.mysite.com/~pings/myblog/images/picture.jpg
I read issue (65)
#65
and I tried:
none of them worked...
but even if it could, still I think that makes the blog really hard to port -- do I need to modify content of every post in order for it to be migrated?
The text was updated successfully, but these errors were encountered: