-
Notifications
You must be signed in to change notification settings - Fork 205
Option to put default language in subfolder also puts non-translated static contents (img etc.) in subfolder #187
Comments
With following settings in
I get next
So it seems to work. If you set
|
@g-konst which version are you using? With |
Latest, 1.7 |
So even if I use 1.7.0 with your config settings, it's not working: Config is:
|
@sceee check this please. |
@g-konst thanks for the video but it seems to behave differently on my side. |
Try disabling all themes or plugins, perhaps one of them overwrites some of the config options. Or to put it another way, try building your project using a different OS (maybe in docker). |
Bumping with a related fix: I also ran into this same problem, however I am using a custom source directory. With the config setting
|
I've configured my site to do exactly what you do with 1.8.0
This feature isn't broken. Since this is > 2 years old, I suggest closing the issue. |
@figgles can you share your environment details?
|
@LorenzoDelpi
|
In the past, I used the setup I also described here:
Have a default language be put to root and in a separate language folder:
Since #170 , it seems there is no way to put the default language to a subfolder but keep static assets in the root. E.g.
It seems that everything specified in
is still put in the default languages's folder:
Of course, I read in the docs that those files should be referenced using a prepend like
Unfortunately, this only works well for html/md files.
In my case, I reference font files (.woff) in sass files - after some googling, it turned out that you cannot simply use
{{ "/fonts/myfont.woff" | prepend: site.baseurl_root }}
in sass files as there are some restrictions that this can only be used in a top-level sass file.So overall, it seems very complicated for a fairly simple thing - I just want all my static assets be on the root so I have a structure like this:
and can just reference those files with a regular
<link rel="stylesheet" href="/css/bootstrap.css"/>
.Is there any possibility to still configure the plugin to produce an output like this with the 1.7 release?
The text was updated successfully, but these errors were encountered: