Discuss Joomla! 4.2.1

[dishon]

Updated test version of Joomla 4.1.5 to version 4.2.1. No errors. Everything seems to work. I see that smart search still does not search for tags and custom fields

[dishon]

My Joomla 4.2.1 site is also very, very slow. Almost as this forum is. On frontend and also on backend. Anyone else experiencing the same?

EDIT: Just found this: https://issues.joomla.org/tracker/joomla-cms/38662

Seems like buggy System - WebAuthn Passwordless Login plugin. Disabled it and speed is back as normal.

[abernyte]

Disable System - WebAuthn Passwordless Login plugin

https://issues.joomla.org/tracker/joomla-cms/38662

[Jaydot]

...WebAuthn Passwordless Login plugin. Disabled it...

Wow! That made a huge difference! Thanks!

[abernyte]

Wooosh!

[JasnaSontag]

Updated test version of Joomla 4.1.5 to version 4.2.1. No errors. Everything seems to work. I see that smart search still does not search for tags and custom fields

Are your plugins for that enabled?

[dishon]

Updated test version of Joomla 4.1.5 to version 4.2.1. No errors. Everything seems to work. I see that smart search still does not search for tags and custom fields

Are your plugins for that enabled?

Smart Search - Tags plugin is enabled and I was wrong as it seems that tags are searchable. But custom fields are not.

[imanickam]

Smart Searching in the Custom Fields may be implemented in Joomla! 4.3. Please review the Pull Request https://github.com/joomla/joomla-cms/pull/38650.

[gilplane]

None of this is serious.
Problematic updates follow one another more and more. Users want simplicity and efficiency.
All its added functionalities must fascinate the developers but add risks of conflicts with the extensions, templates, PHP version etc.... These functionalities should be added with official but optional extensions.
I'm starting to make sites with Wordpress (which has other defaults) but which seems simpler and more stable to me with fewer updates and bugs.
So of course, I understand that everyone here is a volunteer...
But if it continues like this, Joomla will eventually die.
A passionate user since version 1.5 who would just like a stable, efficient and carefree CMS....
Sincerely

[abernyte]

While I will not be drawn into the Joomla v Wordpress theme, it should be pointed out that since the start of 2021 to present day both Joomla and Wordpress have released 9 updates, some major some minor and in both cases some fixing bugs in the previous update.
In both platforms the updates were addressing similar vulnerabilities and external changes in php or introducing modern features.
These features are generally requested by users and developers not just something " that fascinate developers".
I wish you success using Wordpress for the future, especially modifying the core!

[mamboline]

This is a very bad bug. But, ok, this happens...

I am wondering why Joomla 4.2.1 update is not withdrawn immediately. The bug is so serious that should be immediately reported on all social networks as well as the main Joomla site with the steps required to fix the problems it causes. Instead of this, we have

Joomla 4.2.1 Security and Bug Fix Release
The Joomla! Project is delighted to announce a security release for 4.x series of Joomla which addresses a security vulnerability and contains various bug fixes and improvements

everywhere.

[leolam]

The Yootheme forum has a good solution and "formfranka" is right. Michael, a sr. Suppport specialist at Yoothe wrote and I quote

The label "Delete List Entry" tends to be a bit misleading. But it is the same as clicking on the (x) icon in the column "Checked". So, if I were asked, the label should consequently be "Check List Entry".

The "delete" does not refer to the physical files in the list but just to the notification entry. If you click on "Delete List" all ticked notifications in the list will be removed from the list. The referenced files will remain where they are, though.

We use Yotheme Pro on multiple sites and we had this issue also. Michael's solution worked for us and some of our clients on YT Pro. I tested this on a few RT-Theme site with same results. Notifications gone. Note this is not a template issue by any provider...It is a Joomla issue! (one more after insufficient release testing.....again)

Leo

[sozzled]

I must've been asleep!

My requests to the forum moderators, to provide us a place to discuss RC versions of proposed new releases of J! were ignored. If the J! project developers are not interested in the discussions we have here on this forum then why bother to announce "please test this RC version" here on the forum? There was always the likelihood that these RC versions would contain errors and defects leading to further frustration among the community and resulting in ongoing embarrassment for the J! development team.

The chickens have come home to roost. This year alone there have been a couple of release failures after calling for people to test the RC versions. J! 4.1.1 was one and now, it seems, J! 4.2.1 is another. I write this because I see today that J! 4.2.2 is available.

j!422-available.png

A couple of days ago I updated two disposable (testing) J! 4.2.x websites to J! 4.2.1. These sites were updated from J! 4.1.5 to J! 4.2.0 and then to J! 4.2.1. I am still running my current J! 4.x "production" sites with J! 4.1.5. Ever cautious, I read other people's experiences with new releases before rushing headlong into unchartered territory. So what happened with J! 4.2.1? What happened to the announcement about J! 4.2.2 RC? Why was J! 4.2.2 released?

This is my problem: I'm undecided whether I should be relieved that I held back updating my J! 4.1.5 websites to J! 4.2.1 or whether I should be nervous about using J! 4.2.2. I don't think I'm alone here.

[AMurray]

I'd agree, not sure why there wasn't an RC for this 4.2.2 release but there's a few more fixes for this release.

https://www.joomla.org/announcements/re ... lease.html

@brianteeman has been busy with a half-dozen PR's for this release.... .

[sozzled]

If you look at the issue tracker, there are nearly fifty issues that been "tested" and tagged "ready to commit" that did not make it into the J! 4.2.2 release. If I understand this properly—and I could be mistaken—this means that, currently, there is a long list of known issues with J! 4.2.x that won't be attended to until J! 4.2.3 at the very least. I think I'll wait; J! 4.1.5 is good enough for me for the present.

[Per Yngve Berg]

4.2.2 is rushed out to fix the Fido Outage issue only.

[sozzled]

4.2.2 is rushed out to fix the Fido Outage issue only.

I don't know about that: see https://github.com/joomla/joomla-cms/mi ... 6?closed=1.

Can someone tell us if those twenty-three issues were merged into J! 4.2.2 or not? I would like to know what happened and what's happening with J! 4.2.x.

[brian]

4.2.2 is rushed out to fix the Fido Outage issue only.

plus a few minor pull requests that has already been merged from the queue before the fido outage

If I understand this properly—and I could be mistaken

No you dont understand it properly and you are mistaken

Can someone tell us if those twenty-three issues were merged into J! 4.2.2 or not?

Yes they were merged into 4.2.2 and that is exactly what the link shows you

I would like to know what happened and what's happening with J! 4.2.x.

So you can spread more FUD?

[pe7er]

Joomla! 4.2.2 Released: viewtopic.php?f=8&t=996257
Discuss Joomla! 4.2.2: viewtopic.php?f=9&t=996258