-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Problems with {{ ASSET_PATH }} in Jekyll 3.1.1 #295
Comments
I may have found the problem. In Making this change seems to solve my problem. Is this expected? |
@ploeh In Jekyll, yes. See: http://jekyllrb.com/docs/upgrading/2-to-3/#layout-metadata |
It seems the same issue as #290 . |
Perhaps. It fixes issues with posts, but not with other pages. Right now I'm resorting to the hack setting |
@ploeh I'm guessing the issue with the other pages might be that they're no longer generated with extensions. So "/archive.html" is now "/archive/", "/tags.html" is now "/tags/", etc .... I had to make that tweak on my default.html header navigation links under I'll make sure there's not already one, then issue a PR later this week. |
Add to the list the following edit in
|
like it was before. According to the discussion at plusjade/jekyll-bootstrap#295 (comment) the changes I've previously made to archive_path, etc. might be enough. I can't say that I understand this, but we'll see. It looks OK on my machine, but it also did that before, and still looked horrible in GitHub pages.
No, that doesn't help. Or rather, it looks fine on my machine, but when hosted by GitHub Pages, all styling is gone. |
Hmmm. Could be the permalink?
(Note the trailing Guessing based on: 1) I made that edit in my If you don't mind, give that a go and let me know. |
Never mind. The symptom for that would be a 404 error. Still probably needs to be tweaked, though. |
Thank you, but it's not that either... |
Ok... so jekyll upgrade broke my website too (http://www.ajaygautam.com) changing Thanks Ajay |
just saw ploeh's post above. Updated ASSET_PATH in _config.yml - that fixed the issue, but its a very icky solution/workaround. If anyone knows of a better solution, please post here. Thanks |
* Broke for me * Discussion of fix on GitHub [1] [1] plusjade/jekyll-bootstrap#295
Using both #295 (comment) and changing the |
I also have this problem and have updated to Jekyll 3 but am wondering how to update jekyll-bootstrap? I have a blog running on 0.2.13 but would like to update it and can't find anything in the docs. |
I simply* pulled down the changes from the the Jekyll Bootstrap remote and merged them. I don't know how your blog is set up, but mine is configured like this:
*Actually, it wasn't that simple, because I had to deal with a handful of merge conflicts, but I managed... |
CSSが読み込まれない理由としては、 {{ page.theme.name }} が空になってしまうようで、linkタグが <link href="/assets/themes//bootstrap/css/bootstrap.min.css" rel="stylesheet"> このように生成されてしまいます。 以下を参考にして、_include/JB/setup の {{ page.theme.name }} を {{ layout.theme.name }} に変えたらCSSを読み込みました。 [Default ASSET_PATH fails for latest jekyll version #290](plusjade/jekyll-bootstrap#290) [Problems with {{ ASSET_PATH }} in Jekyll 3.1.1 #295](plusjade/jekyll-bootstrap#295) Error Message: [2016-06-04 01:47:15] ERROR `/assets/themes/bootstrap/css/bootstrap.min.css' not found. [2016-06-04 01:47:15] ERROR `/assets/themes/css/style.css' not found.
Github Pages upgraded to Jekyll 3 - which includes major breaking changes - and did not tell anyone about it.... See: - plusjade/jekyll-bootstrap#295 - http://jekyllrb.com/docs/upgrading/2-to-3/#layout-metadata
Please accept my apologies in advance if this issue is inappropriate, or if it's a duplicate.
Since GitHub Pages updated to run on Jekyll 3.0 February 1, 2016,
{{ ASSET_PATH }}
no longer includes the theme on my site.As an example, this:
generates this:
(notice the double slashes between
themes
andbootstrap
) while I would have expected it to generate this:which Jekyll 2 did.
I'm neither a Jekyll expert nor a Ruby programmer, but AFAICT,
ASSET_PATH
is built inJB/Setup
. Here, it uses{{ page.theme.name }}
, but as far as I can tell, this expression evaluates to nothing (or the empty string).My
_layout
files essentially look like the following, so I can't figure out what I'm doing wrong:default.hml
page.html
post.html
My entire site's source code is publicly available, if that's any help.
What am I doing wrong, and what can I do to correct the problem?
The text was updated successfully, but these errors were encountered: