Discuss Joomla! 4.2.9

[pe7er]

Here you can discuss about the release of Joomla 4.2.9

See Announcement: viewtopic.php?f=8&t=1000436

[gws]

FYI the link to full list of bugs fixed doesn't resolve,just a revolver image.

[darb]

Ok tried to do a Joomla 4.2.9 automatic update but get error message: File Checksum Failed

Manual update worked...

[jgress-]

Ok tried to do a Joomla 4.2.9 automatic update but get error message: File Checksum Failed

Manual update worked...

I haven't seen that on any of the updates I've done so far. When you say "automatic update" do you mean via the button in the Joomla Update component? #Strange

[pe7er]

FYI the link to full list of bugs fixed doesn't resolve,just a revolver image.

Thanks but I cannot reproduce that issue. Could you test it with another browser?
Or maybe it was temporary?

Screenshot from 2023-03-14 18-34-18.png

[gws]

Tried with chrome and OK tried again with FF and same problem,then I discovered javascript was blocked for that page,enabled and fine.So my bad. Thanks Pe7er.

[pe7er]

Tried with chrome and OK tried again with FF and same problem,then I discovered javascript was blocked for that page,enabled and fine.So my bad. Thanks Pe7er.

No problem!
I once thought Joomla had a problem with article "save", until I discovered I had disabled JavaScript while testing something on the front-end

[sozzled]

Very interesting to see if the number of "double GZIP" errors will go away after people use J! 4.2.9 in future. :

[Rondeb]

Updated 15 sites and everything went perfect!

Thanks Joomla-Team

[TomT]

There shows a message in 4.2.9:
".htaccess Update Concerning Setting the Content-Encoding Header.

Before 4.2.9 the default htaccess.txt file contained erroneous code for appending the "Content-Encoding" HTTP header. This could result in double encoding errors when Joomla is installed in a subdirectory and both this directory and its parent directory contain an .htaccess file with this code. You should manually apply the necessary changes to any existing .htaccess file, as this file can not be updated automatically.
The old code:
Header append Content-Encoding gzip
The new code:
Header set Content-Encoding gzip"

What am I supposed to do? I have no idea what is meant.

[pe7er]

What am I supposed to do? I have no idea what is meant.

Something has been changed in the htaccess.txt (Joomla's default htaccess file), see https://github.com/joomla/joomla-cms/pull/39205

Joomla cannot change your .htaccess (Apache server settings override). If you have any issues with "Content-Encoding" HTTP header" then you have to change something yourself in your .htaccess file.

[formfranska]

There shows a message in 4.2.9:
".htaccess Update Concerning Setting the Content-Encoding Header.

Before 4.2.9 the default htaccess.txt file contained erroneous code for appending the "Content-Encoding" HTTP header. This could result in double encoding errors when Joomla is installed in a subdirectory and both this directory and its parent directory contain an .htaccess file with this code. You should manually apply the necessary changes to any existing .htaccess file, as this file can not be updated automatically.
The old code:
Header append Content-Encoding gzip
The new code:
Header set Content-Encoding gzip"

What am I supposed to do? I have no idea what is meant.

Just change that line manually in you .htaccess (delete the old line and replace with the new line and save).

[formfranska]

Updated multiple sites with no issues.
PHP 8.1.16
YOOtheme 3.0.25

Thank you J Team

[TomT]

Just change that line manually in you .htaccess (delete the old line and replace with the new line and save).

My .htaccess file was an oldie. I'll upload the one that comes with 4.2.9

Thanks, Tom

[JasnaSontag]

I updates 2 sites and everything works fine.
1) PHP 8.1.16, MySQLi 5.7.41
2) PHP 8.0.28, MySQLi 10.3.38-MariaDB-log-cll-lve
Both are made with Shaper_helixultimate template

[tessera963]

Dealing with the Post Installation Message about correcting the htaccess.txt file, I checked my htaccess.txt file and I don't have "Header append Content-Encoding gzip" in that file. What do I need to do?

Jeff Mertes
Moorhead, MN USA

[pe7er]

I checked my htaccess.txt file and I don't have "Header append Content-Encoding gzip" in that file. What do I need to do?

If you don't have any problems: nothing.

However, if you always used Joomla's htaccess.txt as .htaccess and you haven't made any changes,
you could also replace the .htaccess with Joomla's new htaccess.txt.
Note: backup the old .htaccess before doing so, e.g. by giving it another name.
In case of issues you can revert back easily.

[gilplane]

Around 10 updates from 4.2.8 to 4.2.9.
All is ok.
Templates Gantry, Widgetkit, JCE etc...
Thanks to all the volonters.

[JasnaSontag]

In accessibility menu he last one - speech to text - doesn't work any more, but I didn't check it for a long time. It was working before few months.

[sozzled]

I am unaware of any speech-to-text feature built into any version of J!

Some third-party [J!] extension, maybe? Operating system feature? Browser extension?

I don’t think your problem is directly related to J! 4.2.9 … I think it’s a coincidence.

[AMurray]

@sozzled - Joomla's accessibility features has a speech to text function (apparently) via a Hot-key Ctrl+Alt+S.
https://magazine.joomla.org/all-issues/ ... joomla-4-1 mentions it, but I can't seem to activate it with the hot key combo e.g. in a new article.

[sozzled]

There’s a text-to-speech feature in J! 4.x that I’m aware if, yes; not speech-to-text. Speech-to-text Is quite different, requiring a few hours to train the application to learn someone’s voice.

Screen readers, providing text-to speech output (with limited voice-activated control, perhaps), have been around the past thirty years at least. I repeat, I am unaware of any voice-controlled text input feature built into any version of J!

My iPad and iPhone have speech-to-text input; my desktop PCs do not have speech-to-text. My laptop has limited voice-activated input (e.g. “Hey, Cortana”) but not the ability to dictate content to be converted to text.