What means "it did not work"? Do you have any error messages? If not, try it with error reporting set to maximum and debug on in global configuration. What error message do you get then and is there a call stack shown?

And do you have any 3rd party extensions which could cause it fail?

Without any additional info your issue helps us nothing.

Yes, the error message was: see screenshot below.
Debug and Error reporting set to maximum.
I've made the same updates in 2 web sites (2 different domains) in my own test environment with PHP 8.1.6 and 8.1.10 and they succeed perfectly.

Sorry! Here's the screenshot.

If it works with php 8.1.6 and php 8.1.0 what is different about php 8.1.11 that causes that error?

Sorry, I just don't know!

The installation of Joomla 4.2.2 "online" was made from backup to the empty public_html of the domain carmen-duran.com

And the discussion in the Joomla Forum (Update 4.2.2 to 4.2.3 failed!) is a real jungle for me, any Expert has a different point of view, but till now nobody gave me a clear tip what's really going on with that damn update.

Up to now I also have no idea yet. When you switch on debug in your global configuration in backend, part site, is there some stack trace shown in addition?

Or is there something in the server logs (if necessary ask your provider how to access them if you don’t know)?

What you could do if you urgently need to update your live site is do make a local copy, update that and then move that (files and database) to the live site. Ut then you should maybe make a subdomain on your hosting and keep a copy of your site with own files and db on that subdomain so we later still can reproduce the issue and not need to wait until the next Joomla release for an update being available again.

@sozzled tested on wamp with a vanilla J4.2.2 on php 8.1.11 with full success https://forum.joomla.org/viewtopic.php?f=812&t=996780&p=3672563#p3672531

@Jotinha-jrb User jotabe309 in the support forum, is that you? If so, wy haven't you reported here that your problem is solved meanwhile, liiktated in the forum here https://forum.joomla.org/viewtopic.php?f=812&t=996780&p=3672563#p3672665 ? It's not really helpful to open issues and then not post updates when a problem was solved.

So or so I think it is not a core issue since other users successfully updated from 4.2.2 to 4.2.3 wittt PHP 8.1.11.

Closing as not a core issue.

Sorry, I'm new here and simply forgot to close it immediately.

On Wed, 5 Oct 2022, 14:55 Richard Fath, @.***> wrote:

@Jotinha-jrb https://github.com/Jotinha-jrb User jotabe309 in the
support forum, is that you? If so, wy haven't you reported here that your
problem is solved meanwhile, liiktated in the forum here
https://forum.joomla.org/viewtopic.php?f=812&t=996780&p=3672563#p3672665
? It's not really helpful to open issues and then not post updates when a
problem was solved.

So or so I think it is not a core issue since other users successfully
updated from 4.2.2 to 4.2.3 wittt PHP 8.1.11.

Closing as not a core issue.

—
Reply to this email directly, view it on GitHub
#38890 (comment),
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AK7GOHZZCMZP5TZBTJFMKGTWBV3DZANCNFSM6AAAAAAQ22OMNU
.
You are receiving this because you were mentioned.Message ID:
@.***>