Jump to content
Froxlor Forum

Release 0.10.27 - Debian Bullseye support, added ZeroSSL alternative to Let's Encrypt and custom logo upload


d00p
 Share

Recommended Posts

Dear Froxlor Community,

in this release, we start to support the new Debian Bullseye (11) distribution (including packages via deb.froxlor.org). We have also added the ZeroSSL endpoint as an alternative to Let's Encrypt, you can read more about ZeroSSL here: https://zerossl.com/letsencrypt-alternative/. It is now also possible to customize the login and header logo from within the panel-settings. For users that are currently using the custom_logo.png file to override it - the updater will convert it for you.

Changes in 0.10.27:

  • added a default robots.txt to avoid indexing by search-engines
  • add setting for default serveralias value for new domains
  • prefer custom zone entries over automatically created ones when system.dns_createmailentry is enabled; fixes #944
  • support ZeroSSL via acme.sh (v3); fixes #946
  • allow defining php_value/php_admin_value for session.save_path when using php-fpm; fixes #954
  • possibility to upload custom header/login logo, refs #948
  • possibility to specify custom css; refs #949
  • bump phpmailer/phpmailer from 6.4.1 to 6.5.0
  • support for Debian Jessie has been dropped

 

Download: 0.10.27 | website


Visit http://www.froxlor.org or join our IRC channel #froxlor on irc.libera.chat for support, help, participation or just a chat

Thank you,
d00p

Link to comment
Share on other sites

Congratulations!

Just out of curiosity, I'm gladly surprise that Bullseye support has been added already. Does that mean that changes between Buster and Bullseye are not that big?

Thank you @d00p!

Link to comment
Share on other sites

35 minutes ago, llucps said:

Does that mean that changes between Buster and Bullseye are not that big?

Yes, not that much. Hopefully I didn't miss anything ;)

Link to comment
Share on other sites

Thanks for the possibility with custom.css but the new custom logo solution is a step backwards. Why? It is no longer possible to include different logos in different themes and a database query is needed which means broken database access = wrong logo 😞

Link to comment
Share on other sites

12 minutes ago, Shortie said:

It is no longer possible to include different logos in different themes and a database query is needed which means broken database access = wrong logo 😞

You're right on the first part, yes, haven't thought about that. The contributors idea was to have this custom_logo possiblity more present to the admin. Maybe we can find a solution to satisfy both these needs.

For database query: settings are read either way, but yes, also correct, dB broken, no logo. If you like open up an issue on GitHub for this.

Link to comment
Share on other sites

First thoughts: Use if file_exist in the template directory logo_custom.png and logo_custom_login.png. If nothing found use database. If nothing found in database use logo.png. So you have only include a few lines 😉

 

  • Like 1
Link to comment
Share on other sites

  • d00p unpinned this topic

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...