Discuss Joomla! 4.2.5 RC1

[pe7er]

Here you can discuss about the release of Joomla 4.2.5 RC1

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

[AMurray]

@pe7er,

Please advise the list of fixes for 4.2.5? The announcement post (viewtopic.php?f=8&t=997475) contains no detail (and also a couple of broken links).

Is this the list of fixes for 4.2.5?

Thanks.

[pe7er]

@AMurray,
Oops, those links were lost when copying the message.
I've just fixed them... Thanks!

[sozzled]

I haven't had the chance to test J! 4.2.5 RC1 yet. I see that the testing checklist has been modified in a very generic way. The results of previous testing for earlier J! 4.2.x releases have been erased from the spreadsheet. This means that we have no idea what issues were discovered in testing earlier releases of J! 4.2.x and may require re-testing now.

I note that, at the time of writing, no-one has used the spreadsheet. Either no-one is following the recommended testing methodology or no-one has tested J! 4.2.5 RC1 prior to its expected release in a couple of days' time. It would be nice to know whether J! 4.2.5 RC1 has been tested or is being tested prior to the release of the version available to the public.

From my reading of the list of changes coming in J! 4.2.5, it appears there has been no action on two outstanding bugs that were discovered in August that affect J! 4.2.0-4 and have been mentioned a number of times on this forum. These two bugs are:

1) Articles - Categories module causes "Serialization of 'Closure' is not allowed" error under certain conditions.

2) System - Privacy Consent and MFA plugins cause an infinite redirection loop.

[jgress-]

Michael,
We changed the sheet to be more "generic" so that it wouldn't be confusing as to what tab to use or if a new tab hadn't been made yet etc. We were listening to feedback.

We listened to a previous post where people wanted an announcement discussion, here it is.

How about not worrying who has tested what yet and instead test if you'd like to test?

We give the link to the closed issues and list the things the release leads tell us to focus on. From there, you can test whatever you want that you use. The purpose of the announcement is so that more real world sites can be tested by the community if they choose to.

The purpose of the sheet is to give people a place to start when they ask "what should I test?"

Perhaps you could test if you want to and bring up any issues you find here or in an issue at issues.joomla.org.

Is the whole process perfect? No, so if you want to test, test. We've listened to feedback for an announcement discussion. The sheet is there to guide you.

Best,
Jenn