Discuss Joomla! 4.2.7

[pe7er]

Here you can discuss about the release of Joomla 4.2.7

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

[PhilTaylor-Prazgod]

Once again, as Im banned from contributing to the project - and cannot report this anywhere else - I'll just leave this here.

Joomla 4.2.7 has a code error in a security fix. It should be fixed and a new version should be immediately released.

Joomla 4.2.7 cannot be used on any version in the PHP 7.2 series (which is above the published technical requirements https://downloads.joomla.org/technical-requirements) because once again a last moment "security fix" added to Joomla 4.2.7 at release time was untested in older PHP versions and contains code incompatible with all PHP versions less than PHP 7.3 - that is, Joomla 4.2.7 is no longer compatible with any PHP 7.2 version - despite the published technical requirements of Joomla 4 stating it should be.

Evidence: https://3v4l.org/vtB1U

The Commit that caused this error: https://github.com/joomla/joomla-cms/co ... 3a3fa22df6

Someone should post this here https://github.com/joomla/joomla-cms/issues - but of course I cannot as my input is not valued.

[JasnaSontag]

Joomla 4.2.7 has a code error in a security fix. It should be fixed and a new version should be immediately released.

Thank you

I updated on 4.2.7 in WAMP and nothing appear on php 8.2.1 so I turned back to 8.1.0
Everything else looks good.

[PhilTaylor-Prazgod]

I updated on 4.2.7 in WAMP and nothing appear on php 8.2.1 so I turned back to 8.1.0

Unrelated to the code issue Im talking about.

Hell, Joomla 4's official system requirements RECOMMEND PHP 8.0 - that end of life, security releases only, series of PHP, you can't expect this project to actually work on PHP 8.2.1 right ;-) ;-)

[PhilTaylor-Prazgod]

Release Blocker for Joomla 4.2.8 - You're welcome.

https://github.com/joomla/joomla-cms/pull/39764

[gws]

+1 @ Phil

[SigridGR]

The problem only effects Joomla installation, if you are on PHP 7.2.

We have tested the issue and here you can find more information in the Joomla Documentation:
https://docs.joomla.org/J4.x:Actionlogs ... ith_php7.2

Here is also the link to the PR in github:
https://github.com/joomla/joomla-cms/pull/39764

We have decided that we will stay within the current release cycle. The next Joomla release 4.2.8 will be in 6 weeks.

Thanks Phil for reporting it.

[xtremo54]

I don't use PHP 7.2.......so is it OK to update with this release?

[SigridGR]

yes, you can update.
The update process itself is not broken on 4.2.7 - just the action log view showed an error message.

[xtremo54]

yes, you can update.
The update process itself is not broken on 4.2.7 - just the action log view showed an error message.

Many thanks!

[Rondeb]

Update 15 J4 sites with no problems.

Thanks Joomla Team.

[toivo]

Localhost and remote sites updated to 4.2.7 smoothly, as usual. Thank you teams and individuals involved in developing, testing and releasing the update!

[JurajB]

administrator/index.php?option=com_joomlaupdate&task=update.finalise&6f7d684ba5a34dda6985fd82c7602920=1
Sorry, there was a problem we could not recover from.
The server returned a "500 - Whoops, looks like something went wrong."

Besides this Joomla! works correctly on 4.2.7

[formfranska]

Multiple sites updated smoothly. Thank you J Team
YOOtheme Version 3.0.22
PHP 8.1.13 and PHP 8.1.14

[AMurray]

two live sites updated no issue.

one localhost (Wampserver) site seemed to update but it also appeared to stall at 52% on the progress indicator.

I had to restart WAMPServer, and browser and Joomla 4.2.7 came up as if it had succeeded with no immediate indication of issues.

[Triplicate]

Update 15 J4 sites with no problems.

Thanks Joomla Team.

How much to do my site?

I don't find this so easy and I'm not alone by a long shot. There are plenty of experts here I respect that can't bring this to an easy resolution. Sure I've got a handful of modules/plugins and I'm proud of that. This is just one thread and there are endless problems in general with this 500 error alone among all the other upgrade issues.

To me this shows there is something fundamentally wrong with the whole process. Joomla can't stop from getting in it's own way!

I believe also that it SHOULD BE "no problems" as you say, but for everyone, clearly it's not that way.

Think about it... we have a Joomla 4 version (or any new version of the future) that places demands and complexities on all previous versions, modules and plugins of Joomla that DISALLOWS a clean upgrade path by deeming the past coder files useless and thus breaking everything. The Doctor says "here take this pill but don't forget it could cause serious illness or death". I don't want to risk taking this pill anymore. The risks are too high and completely insane!

I know the train has left the station and it's too late, but given all the issues and problems with v4 I'm seeing in these threads on this forum, it clearly was not ready for prime time when it was first released. Even with 4.2.7 it seems like a beta product. Remember Microsoft Bob?

Only the Core Developers know what the new demands are but do nothing with that knowledge in helping identify the OFFENDING FILES and/or code violations of the past. "Joomla Update" is not enough. It seems to me these same people should provide scripts, utilities and other software tools to run on old sights to provide us admins at least the names of the offending files. THEY HAVE ALL THE INFO TO DO IT!. So these coders that bring us this great Joomla major software upgrades appear to care less about past events and the future issues we face trying to migrate forward.

Imagine if all the module and plugin developers who provide us with one click updates have mostly unsuccessful update messages and just keep braking stuff constantly. Well, that's what I see going on with every new major Joomla upgrade now.

This leaves us with all the dedicated volunteers here in these forums trying desperately to help others with a plethora of upgrade issues and have little to no knowledge or tools to be able to identify specific files that are the real reasons upgrades are failing. Joomla Upgrade has the right idea but is in it's infancy as to what's required to do pain free upgrades/migrations now.

This is my situation, link below, and I feel helpless on moving forward to newer Joomla versions despite of all the great people here trying to help me. I've been here since Mambo so I've been around and seen a lot of things. I can easily see how the volunteers hands are tied not having the appropriate software tools and or core knowledge. (mentioned above) Maybe it's time for a new CMS?

Help us help these great volunteers!

[link removed]

Regards
Ed