-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to load style.css file #1283
Comments
Well, I initially forgot that variable but I have just tried and it didn't help much. My browser is trying to download the style.css file using the url First I added this line to
because I thought that sympa would automatically add the VIRTUAL_DOMAIN part, but it didn't work. Then I changed the
but it didn't work either. The only solution I could find, without reading the configuration instructions (sorry for this, guys), was adding the soft link that I mentioned in my first post. Maybe there is another solution related to adding some any other variables to |
Could you please show the configuration for httpd? |
Hello, We have a similar problem after installing the of sympa (6.2.60 When accessing the page https://lists-test.scc.kit.edu/sympa, the page is loaded, but it does not run properly. The values in the sympa config look like this: The Apache config looks like this: I wonder if this is a configuration error? Kind regards, |
Hi, @ikedas. By "configuration fot httpd", do you mean the apache site created for the web interface of sympa? I used the standard configuration suggested in the documentation:
Take into account that in debian you can enable the required modules with:
Thank you very much. |
You need to define aliases for /pictures-sympa and /css-sympa in your Apache configuration. Regards |
Hello Racke,
thank you for your quick reply.
Is that described on a web page, that and how these aliases have to be set?
According to the website https://metadata.ftp-master.debian.org/changelogs/main/s/sympa/sympa_6.2.60~dfsg-4_changelog , since sympa (6.2.58~dfsg-4), setuid-wrappers are no longer used (as required by sympa).
But the Apache config file /etc/apache2/conf-available/sympa.conf , which comes with the Debian package for Bullseye, still contains the old configuration with wwsympa-wrapper.fcgi .
This old config contains an alias for /css-sympa and /css-picture, but this config is not up to date anymore.
And in the documentation for the setup of the http server of the vanilla Sympa <https://sympa-community.github.io/manual/install/configure-http-server-spawnfcgi.html#setup-http-server> there is no alias for /css and /picture but only an alias for /static-sympa.
Are these aliases missing in the documentation of the vanilla Sympa or is there another mechanism provided in vanilla Sympa and these aliases are only part of the Debian package config?
Kind regards,
Sabine
Von: Stefan Hornburg (Racke) ***@***.***>
Gesendet: Dienstag, 30. November 2021 18:33
An: sympa-community/sympa ***@***.***>
Cc: Lorenz, Sabine (SCC) ***@***.***>; Comment ***@***.***>
Betreff: Re: [sympa-community/sympa] Unable to load style.css file (Issue #1283)
Hello,
We have a similar problem after installing the of sympa (6.2.60dfsg-4) as a Debian package (Debian 11) with Apache 2.4.51-1deb11u1:
When accessing the page https://lists-test.scc.kit.edu/sympa, the page is loaded, but it does not run properly. According to the net log, it tries to load the following non-existent URL: https://lists-test.scc.kit.edu/css-sympa/lists-test.scc.kit.edu/style.css?h=bd2b0c909269bcae2ec25147fa216a05.
The values in the sympa config look like this: ***@***.***:/usr/share/info# grep -e static -e css -e wws -e http -e pic /etc/sympa/sympa.conf | grep -v ^# static_content_path /usr/share/sympa/static_content css_path /var/lib/sympa/css css_url /css-sympa pictures_path /var/lib/sympa/pictures pictures_url /pictures-sympa wwsympa_url https://lists-test.scc.kit.edu/sympa
The Apache config looks like this: ***@***.***:/usr/share/info# grep -v ^# /var/www/conf/sympa.conf | grep -v ^$ RewriteEngine On RewriteRule ^/$ /sympa [R=permanent,L] RedirectPermanent /wws /sympa ProxyErrorOverride On ProxyTimeout 120 <location /sympa> SetHandler "proxy:unix:/run/sympa/wwsympa.socket|fcgi://" Require all granted Alias /static-sympa /usr/share/sympa/static_content <Directory /usr/share/sympa/static_content> Require all granted Alias /logo /var/www/htdocs/logo <location /sympa/sso_login/kit_shibboleth> Include /etc/apache2/include/auth_shibboleth Require shibboleth
I wonder if this is a configuration error? Do we need to define an alias from css-sympa to /var/lib/sympa/css in Apache config? Or is this otherwise a bug in sympa or a bug in the debian package for bullseye?
Kind regards, Sabine
You need to define aliases for /pictures-sympa and /css-sympa in your Apache configuration.
Regards
Racke
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1283 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMIOBGZK5B2U2E3ZSQ2FFX3UOUDE3ANCNFSM5I5RQ5BA> .
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .
|
On 01/12/2021 08:53, Salo15 wrote:
Hello Racke,
thank you for your quick reply.
Is that described on a web page, that and how these aliases have to be set?
I think the aliases used in /etc/apache2/conf-available/sympa.conf should be still correct:
Alias /css-sympa /var/lib/sympa/css
<Directory /var/lib/sympa/css>
Require all granted
</Directory>
Alias /pictures-sympa /var/lib/sympa/pictures
<Directory /var/lib/sympa/pictures>
Require all granted
</Directory>
According to the website https://metadata.ftp-master.debian.org/changelogs/main/s/sympa/sympa_6.2.60~dfsg-4_changelog , since sympa (6.2.58~dfsg-4), setuid-wrappers are no longer used (as required by sympa).
But the Apache config file /etc/apache2/conf-available/sympa.conf , which comes with the Debian package for Bullseye, still contains the old configuration with wwsympa-wrapper.fcgi .
That's correct.
This old config contains an alias for /css-sympa and /css-picture, but this config is not up to date anymore.
And in the documentation for the setup of the http server of the vanilla Sympa <https://sympa-community.github.io/manual/install/configure-http-server-spawnfcgi.html#setup-http-server> there is no alias for /css and /picture but only an alias for /static-sympa.
Are these aliases missing in the documentation of the vanilla Sympa or is there another mechanism provided in vanilla Sympa and these aliases are only part of the Debian package config?
These aliases are only needed when the directories for CSS and pictures are not subdirectories of static_content, which applies to the Debian package but not
to vanilla Sympa with the "standard" configuration parameters.
Regards
Racke
…
Kind regards,
Sabine
Von: Stefan Hornburg (Racke) ***@***.***>
Gesendet: Dienstag, 30. November 2021 18:33
An: sympa-community/sympa ***@***.***>
Cc: Lorenz, Sabine (SCC) ***@***.***>; Comment ***@***.***>
Betreff: Re: [sympa-community/sympa] Unable to load style.css file (Issue #1283)
Hello,
We have a similar problem after installing the of sympa (6.2.60dfsg-4) as a Debian package (Debian 11) with Apache 2.4.51-1deb11u1:
When accessing the page https://lists-test.scc.kit.edu/sympa, the page is loaded, but it does not run properly. According to the net log, it tries to load the following non-existent URL: https://lists-test.scc.kit.edu/css-sympa/lists-test.scc.kit.edu/style.css?h=bd2b0c909269bcae2ec25147fa216a05.
The values in the sympa config look like this: ***@***.***:/usr/share/info# grep -e static -e css -e wws -e http -e pic /etc/sympa/sympa.conf | grep -v ^# static_content_path /usr/share/sympa/static_content css_path /var/lib/sympa/css css_url /css-sympa pictures_path /var/lib/sympa/pictures pictures_url /pictures-sympa wwsympa_url https://lists-test.scc.kit.edu/sympa
The Apache config looks like this: ***@***.***:/usr/share/info# grep -v ^# /var/www/conf/sympa.conf | grep -v ^$ RewriteEngine On RewriteRule ^/$ /sympa [R=permanent,L] RedirectPermanent /wws /sympa ProxyErrorOverride On ProxyTimeout 120 <location /sympa> SetHandler "proxy:unix:/run/sympa/wwsympa.socket|fcgi://" Require all granted Alias /static-sympa /usr/share/sympa/static_content <Directory /usr/share/sympa/static_content> Require all granted Alias /logo /var/www/htdocs/logo <location /sympa/sso_login/kit_shibboleth> Include /etc/apache2/include/auth_shibboleth Require shibboleth
I wonder if this is a configuration error? Do we need to define an alias from css-sympa to /var/lib/sympa/css in Apache config? Or is this otherwise a bug in sympa or a bug in the debian package for bullseye?
Kind regards, Sabine
You need to define aliases for /pictures-sympa and /css-sympa in your Apache configuration.
Regards
Racke
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1283 (comment)> , or unsubscribe <https://github.com/notifications/unsubscribe-auth/AMIOBGZK5B2U2E3ZSQ2FFX3UOUDE3ANCNFSM5I5RQ5BA> .
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub> .
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub <#1283 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AABDCPWI2LR7R542VZOLKJLUOXIAFANCNFSM5I5RQ5BA>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
--
Ecommerce and Linux consulting + Perl and web application programming.
Debian and Sympa administration.
|
If you want to separate path for the CSS from static_content, you you need these settings:
Whitout these settings, default locations will be used: the |
Thank you, @ikedas, for your information. I was able to make it work as expected after adding these two lines to my
and these other to my apache site configuration file:
Maybe a note could be added to the installation documentation but, meanwhile, let this issue serve as help for all those having this problem. You can close this issue whenever you want. |
Hi Racke, thanks for your answer, the suggested solution also worked for me and after adding the aliases to the apache configuration the website can now be accessed without errors. Also from my side the ticket can be closed with it. Should I open a debian bug report, because the apache configuration file /etc/apache2/conf-available/sympa.conf in the sympa debian package for bullseye is outdated and still contains an entry for wwsympa-wrapper.fcgi? Kind regards, |
Hello Sabine, there is already a Debian bug filed for that: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986395. However, I also need to add the corresponding WWSympa FCGI instance to the package (probably with multiwatch as described on https://sympa-community.github.io/manual/install/configure-http-server-systemdsocket.html). Regards, |
Version
sympa-6.2.66
debian 11
apache 2.4.51
Installation method
From source
./configure --build=x86_64-linux-gnu --prefix=/usr --includedir=${prefix}/include --mandir=${prefix}/share/man --infodir=${prefix}/share/info --sysconfdir=/etc --localstatedir=/var --disable-option-checking --disable-silent-rules --libdir=${prefix}/lib/x86_64-linux-gnu --libexecdir=${prefix}/lib/x86_64-linux-gnu --runstatedir=/run --disable-maintainer-mode --disable-dependency-tracking --enable-fhs --sysconfdir=/etc/sympa --sbindir=/usr/lib/sympa/bin --libexecdir=/usr/lib/sympa/bin --with-cgidir=/usr/lib/cgi-bin/sympa --with-staticdir=/usr/share/sympa/static_content --with-cssdir=/var/lib/sympa/css --with-picturesdir=/var/lib/sympa/pictures --datadir=/usr/share --localedir=/usr/share/locale --mandir=/usr/share/man --with-unitsdir=/usr/lib/systemd/system --without-initdir --docdir=/usr/share/doc/sympa --with-piddir=/run/sympa --with-perl=/usr/bin/perl --with-user=sympa --with-group=sympa --with-aliases_file=/etc/mail/sympa/aliases --disable-setuid-fcgi
Expected behavior
Web interface should be correctly displayed
Actual behavior
Web interface shows the content but not the desired style
Additional information
I followed the source code installation instructions detailed in the documentation https://sympa-community.github.io/manual/install/install-sympa-distribution-source.html The configuration of my testing machine is as detailed in the documentation (DB=maria-db, web server=apache, mail server=postfix, single domain sympa configuration, WWSympa FCGI)
I configured my installation using similar values to the debian package (except that I decided to get rid of the init.d scripts and used the Systemd scripts instead). After installation I noticed that the web interface could not load the style.css file; it was trying to load it from the
$STATICDIR
(/usr/share/sympa/static_content
in my case) when they were actually installed in the$CSSDIR
(/var/lib/sympa/css
in my case).I understand that this is a correct behavior given my installation configuration, so I created a soft link in
$STATICDIR
pointing to the$CSSDIR
that solved the issue:I am writing this in order to ask if this could be treated as an bug to be corrected (during installation, when
$STATICDIR
!=$CSSDIR
create soft link) and to serve for others to be aware of the problem and the solution.Thank you very much.
Regards,
The text was updated successfully, but these errors were encountered: