You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 30, 2024. It is now read-only.
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:
I'll review the comments, try to repro the issue, then test and create PR.
Regarding the question:
do I need to modify content of every post in order for it to be migrated?
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. {{ BASE_PATH }}/images/my-image.jpg), since it works in both scenarios.
I got a same issue but solved it. The reason why BASE_PATH was not extracted is
missing of "jekyll.environment" in my environment, so just run "JEKYLL_ENV=production jekyll build"
was help for me.
It's bettter to add mention for it to _config.yml .
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: