No Code Attached Yet
avatar 7at1blow
7at1blow
25 Aug 2021

Steps to reproduce the issue

J4.0.2
Backend > System > Updates > Joomla

Expected result

Update Server is declared as 4.x

Actual result

Update Server is declared as 3.x instead of 4.x
see screenshot

2021-08-25 Joomla 4 Update Server 3 x

System information (as much as possible)

Additional comments

avatar 7at1blow 7at1blow - open - 25 Aug 2021
avatar joomla-cms-bot joomla-cms-bot - change - 25 Aug 2021
Labels Added: No Code Attached Yet
avatar joomla-cms-bot joomla-cms-bot - labeled - 25 Aug 2021
avatar 7at1blow 7at1blow - change - 25 Aug 2021
Title
[4.0] Update Server 3.x ?
[4.0] Update Server declared as 3.x ?
avatar 7at1blow 7at1blow - edited - 25 Aug 2021
avatar richard67
richard67 - comment - 25 Aug 2021

@7at1blow Your 4.0.2 is the result of a new installation? Or has it been updated? If so, from which version(s), i.e. which update history does it have?

avatar richard67
richard67 - comment - 25 Aug 2021

@7at1blow I just see it seems to be a mistake in the German language string:

COM_JOOMLAUPDATE_VIEW_DEFAULT_UPDATES_INFO_DEFAULT="Dieser Server ist mit dem „%s“-Update-Server verbunden - Von dieser Update-Quelle werden alle Updates für die aktuelle Hauptversion (3.x) angeboten."

That means you are very likely on the right update channel, just the text with the version number above the buttons is wrong.

Please report this issue here: https://github.com/joomlagerman/joomla

avatar richard67
richard67 - comment - 25 Aug 2021

@7at1blow I just see there is already a pull request in the German translations repository, so no need to report an issue there: joomlagerman/joomla#2045 . So it will be fixed with a futire update of the language pack, I think.

avatar richard67 richard67 - change - 25 Aug 2021
Status New Closed
Closed_Date 0000-00-00 00:00:00 2021-08-25 15:53:27
Closed_By richard67
avatar richard67 richard67 - close - 25 Aug 2021
avatar richard67
richard67 - comment - 25 Aug 2021

Closing as not a CMS core issue, see previous comments.


This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/35369.

avatar zero-24
zero-24 - comment - 25 Aug 2021

In the end it is a CMS issue. We should pass the versions via sprintf and not rely on the TTs to update the strings. While we are going to fix it now we should do it right in the CMS in the first place.

avatar richard67
richard67 - comment - 25 Aug 2021

In the end it is a CMS issue. We should pass the versions via sprintf and not rely on the TTs to update the strings. While we are going to fix it now we should do it right in the CMS in the first place.

@zero-24 Feel free to make a PR.

avatar zero-24
zero-24 - comment - 25 Aug 2021

In the end it is a CMS issue. We should pass the versions via sprintf and not rely on the TTs to update the strings. While we are going to fix it now we should do it right in the CMS in the first place.

@zero-24 Feel free to make a PR.

I know just want this to be logged here too.

avatar brianteeman
brianteeman - comment - 25 Aug 2021

note that it will require a completely new key

avatar richard67
richard67 - comment - 25 Aug 2021

For such major version related texts I think they could remain hardcoded and translators should properly translate from the English texts for J4 and not just reuse their J3 strings.

avatar brianteeman
brianteeman - comment - 25 Aug 2021

As we have no suitable quality control and we have seen from experience the problems a bad translation can cause (remember the installation folder) we have to do what we can to avoid issues. When experienced joomla users producing the french, german and american packs can produce language packs that have not been tested what chance do the language users have when the translators dont even use joomla

Add a Comment

Login with GitHub to post a comment