Redmine

(For reference: you have posted additional detail in an issue at #42978)

Redmine 6 uses Propshaft (a dynamic assets pipeline) which compiles all styles, javascript files, plugin assets, and themes and puts the compiled files into the public/assets directory. See the announcement of Redmine 6.0.0 at: Redmine 6.0.0 is now available

Please make sure to put your custom theme into the themes directory of your Redmine installation rather than public/themes where it was in previous versions. Very likely, you won.t need the Alias and custom Location in your Apache config.

If a theme uses imports in its css of Javascript files, the theme likely needs to be adapted for Propshaft as here, the final URLs (resp. the generated asset files) always contain a short hash of its contents. You thus need to use dynamic imports with fully qualified URLs. You can check the sources of the default themes which you can find in app/assets/themes for examples.

Unfortunately, it likely that some of the wiki pages on redmine.org regarding themes are outdated and/or misleading. Specifically the HowTo_create_a_custom_Redmine_theme page appears to be outdated as it does not use the required syntax for dynamic includes yet and the Themes page appears to propose a possibly invalid configuration which appears to target "hybrid" URL paths with outdated assets. Updating these guides is still not finished yet (see #40221).

For a "works out of the box" config in your Apache, you I think just need to serve the contents of the public directory without any custom configuration and forward requests to any non-existing files to your Redmine app server (such as Passenger, Puma, ...) For the default Propshaft pipeline to work, the user which runs your Redmine service must have write access to the public directory. Make sure to restart your app server process after any changes to config, code, or assets.

Holger Just wrote in RE: Redmine 6 additional installed themes don't work:

(For reference: you have posted additional detail in an issue at #42978)

Yes, indeed, I asked for that issue to be deleted.

Redmine 6 uses Propshaft (a dynamic assets pipeline) which compiles all styles, javascript files, plugin assets, and themes and puts the compiled files into the public/assets directory. See the announcement of Redmine 6.0.0 at: Redmine 6.0.0 is now available

Yes, noted.

Please make sure to put your custom theme into the themes directory of your Redmine installation rather than public/themes where it was in previous versions. Very likely, you won.t need the Alias and custom Location in your Apache config.

I did indeed put it there. In similar fashion RedmineUp's A1 theme was installed there as well. It shows up in the dropdown select box, which indicated the code in the correct location.

If a theme uses imports in its css of Javascript files, the theme likely needs to be adapted for Propshaft as here, the final URLs (resp. the generated asset files) always contain a short hash of its contents. You thus need to use dynamic imports with fully qualified URLs. You can check the sources of the default themes which you can find in app/assets/themes for examples.

I'll take this up with RedmineUp as well, since the A1 theme is specifically the Redmine 6 version.

Unfortunately, it likely that some of the wiki pages on redmine.org regarding themes are outdated and/or misleading. Specifically the HowTo_create_a_custom_Redmine_theme page appears to be outdated as it does not use the required syntax for dynamic includes yet and the Themes page appears to propose a possibly invalid configuration which appears to target "hybrid" URL paths with outdated assets. Updating these guides is still not finished yet (see #40221).

Note, thanks for the update/

For a "works out of the box" config in your Apache, you I think just need to serve the contents of the public directory without any custom configuration and forward requests to any non-existing files to your Redmine app server (such as Passenger, Puma, ...) For the default Propshaft pipeline to work, the user which runs your Redmine service must have write access to the public directory. Make sure to restart your app server process after any changes to config, code, or assets.

This is how I currently have it.

<VirtualHost *:443>

    ServerName xxx.yy.zz
    ServerAdmin xxx@xxx.yy.zz
    DocumentRoot /var/www/redmine/public
    ErrorLog /var/log/redmine/error.log
    CustomLog /var/log/redmine/access.log combined
    LogLevel warn

Either the A1 theme is faulty, and so also my own custom theme, or there's something else still wrong.

I just completed a new installation of Redmine 6.0.5 and get the exact same result. I didn't install any plugins or other themes, but took the stock standard installed, installed the sample data and then added the theme to the redminehome/themes folder.

Here are my config files:

note: I used this site to configure my system

/etc/apache2/sites-enabled/xxx.yy.zz-le-ssl.conf:

<IfModule mod_ssl.c>
<VirtualHost *:443>

    ServerName xxx.yy.zz
    ServerAdmin redmine@abc.co.za
    DocumentRoot /var/www/redmine/public
    ErrorLog /var/log/redmine/error.log
    CustomLog /var/log/redmine/access.log combined
    LogLevel warn

RewriteEngine on
SSLCertificateFile /etc/letsencrypt/live/xxx.yy.zz/fullchain.pem
SSLCertificateKeyFile /etc/letsencrypt/live/xxx.yy.zz/privkey.pem
Include /etc/letsencrypt/options-ssl-apache.conf
</VirtualHost>
</IfModule>

/etc/apache2/conf-enabled/redmine.conf

LoadModule passenger_module /var/lib/gems/3.2.0/gems/passenger-6.0.27/buildout/apache2/mod_passenger.so
<IfModule mod_passenger.c>
  PassengerRoot /var/lib/gems/3.2.0/gems/passenger-6.0.27
  PassengerDefaultRuby /usr/bin/ruby3.2
</IfModule>

<Directory "/var/www/redmine/public">
  Allow from all
  Options -MultiViews
  Require all granted
</Directory>

Redmine seems to be running fine, except the themes are not loading correctly.

One last comment: I also tried installing a completely different theme farend_bleuclair, but the result is the same.

I ran bundle exec rake assets:precompile RAILS_ENV="production" and restarted Apache. That made the theme load correctly. Could that be the simple step I missed?

Roland Giesler wrote in RE: Redmine 6 additional installed themes don't work:

I ran bundle exec rake assets:precompile RAILS_ENV="production" and restarted Apache. That made the theme load correctly. Could that be the simple step I missed?

thanks for that.
Just to chip in with my observation - themes are broken for me as shown above - with Redmine in a container I put new theme into: /usr/src/redmine/themes I'd fix permission, restart container but only/unless if I do:
-> $ podman container exec --user root redmine.hub.mine.priv bash -c 'exec rake assets:precompile RAILS_ENV="production"'
I can see that path /usr/src/redmine/public/assets/themes got new stuff-theme dir, then container restart is neeed, only ! then such a new theme is not broken.
I don't know if this is by design - but can tell that many non-experts/programmers - like myself - will be defeated by this.