Version 2.9.0 - i18n error about htmly HOT 11 CLOSED

Was just about to delete my website due to this. Could not get it to work.

BUT THE LATEST UPDATE FIXED IT!

Thank you so much. This is great!

from htmly.

Hello,

Please make sure if the de_DE.ini is available in lang directory. Try to replace the language files with the new one (just in case corrupted), and select it again via dashboard and save it.

from htmly.

Unfortunately no change.
Are there any other ideas?

File de_DE from new HTMLy package recopied, in Dashboard first again to another language and back to de_DE, cache deleted, no change.

PHP: v8.1.2-1ubuntu2.14

ii php-intl 2:8.1+92ubuntu1 all Internationalisation module for PHP [default]
ii php8.1-intl 8.1.2-1ubuntu2.14 amd64 Internationalisation module for PHP

A 'phpenmod intl' did not bring any change.

I see in the website source code that lang="de-DE" is written there. Does it matter whether de-DE and de_DE ?
Unfortunately I am not a programmer...

from htmly.

Solution:
I disabled (a2dismod) the mpm_event and proxy_fcgi on the Apache server and then ran 'a2enmod mpm_prefork' and 'a2enmod php8.1'. Everything worked again.

However, the web server no longer has http/2 - too bad. see Apache log:

[http2:warn] [pid 3005] AH10034: The mpm module (prefork.c) is not supported by mod_http2. The mpm determines how things are processed in your server. HTTP/2 has more demands in this regard and the currently selected mpm will just not do. This is an advisory warning. Your server will continue to work, but the HTTP/2 protocol will be inactive.

from htmly.

Hello,

I have blog using http/2 using mpm_event, php-fpm and didn't find any errors (PHP 8.3).

Edit: Ubuntu 20.04.6

from htmly.

I have tested again:
My server has Ubuntu 22.4.3 Server LTS (not desktop!) with kernel 5.15 and php 8.1.2.

I reactivated the modules mpm_event, php-fpm and http/2 - and after a server restart HTMLy works again!

I think that it is not enough to just restart Apache (which I have done so far). There must be another service in the background that requires a restart after the HTMLy update.
Thanks for your support.

P.S. This is my test server. The productive server with the same configuration is now also on 2.9.0 - without any problems.
But I have rebooted to be on the safe side :)

from htmly.

That's great! You're welcome!

from htmly.

I'm having the exact same problem. But i'm on shared hosting and can not restart the webserver. Any other actions I can take to get rid of this? It would pain me to deinstall HTMLy because of this.

from htmly.

Definitely the hosting you use enabling the server side cache for PHP file (ex. OPcache) for performance reason. So sometimes we edit certain PHP files and the new changes will take effect for a while. From OPcache config file:

; When disabled, you must reset the OPcache manually or restart the
; webserver for changes to the filesystem to take effect.
; For Development / testing, keep 1
; For performance / production, keep 0
opcache.validate_timestamps=0

;opcache.revalidate_freq How often in seconds should the code
;cache expire and check if your code has changed. 0 means it
;checks your PHP code every single request IF YOU HAVE 
;opcache.validate_timestamps ENABLED. opcache.validate_timestamps
;should not be enabled by default, as long as it's disabled then any value for opcache.
;revalidate_freq will basically be ignored. You should really only ever enable
;this during development, you don't really want to enable this setting for a production application.
opcache.revalidate_freq=0

So consult your hosting on how to change this. Usually hosting allows us to change options like this, allows user.ini

from htmly.

There are also cache systems that can be restarted on the console. There may be the following cache systems on the server:
(examples for Ubuntu)

systemctl start memcached
service redis-server restart
service php8.1-fpm.service restart

help:
service --status-all

However, I am not familiar with shared servers - I have my own server.

from htmly.

Ok, ty both. I will try this. Hope I can resolve this issue.

from htmly.