J4.x:Updating from an existing version/de

2023-09-25T14:09:48Z

Maggus:

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

==Seite prüfen==
Nach der Aktualisierung sollte der Browser Cache geleert werden und sichergestellt werden, dass das Update erfolgreich war. Es gibt zwei Überprüfungen, die schnell vom Erweiterungs-Manager aus durchgeführt werden können.

Navigiere zu {{rarr|Erweiterungen,Datenbank}}. Wenn die Datenbank aktuell ist, sollte der Bildschirm in etwa so aussehen:

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|Datenbank ohne Probleme]]

Wenn die Datenbank nicht aktuell ist, wird eine Liste der gefundenen Probleme angezeigt, ähnlich wie in diesem Abbild:

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|Datenbank mit 3 Problemen]]

In diesem Fall sollte der Reparieren Button oben links genutzt werden. Joomla wird die Datenbank nun aktualisieren, um die angezeigten Fehler zu beheben und anschließend die Seite erneut anzeigen. Falls die Reparatur erfolgreich war, wird angezeigt, dass die Datenbank auf dem neuesten Stand ist.

'''N.B.''' Sofern immer noch ein Fehler vorhanden ist, sollte geprüft werden, ob alle Datenbank-Tabellen freigegeben sind.

==Erweiterungen: Überprüfen==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/59/de

2023-09-25T14:09:46Z

Maggus:

==Erweiterungen: Überprüfen==

J4.x:Updating from an existing version/de

2023-09-25T14:09:21Z

Maggus: Created page with "'''N.B.''' Sofern immer noch ein Fehler vorhanden ist, sollte geprüft werden, ob alle Datenbank-Tabellen freigegeben sind."

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

==Seite prüfen==
Nach der Aktualisierung sollte der Browser Cache geleert werden und sichergestellt werden, dass das Update erfolgreich war. Es gibt zwei Überprüfungen, die schnell vom Erweiterungs-Manager aus durchgeführt werden können.

Navigiere zu {{rarr|Erweiterungen,Datenbank}}. Wenn die Datenbank aktuell ist, sollte der Bildschirm in etwa so aussehen:

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|Datenbank ohne Probleme]]

Wenn die Datenbank nicht aktuell ist, wird eine Liste der gefundenen Probleme angezeigt, ähnlich wie in diesem Abbild:

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|Datenbank mit 3 Problemen]]

In diesem Fall sollte der Reparieren Button oben links genutzt werden. Joomla wird die Datenbank nun aktualisieren, um die angezeigten Fehler zu beheben und anschließend die Seite erneut anzeigen. Falls die Reparatur erfolgreich war, wird angezeigt, dass die Datenbank auf dem neuesten Stand ist.

'''N.B.''' Sofern immer noch ein Fehler vorhanden ist, sollte geprüft werden, ob alle Datenbank-Tabellen freigegeben sind.

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/58/de

2023-09-25T14:09:21Z

Maggus: Created page with "'''N.B.''' Sofern immer noch ein Fehler vorhanden ist, sollte geprüft werden, ob alle Datenbank-Tabellen freigegeben sind."

'''N.B.''' Sofern immer noch ein Fehler vorhanden ist, sollte geprüft werden, ob alle Datenbank-Tabellen freigegeben sind.

J4.x:Updating from an existing version/de

2023-09-25T14:07:15Z

Maggus: Created page with "In diesem Fall sollte der Reparieren Button oben links genutzt werden. Joomla wird die Datenbank nun aktualisieren, um die angezeigten Fehler zu beheben und anschließend die..."

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

==Seite prüfen==
Nach der Aktualisierung sollte der Browser Cache geleert werden und sichergestellt werden, dass das Update erfolgreich war. Es gibt zwei Überprüfungen, die schnell vom Erweiterungs-Manager aus durchgeführt werden können.

Navigiere zu {{rarr|Erweiterungen,Datenbank}}. Wenn die Datenbank aktuell ist, sollte der Bildschirm in etwa so aussehen:

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|Datenbank ohne Probleme]]

Wenn die Datenbank nicht aktuell ist, wird eine Liste der gefundenen Probleme angezeigt, ähnlich wie in diesem Abbild:

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|Datenbank mit 3 Problemen]]

In diesem Fall sollte der Reparieren Button oben links genutzt werden. Joomla wird die Datenbank nun aktualisieren, um die angezeigten Fehler zu beheben und anschließend die Seite erneut anzeigen. Falls die Reparatur erfolgreich war, wird angezeigt, dass die Datenbank auf dem neuesten Stand ist.

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/57/de

2023-09-25T14:07:11Z

In diesem Fall sollte der Reparieren Button oben links genutzt werden. Joomla wird die Datenbank nun aktualisieren, um die angezeigten Fehler zu beheben und anschließend die Seite erneut anzeigen. Falls die Reparatur erfolgreich war, wird angezeigt, dass die Datenbank auf dem neuesten Stand ist.

J4.x:Updating from an existing version/de

2023-09-25T14:00:51Z

Maggus: Created page with "Datenbank mit 3 Problemen"

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

==Seite prüfen==
Nach der Aktualisierung sollte der Browser Cache geleert werden und sichergestellt werden, dass das Update erfolgreich war. Es gibt zwei Überprüfungen, die schnell vom Erweiterungs-Manager aus durchgeführt werden können.

Navigiere zu {{rarr|Erweiterungen,Datenbank}}. Wenn die Datenbank aktuell ist, sollte der Bildschirm in etwa so aussehen:

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|Datenbank ohne Probleme]]

Wenn die Datenbank nicht aktuell ist, wird eine Liste der gefundenen Probleme angezeigt, ähnlich wie in diesem Abbild:

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|Datenbank mit 3 Problemen]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/56/de

2023-09-25T14:00:50Z

Maggus: Created page with "Datenbank mit 3 Problemen"

Datenbank mit 3 Problemen

J4.x:Updating from an existing version/de

2023-09-25T14:00:23Z

Maggus:

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

==Seite prüfen==
Nach der Aktualisierung sollte der Browser Cache geleert werden und sichergestellt werden, dass das Update erfolgreich war. Es gibt zwei Überprüfungen, die schnell vom Erweiterungs-Manager aus durchgeführt werden können.

Navigiere zu {{rarr|Erweiterungen,Datenbank}}. Wenn die Datenbank aktuell ist, sollte der Bildschirm in etwa so aussehen:

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|Datenbank ohne Probleme]]

Wenn die Datenbank nicht aktuell ist, wird eine Liste der gefundenen Probleme angezeigt, ähnlich wie in diesem Abbild:

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With 3 Database Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/54/de

2023-09-25T14:00:15Z

Maggus:

Wenn die Datenbank nicht aktuell ist, wird eine Liste der gefundenen Probleme angezeigt, ähnlich wie in diesem Abbild:

J4.x:Updating from an existing version/de

2023-09-25T13:59:46Z

Maggus: Created page with "Wenn die Datenbank nicht aktuell ist, wird eine Liste zu den erkannten Problemen angezeigt, ähnlich wie in diesem Abbild:"

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

==Seite prüfen==
Nach der Aktualisierung sollte der Browser Cache geleert werden und sichergestellt werden, dass das Update erfolgreich war. Es gibt zwei Überprüfungen, die schnell vom Erweiterungs-Manager aus durchgeführt werden können.

Navigiere zu {{rarr|Erweiterungen,Datenbank}}. Wenn die Datenbank aktuell ist, sollte der Bildschirm in etwa so aussehen:

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|Datenbank ohne Probleme]]

Wenn die Datenbank nicht aktuell ist, wird eine Liste zu den erkannten Problemen angezeigt, ähnlich wie in diesem Abbild:

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With 3 Database Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/54/de

2023-09-25T13:59:40Z

Maggus: Created page with "Wenn die Datenbank nicht aktuell ist, wird eine Liste zu den erkannten Problemen angezeigt, ähnlich wie in diesem Abbild:"

Wenn die Datenbank nicht aktuell ist, wird eine Liste zu den erkannten Problemen angezeigt, ähnlich wie in diesem Abbild:

J4.x:Updating from an existing version/de

2023-09-25T13:58:22Z

Maggus: Created page with "Datenbank ohne Probleme"

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

==Seite prüfen==
Nach der Aktualisierung sollte der Browser Cache geleert werden und sichergestellt werden, dass das Update erfolgreich war. Es gibt zwei Überprüfungen, die schnell vom Erweiterungs-Manager aus durchgeführt werden können.

Navigiere zu {{rarr|Erweiterungen,Datenbank}}. Wenn die Datenbank aktuell ist, sollte der Bildschirm in etwa so aussehen:

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|Datenbank ohne Probleme]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
</div>

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With 3 Database Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/53/de

2023-09-25T13:58:18Z

Maggus: Created page with "Datenbank ohne Probleme"

Datenbank ohne Probleme

J4.x:Updating from an existing version/de

2023-09-25T13:57:30Z

Maggus: Created page with "Navigiere zu {{rarr|Erweiterungen,Datenbank}}. Wenn die Datenbank aktuell ist, sollte der Bildschirm in etwa so aussehen:"

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

==Seite prüfen==
Nach der Aktualisierung sollte der Browser Cache geleert werden und sichergestellt werden, dass das Update erfolgreich war. Es gibt zwei Überprüfungen, die schnell vom Erweiterungs-Manager aus durchgeführt werden können.

Navigiere zu {{rarr|Erweiterungen,Datenbank}}. Wenn die Datenbank aktuell ist, sollte der Bildschirm in etwa so aussehen:

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With No Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
</div>

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With 3 Database Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/51/de

2023-09-25T13:57:28Z

Maggus: Created page with "Navigiere zu {{rarr|Erweiterungen,Datenbank}}. Wenn die Datenbank aktuell ist, sollte der Bildschirm in etwa so aussehen:"

Navigiere zu {{rarr|Erweiterungen,Datenbank}}. Wenn die Datenbank aktuell ist, sollte der Bildschirm in etwa so aussehen:

J4.x:Updating from an existing version/de

2023-09-25T13:54:47Z

Maggus: Created page with "Nach der Aktualisierung sollte der Browser Cache geleert werden und sichergestellt werden, dass das Update erfolgreich war. Es gibt zwei Überprüfungen, die schnell vom Erwei..."

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

==Seite prüfen==
Nach der Aktualisierung sollte der Browser Cache geleert werden und sichergestellt werden, dass das Update erfolgreich war. Es gibt zwei Überprüfungen, die schnell vom Erweiterungs-Manager aus durchgeführt werden können.

<div lang="en" dir="ltr" class="mw-content-ltr">
Navigate to {{rarr|Extension Manager,Database}}. If your database is up to date, you should see a screen similar to the one below:
</div>

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With No Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
</div>

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With 3 Database Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/50/de

2023-09-25T13:54:41Z

Nach der Aktualisierung sollte der Browser Cache geleert werden und sichergestellt werden, dass das Update erfolgreich war. Es gibt zwei Überprüfungen, die schnell vom Erweiterungs-Manager aus durchgeführt werden können.

J4.x:Updating from an existing version/de

2023-09-25T13:51:10Z

Maggus:

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

==Seite prüfen==
<div lang="en" dir="ltr" class="mw-content-ltr">
After an update, it is a good idea to clear your browser cache and check your site to make sure the update was successful. There are two quick checks you can do from the Extension Manager.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Navigate to {{rarr|Extension Manager,Database}}. If your database is up to date, you should see a screen similar to the one below:
</div>

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With No Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
</div>

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With 3 Database Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/49/de

2023-09-25T13:51:08Z

Maggus:

==Seite prüfen==

J4.x:Updating from an existing version/de

2023-09-25T13:50:55Z

Maggus: Created page with "# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen."

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

==Checking Your Site==
<div lang="en" dir="ltr" class="mw-content-ltr">
After an update, it is a good idea to clear your browser cache and check your site to make sure the update was successful. There are two quick checks you can do from the Extension Manager.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Navigate to {{rarr|Extension Manager,Database}}. If your database is up to date, you should see a screen similar to the one below:
</div>

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With No Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
</div>

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With 3 Database Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/48/de

2023-09-25T13:50:54Z

Maggus: Created page with "# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen."

# Leere den Browser Cache und stelle sicher, dass das Update erfolgreich war, indem du den Schritten folgst, die unter '''Seite prüfen''' stehen.

J4.x:Updating from an existing version/de

2023-09-25T13:49:48Z

Maggus: Created page with "# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Program..."

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.
<div lang="en" dir="ltr" class="mw-content-ltr">
# Clear your browser's cache and check that the update was successful, using the steps outlined in the '''Checking Your Site''' tab.
</div>

==Checking Your Site==
<div lang="en" dir="ltr" class="mw-content-ltr">
After an update, it is a good idea to clear your browser cache and check your site to make sure the update was successful. There are two quick checks you can do from the Extension Manager.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Navigate to {{rarr|Extension Manager,Database}}. If your database is up to date, you should see a screen similar to the one below:
</div>

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With No Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
</div>

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With 3 Database Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/47/de

2023-09-25T13:49:44Z

# Nutze eine der in diesem Dokument beschriebenen Methoden für die Aktualisierung. Diese Methoden installieren die neuen Programmdateien, löschen nicht mehr genutzte Programmdateien und aktualisieren die Datenbank, sofern die neue Joomla! Version dies braucht.

J4.x:Updating from an existing version/de

2023-09-25T13:45:24Z

Maggus: Created page with "# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat."

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.
<div lang="en" dir="ltr" class="mw-content-ltr">
# Update using one of the recommended methods outlined in this document. These methods install the new program files, delete unneeded old program files, and update the database as needed for the new Joomla version.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Clear your browser's cache and check that the update was successful, using the steps outlined in the '''Checking Your Site''' tab.
</div>

==Checking Your Site==
<div lang="en" dir="ltr" class="mw-content-ltr">
After an update, it is a good idea to clear your browser cache and check your site to make sure the update was successful. There are two quick checks you can do from the Extension Manager.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Navigate to {{rarr|Extension Manager,Database}}. If your database is up to date, you should see a screen similar to the one below:
</div>

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With No Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
</div>

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With 3 Database Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/46/de

2023-09-25T13:45:23Z

Maggus: Created page with "# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat."

# Schaue dir die Release Notes zur neuen Version an, um zu erfahren, was sich geändert hat.

J4.x:Updating from an existing version/de

2023-09-25T13:44:06Z

Maggus:

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
<div lang="en" dir="ltr" class="mw-content-ltr">
# Review the release notes for the new version to be familiar with what was changed.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Update using one of the recommended methods outlined in this document. These methods install the new program files, delete unneeded old program files, and update the database as needed for the new Joomla version.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Clear your browser's cache and check that the update was successful, using the steps outlined in the '''Checking Your Site''' tab.
</div>

==Checking Your Site==
<div lang="en" dir="ltr" class="mw-content-ltr">
After an update, it is a good idea to clear your browser cache and check your site to make sure the update was successful. There are two quick checks you can do from the Extension Manager.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Navigate to {{rarr|Extension Manager,Database}}. If your database is up to date, you should see a screen similar to the one below:
</div>

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With No Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
</div>

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With 3 Database Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/45/de

2023-09-25T13:44:06Z

Maggus:

# Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.

J4.x:Updating from an existing version/de

2023-09-25T13:43:57Z

Maggus: Created page with "Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer frühere..."

<noinclude><languages /></noinclude><br />
{{note|<center><big>'''Vor dem Update unbedingt ein Backup erstellen'''</big></center>|type=serious}}
==Introduction==
Es wird empfohlen, die Joomla Update Komponente zu nutzen, um Joomla zu aktualisieren.

Die standardmäßige Installation von Joomla 4 beinhaltet nach dem Login eine hilfreiche Benachrichtigungsleiste auf dem Home-Dashboard. So ist mit einem Blick ersichtlich, ob ein Update verfügbar ist und welche Versionsnummer es hat.

Auch wenn Joomla anzeigt, dass ein Update verfügbar ist, muss dieses immer noch manuell ausgeführt werden. Dieser Schritt ist einfach und sollte bei der nächstbesten Gelegenheit erfolgen, um die Website aktuell zu halten.

Wenn von einer früheren Joomla-Version vor 4.x aktualisiert wird, müssen folgende Punkte beachtet werden:

<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Potential_backward_compatibility_issues_in_Joomla_4|Potential backward compatibility issues in Joomla 4]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* [[S:MyLanguage/Joomla_3.x_to_4.x_Step_by_Step_Migration|Joomla 3.x to 4.x Step by Step Migration]]
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Updating 1.x or 2.x to 3.x: use [[S:MyLanguage/J3.x:Updating Joomla (Install Method)|Updating Joomla (Install Method)]].
</div>

==Zugriff auf die Update Komponente==

Wenn das Benachrichtigungsfeld auf dem Home Dashboard angezeigt wird, gelangt man durch Klicken auf die Benachrichtigung direkt zur Update Komponente.

[[File:j4x_joomla_update_notification-en.png|border|800px]]
{{-}}

Alternativ ist es auch möglich, im Administration Seitenmenü auf ''System'' zu klicken. Damit erreicht man das ''System Dashboard''.

[[File:j4x_joomla_system_dashboard_update-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
The System Dashboard has an ''Update Panel'' that includes a Joomla link that will show the available update version number. Click the ''Joomla'' link and you will be taken to the Update Component.
</div>

==Aktualisierung durchführen==
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

Achte sorgfältig darauf alle markierten Punkte vor dem Update zu beheben. Erweiterungen solltest du noch sorgfältiger prüfen und zuerst updaten.

Es ist nicht ungewöhnlich, Warnungen für "Empfohlene Einstellungen" zu sehen. Diese sind oft Server spezifisch und abhängig vom Host - es ist möglich, dass es sie schon gab, als du Joomla installiert hast und werden höchstwahrscheinlich das Update nicht verhindern.

Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast.

Unterhalb des Update Buttons ist ein link. In den meisten Fällen kannst du den ignorieren. Er stellt die Möglichkeit zur Verfügung die Update Ordner manuell auf deinen Server zu laden, falls dein Server von einer Firewall geschützt ist oder es aus anderen Gründen unmöglich ist auf den Joomla Update Server zuzugreifen.

Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update".

===Bestätige das Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

Klicke die Checkbox an, um zu bestätigen, dass du ein Backup gemacht und überprüft hast, dass die Erweiterungen kompatibel sind, dann klicke "Update starten".

===Update Fortschritt===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update.

===Fertigstellung===

[[File:j4x_joomla_updated-en.png|border|800px]]

Wenn der Fortschrittsbalken 100 % erreicht hat, bestätigt eine Nachricht das Update deiner Seite und die Versionsnummer. Die neue Versionsnummer wird ebenso in der oberen Werkzeugleiste neben dem Seitennamen angezeigt.

Klicke den "Zurück" Button und du kommst zurück zur Joomla Update Komponente, dort kannst du erneut nach Updates schauen.

==Überprüfungen nach dem Update==

Wenn das Update fertiggestellt ist, solltest du überprüfen das alles wie erwartet funktioniert und keine Fehler oder Änderungen auftreten, die weitere Aktionen erfordern.

===Frontend überprüfen===
Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update.

Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden.

===System Checks===

in Joomla ist es einfach eine "Gesundheits" Überprüfung zu machen. Klick auf dem Seitenmenu "System" an, um zurück zum System Dashboard zu kommen. Hier bekommt man einen Überblick über den aktuellen Stand der Joomla Seite.

[[File:j4x_system_dashboard-en.png|border|800px]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this example we can see that since the update we have two items that require attention. They are marked with a label that includes a number. The number relates to how many items require attention. Clicking on each one will allow you to fix them.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''Note''' The System Dashboard makes a check each time the page is loaded. Bear in mind that browser caching settings could affect this. It's good practice to clear the browser's cache when checking.
</div>

==== Empfohlene Schritte und Aktionen ====
Es wird empfohlen, diese Schritte durchzuführen, wenn eine Produktivseite aktualisiert wird:
Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.
<div lang="en" dir="ltr" class="mw-content-ltr">
# Review the release notes for the new version to be familiar with what was changed.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Update using one of the recommended methods outlined in this document. These methods install the new program files, delete unneeded old program files, and update the database as needed for the new Joomla version.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Clear your browser's cache and check that the update was successful, using the steps outlined in the '''Checking Your Site''' tab.
</div>

==Checking Your Site==
<div lang="en" dir="ltr" class="mw-content-ltr">
After an update, it is a good idea to clear your browser cache and check your site to make sure the update was successful. There are two quick checks you can do from the Extension Manager.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Navigate to {{rarr|Extension Manager,Database}}. If your database is up to date, you should see a screen similar to the one below:
</div>

[[File:j4x-update-screenshot-db-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With No Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If your database is not up to date, you will see a screen listing the problems found, similar to the one below:
</div>

[[File:j4x-update-screenshot-db-not-ok-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Database Screen With 3 Database Problems
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, press the Fix button in the upper right corner. Joomla will update your database to correct the issues listed and then it will re-display the screen. If the fix was successful, the display will indicate that the database is up to date.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
'''N.B.''' If any errors still exist make sure all the database tables are checked in.
</div>

==Extension Manager: Discover==
<div lang="en" dir="ltr" class="mw-content-ltr">
In some cases, when you update to a new Joomla version, new core extensions are added. If there were problems with the database update, these extensions may not have been correctly installed. To check this, navigate to {{rarr|System,Discover}}. Then click on the Discover icon in the toolbar. The screen should show as follows:
</div>

[[File:j4x-update-screenshot-extensions-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With No Extensions To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
If so, you know that any new extensions added during the update were correctly installed in the database.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If there are uninstalled extensions, they will show similar to the following screen:
</div>

[[File:j4x-update-screenshot-uninstalled-ext-en.png|border|800px|<div lang="en" dir="ltr" class="mw-content-ltr">
Discover Screen With One Extension To Install
</div>]]

<div lang="en" dir="ltr" class="mw-content-ltr">
In this case, check the boxes and click on the Install icon in the toolbar. Joomla will install the extension(s) and then display the screen showing no extensions discovered. At this point, the new extensions have been installed in the database.
</div>

==Troubleshooting==
<span lang="en" dir="ltr" class="mw-content-ltr">If you have any questions, problems or errors before, during or after the update, please ask them on the ''[[jforum:812|Migrating and Upgrading to Joomla! 4.x Forum]]''.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
If you have problems or errors during the update process, here are some tips.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* Clearing your browser cache. There may have been changes to the CSS or JavaScript that will need to be reloaded by your Web browser after an update.
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
* If any database error messages show after the update, be sure to check the {{rarr|System,Maintenance panel,Database}} link. In some cases, if a database error occurs it will prevent all of the database updates from running. In this case, you can run them from the Database link and then use the {{rarr|System,Install,Discover}} method to check and install any new extensions.
</div>

== Troubleshooting Joomla Update ==

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla Update is a core component which is responsible for determining if there is a newer version of Joomla available for installation of your site, download it (or let you upload it) and install it. It has been available in Joomla since Joomla 2.5.1 and as a third party extension two years prior to that. You can access it at System, Update, Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The update process consists of several different steps. While every care has been taken to make this process as trouble–free as possible there's always a small chance that something may go wrong, typically due to a very restrictive server configuration or network conditions on a very small minority of sites.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
The following troubleshooting instructions are organised by update step to make it easier to find the information you are looking for. Furthermore, it is an exhaustive resource, based on more than a decade of experience troubleshooting all possible (and some borderline impossible) problems with Joomla and extension updates. It lists problems which are extremely unlikely to occur. Don't let its length scare you; you are very unlikely to ever see any of these problems occur.
</div>

===Schauen, ob es Updates gibt===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will make a request to its update server over HTTPS and download an XML file provided by the Joomla project listing the latest available versions. The update server in use can be determined by going to {{rarr|System, Update,Joomla,Options}} and examining which update server is in use. You should use the ''Default'' update server to receive updates to your current major version of Joomla. Use ''Joomla Next'' when you want to upgrade your site to the next major version of Joomla — this is best done on a copy of your site to avoid any nasty surprises; not all third party extensions and templates will be compatible across major Joomla versions. The major version of Joomla is the first digit in the Joomla version, before the first dot. For example, the major version of Joomla 4.0.1 is 4.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If Joomla cannot determine that an update is available please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The Joomla Update information is out of date in the database. Go to {{rarr|System,Update,Joomla,Check for Updates}}.
* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the Testing update channel. Select ''Save & Close''. Click on Options again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.
* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to https://update.joomla.org. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.
* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by the Joomla update CDN. Please ask your host about it.
</div>

===Entscheiden, ob die Third Party Software kompatibel ist mit der neuen Version, die installiert werden soll===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla does not have a magical way of evaluating third party code for compatibility. Its report is based solely on the extension information kept in Joomla's ''#__extensions'' table, the update sites provided by the installed extensions and the update information provided by the developers of third party extensions including but not limited to which version of their software is compatible with which version of Joomla.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
If the information displayed is incorrect please check the following:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* What is the minimum stability for extension updates? Go to {{rarr|System,Update,Extensions,Options}}. The ''Minimum Extension Stability'' determines which is the minimum stability level of a third party software that Joomla will take into account when evaluating compatibility. For example, if this option is set to ''Stable'' but only a beta version of a third party extension is compatible with the Joomla version you want to upgrade to Joomla will tell you that there is no compatible version of the third party extension available.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update information may be out of date. Go to {{rarr|System,Update,Extensions,Check For Updates}}. Then go back to {{rarr|System,Update,Joomla}} and see if the extension now appears as compatible or if you are told than a compatible update is available.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update sites information in Joomla is corrupt. Go to {{rarr|System,Update,Update Sites,Rebuild}}. Then go to {{rarr|System,Update,Joomla,Options}}. Select the ''Testing'' update channel. Select ''Save & Close''. Click on ''Options'' again. Select the ''Default'' or ''Joomla Next'' update channel — depending on your preference — and click on ''Save & Close''.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTP/HTTPS requests at all or restricts them to predefined allowed IP addresses. This will prevent Joomla from retrieving update information from third party update sites. First go to {{rarr|System,Update,Update Sites}}. Below each update site you will see its URL. Make a list of those URLs. Then ask your host to allow your site to make requests to these URLs. Please note that some of these URLs may point to a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by most third party extension developers' update sites. Please ask your host about it.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may have 'orphaned' extensions. Most modern Joomla extensions are delivered as ‘package’ type extensions which include two or more related extensions. When installing a package extension Joomla records a package extension in its database. It then records the package ID to each of the installed extensions from that package in the database. The update information is provided for the package, not each individual extension. This association may break if you used ''Discover'' to install the extensions, extracted the package and installed the separate extensions directly. Joomla failed to record the package ID for each extension when installing the package (most likely because an error occurred) or your site has been upgraded from an old version of Joomla which predates the use of packages in extensions. In this case even updating the extension will '''not''' update the package association. There is currently no solution to this except determining manually the compatibility of extensions with each Joomla version.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* In some cases the number of requests Joomla sends to your server as it determines compatibility for each extension may overwhelm the server and trigger a Denial of Service protection. In this case some or all of the extensions will appear as of indeterminate compatibility status. Unfortunately, you will have to check the compatibility of each extension manually against the information published by extension's developer.</span>

===Das Update herunterladen===

<div lang="en" dir="ltr" class="mw-content-ltr">
Joomla will need to download its update package, a ZIP file which is similar to the Joomla installation ZIP file but without the web installer (the ''installation'' directory). This could fail for a few reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* The ZIP file is rather big. Joomla 4 update packages are around 25 MiB. If your server is slow, overwhelmed or has poor connectivity with GitHub — where Joomla update packages are downloaded — it may take a long time to download the package. If that time is longer than your server's PHP maximum execution time, its maximum CPU usage limit (as determined by ulimit -t in the server command line), the PHP-FPM timeout or the web server's timeout the download will fail and you will see an error page. You will have to ask your host for help with that.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* You may not have enough free space on your site. You need enough space to store the compressed update ZIP file and its extracted files. As a rule of thumb, you need about 50–60 MiB of free space for Joomla Update to work correctly. Do note that the free space reported by your hosting control panel is not always realtime, i.e. it may 'lag' several minutes or hours behind the actual disk space usage on your site. Moreover, further limits may be imposed by your host. If unsure, please ask your host.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host prevents making outbound HTTPS requests at all or restricts them to predefined allowed IP addresses. Please ask them to allow outbound HTTP requests to ''https://github.com''. This is a CDN, meaning that the exact IP address will be different depending on where the world you are trying to access this URL from. Do tell your host; they will know what to do with this information.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Your host may have an outdated SSL library which does not understand the modern TLS certificates used by GitHub. Please ask your host about it.</span>

===das Update extrahieren===

<div lang="en" dir="ltr" class="mw-content-ltr">
After the update ZIP file has downloaded Joomla needs to extract it on your site. Since Joomla is effectively replacing itself and because this process does take some time to complete it cannot happen within Joomla itself. Instead, a separate file (''administrator/components/com_joomlaupdate/extract.php'') is used to perform the update. This file is inert except when an update is in progress.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
You may get an error during the extraction for one of the following reasons:
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
* You cannot access the ''extract.php'' file because of a server protection e.g. a customised ''.htaccess'' file on Apache and Litespeed servers. Try accessing ''https://www.example.com/administrator/components/com_joomlaupdate/extract.php'' from a web browser, where ''https://www.example.com/'' is to be replaced with the URL to your site. You should see the message {"status":false,"message":"Invalid login"} If you see anything else you are being forbidden from accessing this file.
</div>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you can access the file but extracting the update fails immediately, there is a different server protection on your site which prevents the request to ''extract.php'' from being handled by that file. Please contact your host about this.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using CloudFlare, go to Rules and create a new Page Rule. Set the ''If URL Matches'' to ''*/administrator/components/com_joomlaupdate/extract.php'' and Then The Settings Are to “Disable Security” and on a new line ”Cache Level”, ‘Bypass’. Set the Order to ''First''. Click on Save and Deploy. This ensures that CloudFlare will not try to block the update extraction.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The update ZIP file is corrupt or truncated. This could happen if downloading the update file failed with an error. Go back and retry. See also the previous section.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* If you are using upload and update, i.e. you uploaded the update ZIP file yourself, please make sure that you are using only the official Joomla Update ZIP files. The extraction script only supports a subset of the ZIP archive format used by the official update ZIP files.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you run out of disk space? Please check the section above.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Are the ownership and permissions of all files correct? Joomla needs write access to all of its files and folders. If unsure, ask your host. There is no specific set of “good” permissions! The permissions needed depend on the ownership of your files and which system user the web server runs under.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* Did you lose network connectivity or your network has very high latency? It's possible that the request fails because of that.</span>
<span lang="en" dir="ltr" class="mw-content-ltr">* The extraction takes place by making consecutive requests to the aforementioned ''extract.php'' file. Each request is set up to take between 3 and 4 seconds. The process repeats until the entirety of the update file has been extracted. On some servers this cadence of requests to the same file from the same IP address may trigger the server's security. On other servers it may trigger a different server protection, e.g. a maximum PHP time limit, a maximum CPU usage limit or another server timeout. On even fewer servers running on CloudLinux, it could trigger a server memory outage situation if your server was already running low on memory. Contact your server about that; there is nothing you can do yourself to work around these server limitations.</span>

===Hochladen abschließen===

<div lang="en" dir="ltr" class="mw-content-ltr">
This is a two step process.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Right after the update ZIP file has been extracted, a final step will run which removes old files. When upgrading to a new major version of Joomla the list of files to remove is large and the process may timeout. Moreover, the point made in the previous section about ownership and permissions of files is important here too; Joomla needs write permissions to the old files and folders it has to remove. If this step fails you can resume it from the command line. Go into the ''cli'' folder and run ''php joomla.php update:joomla:remove-old-files''. If you cannot do it yourself ask your host to do it for you. You will also need to follow the workaround for the next step.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Finally, Joomla reloads and you are logged back into the Administrator interface. At this point Joomla updates its database tables and performs any database administration tasks. If this fails you can resume the process by going to {{rarr|System,Maintenance,Database}}. Select ''Joomla CMS'' from the list and click on ''Update Structure''.
</div>

<noinclude>
[[Category:Upgrading{{#translation:}}]]
[[Category:Joomla! 4.x{{#translation:}}]]
[[Category:Update Working Group{{#translation:}}]]
</noinclude>

Translations:J4.x:Updating from an existing version/45/de

2023-09-25T13:43:53Z

Mache ein Backup deiner Seite, bevor du auf die neue Version aktualisierst. Sollte während des Updates etwas schief laufen, kannst du die Seite ganz einfach zu einer früheren Version wiederherstellen.