The link with the relevant information is in the message

It checks if all the requirements meet the recommended versions, so showing that result to the user will be useful.

As I mentioned above if someone knows the issue specifically then s/he might ask the hosting provider to fix/update that.

I checked the doc and I know which component needed to be updated and I did that. But I am sure there are others who might not be able to do that.

Did you read carefully what Brian said, and the technical requirements for J!5?
https://manual.joomla.org/docs/next/get-started/technical-requirements/#requirements-for-joomla-5x

The OP doesn't need help obtaining the requirements. They're referring to the generic message displayed.

Seeing as the checks are already performed, it would make sense to show which check actually failed, rather than having to manally find the version of 3 separate services.

@ghazal

Did you read carefully what Brian said, and the technical requirements for J!5? https://manual.joomla.org/docs/next/get-started/technical-requirements/#requirements-for-joomla-5x

Please read my previous comments first!
This was not the link with the generic message, it was https://downloads.joomla.org/technical-requirements, which was last updated on Last Updated: 17 August 2021. I know where to look and how to fix this issue. I also know not every other Joomla user will have the same knowledge and skills to find server configurations of multiple services.

Joomla 5 is a major release and it must have separate pages for server requirements and other details.

@C-Lodder thanks for understanding the issue.

I did not understand the reason for hiding the test results and showing a generic message with a link that does not have the requirements of v5.

it is easy enough to make the requested change if the maintainers agreed

it is easy enough to make the requested change if the maintainers agreed

@brianteeman I would like that but I'm only one. Maybe you could make a PR to come forward?

It checks if all the requirements meet the recommended versions, so showing that result to the user will be useful.

As I mentioned above if someone knows the issue specifically then s/he might ask the hosting provider to fix/update that.

I checked the doc and I know which component needed to be updated and I did that. But I am sure there are others who might not be able to do that.

showing the issues that prevent it is done in 3 to 4 and 4.+ so idk why it shouldn't be that way in 5 also.

@richard67 in light of comments from the release leads I wont waste my time on it without prior approval.

showing the issues that prevent it is done in 3 to 4 and 4.+ so idk why it shouldn't be that way in 5 also.

That;s not correct

... in light of comments from the release leads ...

@brianteeman Where? Have I missed something?

As already was discussed in #42034
The Updater is picking the best URL match for User site from available in update XML, based on Server environment. Because in XML it is possible to provide an update for differnt envrimoments (we do not use it, but it is possible).
It does not meant to show any "check result", but only the "best URL" if any is match to env.

To display a proper check result it is need to code some additional testing code aside existing. Or re-think existing.

It is not a trivial change.
Until someone will come come up with proper solution I would suggest to not pollute the issue.
Or it can be just closed.

@nasirkhan thanks for bringing this up.
From a user's point of view I completely agree with you.

But it seems that this is not as trivial, as @Fedik explained and as we can see in former discussions.

I suggest to keep this open.

showing the issues that prevent it is done in 3 to 4 and 4.+ so idk why it shouldn't be that way in 5 also.

That;s not correct

@brianteeman once again you run your mouth before engaging brain. When you update from 4.3 to 4.4 it runs a compatiblity check and shows you what might be issues. If you think it doesn't then you should reinstall core and put your glasses on.

@N6REJ The issue here and the related issue #42034 are not about the pre-update check, they are about no update being applicable due to minimum version requirements for PHP and database for the update are not met. This is something which cannot have happened from 4.3 to 4.4 as these requirements only change with a new major version, i.e. from 3 to 4 or 4 to 5.

I expected it to show me in detail which requirements were not met to update to v5.0.0. For example, if the PHP version is the issue, it displays the PHP version available on the server and the recommended version.

@richard67 thats not what I understand from the opening of the ticket

I expected it to show me in detail which requirements were not met to update to v5.0.0. For example, if the PHP version is the issue, it displays the PHP version available on the server and the recommended version.

and 3->4 did have the check https://docs.joomla.org/Joomla_3.x_to_4.x_Step_by_Step_Migration

I have just received this same message. Firstly, the link goes to the wrong info page as it has been moved to https://manual.joomla.org/docs/next/get-started/technical-requirements/#fn-2

That aside, I upgraded an old version of a site on a backup sub-domain of a J4 site, upgrading it to 4.4.0 and then to 5.0.0 successfully as a test a couple of days ago. Then, I copied over the latest live version to the same domain and tried to upgrade that one, only to get this message 'This site can't be updated...' message . My PHP is 8.1.24, database is 10.6.15-MariaDB-cll-lve-log. The Web Server is LiteSpeed - an Apache alternative - but which is not listed in the requirements page but has always worked before.

BUT... I logged out and logged in again on another browser (from Firefox to Chrome) and it has now updated to 5.0.0. Is it a cache issue, perhaps?

and 3->4 did have the check https://docs.joomla.org/Joomla_3.x_to_4.x_Step_by_Step_Migration

@N6REJ We are not talking about the check for the PHP version and database type being supported which is and always was shown in the pre-update checker. This always referred to the currently installed Joomla version, not to the one to which you want to update.

What we are talking about is that when the updater searches for an update, it sorts out all updates which do not have the right targetplatgormversion in their XML. In addition it checks the required PHP version and the required versions for the different database server types from the update site's XML and sorts out unsuitable updates.

In J3 this resulted in "no update found" for the quickicon and the update component's view.

Since J4.something the quickicon had shown an available update, but the component view not, this was confusing and reported with issue #42034 and solved with PR #42103 so that the user gets a message that there has been an update found which is not suitable. That was all which could be done without bigger changes in the code of the update component and the installer library.

As said, this thing is only relevant for the requirements of the target version to which you want to update, and that is something which changes only with a major version and so can not have happened when updating from 4.3 to 4.4, like you wrote.

and that is why I wont waste my time without prior approval

thanks, everyone for participating in the conversation. I can not answer everyone but here are some replies I need to address. Many of you talking like this is not an issue and some others are suggesting ignoring/accepting this issue.

Please find and talk to someone who is using Joomla and has 0 technical knowledge, or just assume, s/he wants to update to J5. S/he will not have any clue about the issue and will land on the wrong page and if s/he is brave will open Joomla! Programmers Documentation, a page that is built for the Joomla developers. As s/he does not know the exact problem, who will help that person? S/he will hire a developer? call hosting company? or ask Joomla team members?

@Fedik

To display a proper check result it is need to code some additional testing code aside existing. Or re-think existing.

Why do you want to keep the issue and suggest not to code?

... Or it can be just closed.

This is a major issue for the end user, but surely not for the Joomla team members. Otherwise, it should have been fixed.

@N6REJ
thanks for sharing the link.

@richard67
why you are pushing to accept a sub-standard product?

This always referred to the currently installed Joomla version, not to the one to which you want to update.

This is Joomal 5, not Joomla 50 there are only a few major releases earlier. So first we need to agree, we want to build a good product. For minor releases, you are showing test results and for major releases, you are showing the wrong URL. Results help to fix/change what is needed.

I have wrote a different thing. And explained some root reasons of the issue. Please check it again. Thanks.

I'm going to give a users view and then be quiet.
From 3->4 we show what issues might exist.
from 4.3 to 4.4 we do the same if I recall
from 4->5 we SHOULD, and thought we did, show the same.

IMO we should do this for every release that has a possible conflict not just major releases.
Lets not force them to go to some document that may or may not be right ( we all know our documentation history ). Lets give them the info they need. Quite frankly if we have the ability to do it for one upgrade, irregardless if its a major or not, we should be able to do it for all upgrades.
This helps the uneducated end user. That shouldn't be a bad thing

@N6REJ Please read again the posts by @richard67 you are talking about something completely different to the issue here!!

As can be seen by this new issue report the situation in J3 was worse #42249

Any update on this?
(Using "Joomla" since the first Mambo releases, managing my own servers)

PHP 8.2.x
MariaDB 10.6.16
Apache/Litespeed Enterprise

Thanks!

@josephsimony Could you double-check the PHP and database versions in the system information in backend and if possible post a screenshot or text extract here?

@nasirkhan Could you double-check the PHP and database versions in the system information in backend and if possible post a screenshot or text extract here?

@nasirkhan Sorry, I've notified you by mistake. I meant @josephsimony . In your case it's clear that your database version is too low. In his case it is not clear yet, if he really has the mentioned PHP and database versions the message should not appear.

@richard67

@nasirkhan Sorry, I've notified you by mistake. I meant @josephsimony . In your case it's clear that your database version is too low. In his case it is not clear yet, if he really has the mentioned PHP and database versions the message should not appear.

Please understand that, I did not create the issue from any confusion! I know that the MySQL version did not meet the minimum requirement.

The message it shows is misleading, It asks to open a link that should contain related information, but that page asks to open another page that says

This is unreleased documentation for Joomla! Programmers Documentation 5.0 (upcoming) version.
For up-to-date documentation, see the latest version (4.3).

You are comparing the server PHP/MySQL versions with the minimum requirements. If you would show the server version and the required version side by side @josephsimony, me and other users will find the right reasons for not being able to update the site.

I believe there are capable contributors in the community who might solve the issue and publish Joomla 4.5.0 or so.

Can you please tell me why you want to stick with and push us to accept a sub-standard faulty release?

Can you please tell me why you want to stick with and push us to accept a sub-standard faulty release?

@nasirkhan Where have I said that? Please stop to blame me for having said something which I've never said.