[i18n_subsites] STATIC_PATHS copied multiple times

[Scheirle]

All files and folders in the STATIC_PATHS variable are copied in each subsite.

This is a huge problem if you have large files in it.

It would be better to just copy it once, but therefore correct the links in the subsites.

[smartass101]

Hi, thank you for pointing this out.
There is a way to fix this, but the thing is that some people may put the output in a different OUTPUT_PATH for each lang.
Maybe I should add some setting for this functionality? like I18N_COPY_STATIC=False by default

[smartass101]

Actually a simple fix is to set STATIC_PATHS to [] in the I18N_SUBSITES overrides dict for each language that you don't want to copy them. If this fixes your problem, you can close the issue :)

[Scheirle]

The problem with overwriting STATIC_PATHS in I18N_SUBSITES is that it isn't possible anymore to create an internal link to the content in STATIC_PATHS.

Btw the static folder of the theme(s) should also be considered.

[smartass101]

I think this would require something like the move_translations_links function for all elements of the staticfiles list in the context. Therefore, I think we should first try to redesign that function as per #182 and then use it for static files.

[smartass101]

I was looking into this and I don't see a solution. All the intrasite links are made relative to the current SITEURL as is THEME_STATIC_DIR in templates. Moreover, if we enable the user to specify an arbitrary SITEURL and OUTPUT_PATH as requested in #180, I simply don't see a reliable way to "link back" to the top site that would work for everyone. In a particular case it could be solved by overriding STATIC_PATHS and THEME_STATIC_DIR and then adding some special filters in templates.

[Scheirle]

@smartass101 I have code which should solve this problem. It still uses the old design (runnig pelican multiple times), but maybe it will help.

I didn't posted this earlier because I am not pleased with it.

Changes in Scheirle@0f574ad:

• Change the SITEURL for every pelican run (appanding the language)
• Move the output and url for all static files
  • The exclude of EXTRA PATH METADATA only is a proof of concept
  • Note the use of the update_generator_contents_static signal

[smartass101]

Doing something like that would be possible of course, but as I said before, it won't work with arbitrary SITEURL and OUTPUT_PATH settings.