Joomla! Documentation - User contributions [en]

J4.x:Updating from an existing version/de

2023-08-26T12:57:47Z

Quiltgabi: Created page with "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 Ü..."

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/39/de

2023-08-26T12:57:44Z

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.

J4.x:Updating from an existing version/de

2023-08-26T12:53:20Z

Quiltgabi: Created page with "Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden."

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/37/de

2023-08-26T12:53:19Z

Quiltgabi: Created page with "Selbstverständlich solltest du deinen Browser Cache leeren um Änderungen der Formatvorlagen und Skripte zu laden."

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

J4.x:Updating from an existing version/de

2023-08-26T12:48:41Z

Quiltgabi: Created page with "Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update."

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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.

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/36/de

2023-08-26T12:48:36Z

Quiltgabi: Created page with "Schau dir das Frontend der Webseite an und überprüfe, ob alles so funktioniert und dargestellt wird wie vor dem Update."

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

J4.x:Updating from an existing version/de

2023-08-26T12:46:54Z

Quiltgabi:

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/35/de

2023-08-26T12:46:50Z

Quiltgabi:

===Frontend überprüfen===

J4.x:Updating from an existing version/de

2023-08-26T12:46:41Z

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

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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 Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/34/de

2023-08-26T12:46:37Z

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

J4.x:Updating from an existing version/de

2023-08-26T12:28:05Z

Quiltgabi:

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/33/de

2023-08-26T12:27:42Z

Quiltgabi:

==Überprüfungen nach dem Update==

J4.x:Updating from an existing version/de

2023-08-26T12:26:45Z

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

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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.

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/32/de

2023-08-26T12:26:36Z

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

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

J4.x:Updating from an existing version/de

2023-08-26T12:20:30Z

Quiltgabi: Created page with "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 Wer..."

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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.

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/31/de

2023-08-26T12:20:26Z

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.

J4.x:Updating from an existing version/de

2023-08-26T12:12:15Z

Quiltgabi:

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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]]

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/29/de

2023-08-26T12:12:10Z

Quiltgabi:

===Fertigstellung===

J4.x:Updating from an existing version/de

2023-08-26T11:14:57Z

Quiltgabi: Created page with "Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update."

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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.

===Completion===

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

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/28/de

2023-08-26T11:14:49Z

Quiltgabi: Created page with "Wenn das Update gestartet ist, erscheint ein Fortschrittsbalken für das Joomla Update."

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

J4.x:Updating from an existing version/de

2023-08-26T11:12:21Z

Quiltgabi:

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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]]

<span lang="en" dir="ltr" class="mw-content-ltr">Once the update starts a progress bar will appear as Joomla is updated.</span>

===Completion===

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

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/26/de

2023-08-26T11:12:16Z

Quiltgabi:

===Update Fortschritt===

J4.x:Updating from an existing version/de

2023-08-26T11:12:03Z

Quiltgabi: Created page with "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"."

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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 Progress===
[[File:j4x_joomla_update_progress-en.png|border|800px]]

<span lang="en" dir="ltr" class="mw-content-ltr">Once the update starts a progress bar will appear as Joomla is updated.</span>

===Completion===

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

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/25/de

2023-08-26T11:12:02Z

Quiltgabi: Created page with "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"."

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".

J4.x:Updating from an existing version/de

2023-08-26T11:08:15Z

Quiltgabi:

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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]]

<span lang="en" dir="ltr" class="mw-content-ltr">Click the checkbox to confirm you have made a backup and checked extensions are compatible then select the ''Start Update''.</span>

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

<span lang="en" dir="ltr" class="mw-content-ltr">Once the update starts a progress bar will appear as Joomla is updated.</span>

===Completion===

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

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/23/de

2023-08-26T11:08:12Z

Quiltgabi:

===Bestätige das Update===

J4.x:Updating from an existing version/de

2023-08-26T11:08:03Z

Quiltgabi: Created page with "Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update"."

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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".

===Confirming the Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

<span lang="en" dir="ltr" class="mw-content-ltr">Click the checkbox to confirm you have made a backup and checked extensions are compatible then select the ''Start Update''.</span>

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

<span lang="en" dir="ltr" class="mw-content-ltr">Once the update starts a progress bar will appear as Joomla is updated.</span>

===Completion===

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

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/22/de

2023-08-26T11:07:54Z

Quiltgabi: Created page with "Wenn du den Vor-Update Check überprüft und zufrieden bist, klicke "Update"."

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

J4.x:Updating from an existing version/de

2023-08-26T11:06:13Z

Quiltgabi: Created page with "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 Serv..."

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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.

<div lang="en" dir="ltr" class="mw-content-ltr">
When you have reviewed the Pre-Update Check and are happy, select ''Update''.
</div>

===Confirming the Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

<span lang="en" dir="ltr" class="mw-content-ltr">Click the checkbox to confirm you have made a backup and checked extensions are compatible then select the ''Start Update''.</span>

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

<span lang="en" dir="ltr" class="mw-content-ltr">Once the update starts a progress bar will appear as Joomla is updated.</span>

===Completion===

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

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/21/de

2023-08-26T11:06:12Z

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.

J4.x:Updating from an existing version/de

2023-08-26T10:59:29Z

Quiltgabi: Created page with "Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast."

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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.

<div lang="en" dir="ltr" class="mw-content-ltr">
There is a link below the update button. In most cases you can ignore this link. It provides an option to manually upload the update files if your server is behind a firewall or otherwise unable to contact the Joomla update servers.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When you have reviewed the Pre-Update Check and are happy, select ''Update''.
</div>

===Confirming the Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

<span lang="en" dir="ltr" class="mw-content-ltr">Click the checkbox to confirm you have made a backup and checked extensions are compatible then select the ''Start Update''.</span>

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

<span lang="en" dir="ltr" class="mw-content-ltr">Once the update starts a progress bar will appear as Joomla is updated.</span>

===Completion===

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

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/20/de

2023-08-26T10:59:27Z

Quiltgabi: Created page with "Beachte, dass du unbedingt ein Backup machen solltest, falls du das noch nicht gemacht hast."

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

J4.x:Updating from an existing version/de

2023-08-26T10:56:19Z

Quiltgabi: Created page with "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 ga..."

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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.

<div lang="en" dir="ltr" class="mw-content-ltr">
''Note the reminder that you are strongly advised to take a backup if you haven't already!''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There is a link below the update button. In most cases you can ignore this link. It provides an option to manually upload the update files if your server is behind a firewall or otherwise unable to contact the Joomla update servers.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When you have reviewed the Pre-Update Check and are happy, select ''Update''.
</div>

===Confirming the Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

<span lang="en" dir="ltr" class="mw-content-ltr">Click the checkbox to confirm you have made a backup and checked extensions are compatible then select the ''Start Update''.</span>

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

<span lang="en" dir="ltr" class="mw-content-ltr">Once the update starts a progress bar will appear as Joomla is updated.</span>

===Completion===

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

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/19/de

2023-08-26T10:56:15Z

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.

J4.x:Updating from an existing version/de

2023-08-26T10:50:40Z

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

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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.

<div lang="en" dir="ltr" class="mw-content-ltr">
It is not uncommon to see warnings for ''Recommended Settings'' as these are often server specific and hosting related - it is likely they existed when you installed Joomla and most likely won't prevent the update from happening.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
''Note the reminder that you are strongly advised to take a backup if you haven't already!''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There is a link below the update button. In most cases you can ignore this link. It provides an option to manually upload the update files if your server is behind a firewall or otherwise unable to contact the Joomla update servers.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When you have reviewed the Pre-Update Check and are happy, select ''Update''.
</div>

===Confirming the Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

<span lang="en" dir="ltr" class="mw-content-ltr">Click the checkbox to confirm you have made a backup and checked extensions are compatible then select the ''Start Update''.</span>

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

<span lang="en" dir="ltr" class="mw-content-ltr">Once the update starts a progress bar will appear as Joomla is updated.</span>

===Completion===

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

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/18/de

2023-08-26T10:50:34Z

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

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

J4.x:Updating from an existing version/de

2023-08-26T10:37:41Z

Quiltgabi: Created page with "Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel 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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[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.

<div lang="en" dir="ltr" class="mw-content-ltr">
Pay careful attention to these and take action to rectify any issues highlighted before updating. You may need to double check extensions and update them first.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It is not uncommon to see warnings for ''Recommended Settings'' as these are often server specific and hosting related - it is likely they existed when you installed Joomla and most likely won't prevent the update from happening.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
''Note the reminder that you are strongly advised to take a backup if you haven't already!''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There is a link below the update button. In most cases you can ignore this link. It provides an option to manually upload the update files if your server is behind a firewall or otherwise unable to contact the Joomla update servers.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When you have reviewed the Pre-Update Check and are happy, select ''Update''.
</div>

===Confirming the Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

<span lang="en" dir="ltr" class="mw-content-ltr">Click the checkbox to confirm you have made a backup and checked extensions are compatible then select the ''Start Update''.</span>

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

<span lang="en" dir="ltr" class="mw-content-ltr">Once the update starts a progress bar will appear as Joomla is updated.</span>

===Completion===

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

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/17/de

2023-08-26T10:37:36Z

Die Joomla Update Komponente informiert Dich mit einem Vor-Update Check ob dein Server, deine Einstellungen und installierten Erweiterungen mit dem Update kompatibel sind.

J4.x:Updating from an existing version/de

2023-08-26T10:25:45Z

Quiltgabi:

<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>

<div class="mw-translate-fuzzy">
==Carrying out the Update==
</div>
[[File:j4x_joomla_pre_update_check-en.png|border|800px]]
{{-}}
<div lang="en" dir="ltr" class="mw-content-ltr">
At the Joomla Update Component you will be presented with a Pre-Update Check that provides you with information about the readiness of your server, settings and installed extensions for the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
Pay careful attention to these and take action to rectify any issues highlighted before updating. You may need to double check extensions and update them first.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
It is not uncommon to see warnings for ''Recommended Settings'' as these are often server specific and hosting related - it is likely they existed when you installed Joomla and most likely won't prevent the update from happening.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
''Note the reminder that you are strongly advised to take a backup if you haven't already!''
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
There is a link below the update button. In most cases you can ignore this link. It provides an option to manually upload the update files if your server is behind a firewall or otherwise unable to contact the Joomla update servers.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
When you have reviewed the Pre-Update Check and are happy, select ''Update''.
</div>

===Confirming the Update===
[[File:j4x_joomla_start_update-en.png|border|800px]]

<span lang="en" dir="ltr" class="mw-content-ltr">Click the checkbox to confirm you have made a backup and checked extensions are compatible then select the ''Start Update''.</span>

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

<span lang="en" dir="ltr" class="mw-content-ltr">Once the update starts a progress bar will appear as Joomla is updated.</span>

===Completion===

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

<span lang="en" dir="ltr" class="mw-content-ltr">When the progress bar reaches 100% a notification will confirm that your site has been updated and the version number. The version number will also update in the top toolbar next to the site name.</span>

<div lang="en" dir="ltr" class="mw-content-ltr">
Click the ''Back'' button and you will be returned to the Joomla Update Component where it is possible to check for updates again.
</div>

==Post Update Checks==

<div lang="en" dir="ltr" class="mw-content-ltr">
Once the update is complete you should carry out some checks to make sure everything went as expected, that no errors are present and that there have been no changes that require further action.
</div>

===Frontend Check===
<div lang="en" dir="ltr" class="mw-content-ltr">
Go to the front end of the website and check it is working and displaying as it did prior to the update.
</div>

<div lang="en" dir="ltr" class="mw-content-ltr">
As a matter of course, clear your browser cache as this will load any changes to style sheets and scripts.
</div>

===System Checks===

<span lang="en" dir="ltr" class="mw-content-ltr">Joomla makes it easy to do a "health" check. From the sidebar menu click ''System'' to be taken to the System Dashboard. This gives you an overview of the current status of your Joomla site.</span>

[[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:'''
<div lang="en" dir="ltr" class="mw-content-ltr">
It is recommended that you follow these steps when updating a production site:
</div>
<div lang="en" dir="ltr" class="mw-content-ltr">
# Back up your site before updating to a new version. If something goes wrong during the update process, you can easily restore your site to the earlier version.
</div>
<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/91/de

2023-08-26T10:25:41Z

Quiltgabi:

===Hochladen abschließen===

Adding an image to an article/de

2023-08-26T10:22:07Z

Quiltgabi:

<noinclude><languages /></noinclude>
== Introduction ==

How best to add images to an article depends on which version of Joomla and which editor are in use. This article has illustrations for Joomla 4, with notes on differences in Joomla 3, and TinyMCE the Joomla default editor. To get started, open an article for editing:

*'''Select''' {{rarr|Content,Articles}} in the Administrator menu.
* '''Select''' the title of the article you wish to edit

After inserting the article text, place the cursor at the location where the image should appear.

== Adding a local image ==

If the image is located in the images folder of your Joomla installation you should insert the image using the {{rarr|CMS Content, Media}} button In the TinyMCE edit toolbar (In Joomla 3: Select the Image button):

[[File:adding-an-image-to-an-article-cms-content-media.png|800|Adding an image]]

In the popup window, navigate to the image you want to use and click to select it. On selection a form will appear prompting for additional data. In Joomla 4 the form is to the left. In joomla 3 the form is at the bottom (scroll down):

[[File:adding-an-image-to-an-article-selected-image.png|800|Selecting an image]]

#Wähle die gewünschten Bildeinstellungen: Üblicherweise solltest du unbedingt das Feld Bildbeschreibung (Alt Text) ausfüllen. Die anderen Felder werden benutzt um das Aussehen des Bildes mit der eigenen css festzulegen.
*"Bild Beschreibung": Dies wird als "alt"-Eigenschaft des Bildes dargestellt, eine wichtige Funktion für Barrierefreiheit und die Erfüllung der Web-Standards. In Joomla 3 wurde es als '"Bildtitel"' bezeichnet.
*"Bild Beschreibung": Wenn ein Bild ohne Steuerelemente benutzt wird, können hier einige benutzerdefinierte Klassen eingefügt werden. Z.B. in Joomla 4 "float-end ms-2 mb-1" richtet das Bild rechts aus, umflossen vom Text mit einem Rand links und unten, damit der Text nicht das Bild berührt. In Joomla 3 entspricht das dem Stil "pull-right".
*"Figure Class" : wenn ein Steuerelement festgelegt wurde, könnte eine Ausrichtungs Klasse zur Darstellung hinzugefügt werden. Dies ist ein html tag, der den img tag umschließt. Beachte das in Cassiopeia Ränder über das Template Style Sheet geregelt werden.
#*'''Bildbeschriftung''': Wird unter dem Bild als Bild Titel angezeigt.
'''In Joomla 3'''
#*'''Ausrichtung''': Bildausrichtung festlegen. Standartmäßig ist es auf '''Nicht definiert''' gesetzt.
#*'''Beschriftung Klasse''': Fügt die eingegebene Klasse an das ''figcaption'' Element an.

#Klick den ''Einfügen Media'' Button, um das Bild einzufügen. Das Bild-Einfügefenster wird geschlossen und das Bild erscheint im Editor. Oder klick den "Abbrechen" Button um das Bild-Einfügefenster zu verlassen.

"Tip:" wähle den Umschalt Editor Button um die hinzugefügten Bild- und Beschriftungsstile zu sehen.

=== Using Drag and Drop for Local images ===

In both Joomla 4 and Joomla 3 you can drag an image from the desktop or a file browser directly into the article text and the image will be uploaded to the media folder and placed in the article. The only snag is that all such uploaded images will be placed in the same media folder. The location of the Images Directory used for upload and whether this feature is enabled (On by default) are set in the TinyMCE configuration Options.

== Adding a remote image ==

If the image you wish to use is not in the images folder of your Joomla installation a slightly different procedure is needed.

*'''Select''' {{rarr|Insert,Image}} from the TinyMCE toolbar to open a dialog box. In Jooml 3, use the Image icon and the same dialog as used for local images.
*'''Insert''' the image url in the Source field.
*'''Fill out''' the other fields as required.
*'''Advanced''' provides some formatting options applied as in-line styles. Experiment with 1rem, 2, groove. (This feature is incomplete)

[[File:adding-an-image-to-an-article-insert-edit-image.png|center|border|Data for a remote image]]

=== Using Drag and Drop for Remote images ===

You can drag and drop an image from a remote web site directly into your article text. But be aware that this may also copy the image container html with class statements not valid for your site.

== Bilder einfügen mit dem "Bild-Einfügefenster" ==

Du kannst zum Hochladen neuer Bilder das Medienfenster benutzen (das Bildfenster in Joomla 3)
Öffne zuerst den Media Browser und gehe zu dem Ordner, in dem du die neuen Bilder für den aktuellen Beitrag speichern willst.
Im Medien Bildschirm wähle den Hochladen Button oben links (in Joomla 3 scroll runter zum Rand zum Durchsuchen Button), um den Dateibrowser zu öffnen.
#Wähle die Bilder aus, die Du hochladen willst. Klicke auf "Öffnen" im Datei-Browser um die Auswahl zu bestätigen. Hinweis: Stil und Layout des Datei-Browsers hängt davon ab, welchen Browser und welches Betriebssystem Du verwendest.
In Joomla 4 wird sofort hochgeladen, in Joomla 3 wähle den Hochladen starten Button.
#Die ausgewählten Datei(en) erscheinen in alphabetischer Reihenfolge im Medien/Bild Fenster.
#*Wenn die Datei fertig hochgeladen ist, erscheint eine grüne Bestätigungsnachricht oben im Fenster.
#Du kannst nun das hochgeladene Bild wie zuvor beschrieben auswählen und einfügen.

<noinclude>
[[Category:Tutorials/de|Tutorials]]
[[Category:Article Management/de|Beitragsverwaltung]]
[[Category:Beginners/de|Einsteiger]]
</noinclude>

Translations:Adding an image to an article/18/de

2023-08-26T10:22:02Z

Quiltgabi:

Du kannst zum Hochladen neuer Bilder das Medienfenster benutzen (das Bildfenster in Joomla 3)

Adding an image to an article/de

2023-08-26T10:19:10Z

Quiltgabi:

<noinclude><languages /></noinclude>
== Introduction ==

How best to add images to an article depends on which version of Joomla and which editor are in use. This article has illustrations for Joomla 4, with notes on differences in Joomla 3, and TinyMCE the Joomla default editor. To get started, open an article for editing:

*'''Select''' {{rarr|Content,Articles}} in the Administrator menu.
* '''Select''' the title of the article you wish to edit

After inserting the article text, place the cursor at the location where the image should appear.

== Adding a local image ==

If the image is located in the images folder of your Joomla installation you should insert the image using the {{rarr|CMS Content, Media}} button In the TinyMCE edit toolbar (In Joomla 3: Select the Image button):

[[File:adding-an-image-to-an-article-cms-content-media.png|800|Adding an image]]

In the popup window, navigate to the image you want to use and click to select it. On selection a form will appear prompting for additional data. In Joomla 4 the form is to the left. In joomla 3 the form is at the bottom (scroll down):

[[File:adding-an-image-to-an-article-selected-image.png|800|Selecting an image]]

#Wähle die gewünschten Bildeinstellungen: Üblicherweise solltest du unbedingt das Feld Bildbeschreibung (Alt Text) ausfüllen. Die anderen Felder werden benutzt um das Aussehen des Bildes mit der eigenen css festzulegen.
*"Bild Beschreibung": Dies wird als "alt"-Eigenschaft des Bildes dargestellt, eine wichtige Funktion für Barrierefreiheit und die Erfüllung der Web-Standards. In Joomla 3 wurde es als '"Bildtitel"' bezeichnet.
*"Bild Beschreibung": Wenn ein Bild ohne Steuerelemente benutzt wird, können hier einige benutzerdefinierte Klassen eingefügt werden. Z.B. in Joomla 4 "float-end ms-2 mb-1" richtet das Bild rechts aus, umflossen vom Text mit einem Rand links und unten, damit der Text nicht das Bild berührt. In Joomla 3 entspricht das dem Stil "pull-right".
*"Figure Class" : wenn ein Steuerelement festgelegt wurde, könnte eine Ausrichtungs Klasse zur Darstellung hinzugefügt werden. Dies ist ein html tag, der den img tag umschließt. Beachte das in Cassiopeia Ränder über das Template Style Sheet geregelt werden.
#*'''Bildbeschriftung''': Wird unter dem Bild als Bild Titel angezeigt.
'''In Joomla 3'''
#*'''Ausrichtung''': Bildausrichtung festlegen. Standartmäßig ist es auf '''Nicht definiert''' gesetzt.
#*'''Beschriftung Klasse''': Fügt die eingegebene Klasse an das ''figcaption'' Element an.

#Klick den ''Einfügen Media'' Button, um das Bild einzufügen. Das Bild-Einfügefenster wird geschlossen und das Bild erscheint im Editor. Oder klick den "Abbrechen" Button um das Bild-Einfügefenster zu verlassen.

"Tip:" wähle den Umschalt Editor Button um die hinzugefügten Bild- und Beschriftungsstile zu sehen.

=== Using Drag and Drop for Local images ===

In both Joomla 4 and Joomla 3 you can drag an image from the desktop or a file browser directly into the article text and the image will be uploaded to the media folder and placed in the article. The only snag is that all such uploaded images will be placed in the same media folder. The location of the Images Directory used for upload and whether this feature is enabled (On by default) are set in the TinyMCE configuration Options.

== Adding a remote image ==

If the image you wish to use is not in the images folder of your Joomla installation a slightly different procedure is needed.

*'''Select''' {{rarr|Insert,Image}} from the TinyMCE toolbar to open a dialog box. In Jooml 3, use the Image icon and the same dialog as used for local images.
*'''Insert''' the image url in the Source field.
*'''Fill out''' the other fields as required.
*'''Advanced''' provides some formatting options applied as in-line styles. Experiment with 1rem, 2, groove. (This feature is incomplete)

[[File:adding-an-image-to-an-article-insert-edit-image.png|center|border|Data for a remote image]]

=== Using Drag and Drop for Remote images ===

You can drag and drop an image from a remote web site directly into your article text. But be aware that this may also copy the image container html with class statements not valid for your site.

== Bilder einfügen mit dem "Bild-Einfügefenster" ==

<div class="mw-translate-fuzzy">
Du kannst auch Bilder einfügen, indem Du den "Upload-Bereich" im "Bild-Einfügefenster" benutzt.
</div>
Öffne zuerst den Media Browser und gehe zu dem Ordner, in dem du die neuen Bilder für den aktuellen Beitrag speichern willst.
Im Medien Bildschirm wähle den Hochladen Button oben links (in Joomla 3 scroll runter zum Rand zum Durchsuchen Button), um den Dateibrowser zu öffnen.
#Wähle die Bilder aus, die Du hochladen willst. Klicke auf "Öffnen" im Datei-Browser um die Auswahl zu bestätigen. Hinweis: Stil und Layout des Datei-Browsers hängt davon ab, welchen Browser und welches Betriebssystem Du verwendest.
In Joomla 4 wird sofort hochgeladen, in Joomla 3 wähle den Hochladen starten Button.
#Die ausgewählten Datei(en) erscheinen in alphabetischer Reihenfolge im Medien/Bild Fenster.
#*Wenn die Datei fertig hochgeladen ist, erscheint eine grüne Bestätigungsnachricht oben im Fenster.
#Du kannst nun das hochgeladene Bild wie zuvor beschrieben auswählen und einfügen.

<noinclude>
[[Category:Tutorials/de|Tutorials]]
[[Category:Article Management/de|Beitragsverwaltung]]
[[Category:Beginners/de|Einsteiger]]
</noinclude>

Adding an image to an article/de

2023-08-26T10:18:30Z

Quiltgabi:

<noinclude><languages /></noinclude>
== Introduction ==

How best to add images to an article depends on which version of Joomla and which editor are in use. This article has illustrations for Joomla 4, with notes on differences in Joomla 3, and TinyMCE the Joomla default editor. To get started, open an article for editing:

*'''Select''' {{rarr|Content,Articles}} in the Administrator menu.
* '''Select''' the title of the article you wish to edit

After inserting the article text, place the cursor at the location where the image should appear.

== Adding a local image ==

If the image is located in the images folder of your Joomla installation you should insert the image using the {{rarr|CMS Content, Media}} button In the TinyMCE edit toolbar (In Joomla 3: Select the Image button):

[[File:adding-an-image-to-an-article-cms-content-media.png|800|Adding an image]]

In the popup window, navigate to the image you want to use and click to select it. On selection a form will appear prompting for additional data. In Joomla 4 the form is to the left. In joomla 3 the form is at the bottom (scroll down):

[[File:adding-an-image-to-an-article-selected-image.png|800|Selecting an image]]

#Wähle die gewünschten Bildeinstellungen: Üblicherweise solltest du unbedingt das Feld Bildbeschreibung (Alt Text) ausfüllen. Die anderen Felder werden benutzt um das Aussehen des Bildes mit der eigenen css festzulegen.
*"Bild Beschreibung": Dies wird als "alt"-Eigenschaft des Bildes dargestellt, eine wichtige Funktion für Barrierefreiheit und die Erfüllung der Web-Standards. In Joomla 3 wurde es als '"Bildtitel"' bezeichnet.
*"Bild Beschreibung": Wenn ein Bild ohne Steuerelemente benutzt wird, können hier einige benutzerdefinierte Klassen eingefügt werden. Z.B. in Joomla 4 "float-end ms-2 mb-1" richtet das Bild rechts aus, umflossen vom Text mit einem Rand links und unten, damit der Text nicht das Bild berührt. In Joomla 3 entspricht das dem Stil "pull-right".
*"Figure Class" : wenn ein Steuerelement festgelegt wurde, könnte eine Ausrichtungs Klasse zur Darstellung hinzugefügt werden. Dies ist ein html tag, der den img tag umschließt. Beachte das in Cassiopeia Ränder über das Template Style Sheet geregelt werden.
#*'''Bildbeschriftung''': Wird unter dem Bild als Bild Titel angezeigt.
'''In Joomla 3'''
#*'''Ausrichtung''': Bildausrichtung festlegen. Standartmäßig ist es auf '''Nicht definiert''' gesetzt.
#*'''Beschriftung Klasse''': Fügt die eingegebene Klasse an das ''figcaption'' Element an.

#Klick den ''Einfügen Media'' Button, um das Bild einzufügen. Das Bild-Einfügefenster wird geschlossen und das Bild erscheint im Editor. Oder klick den "Abbrechen" Button um das Bild-Einfügefenster zu verlassen.

"Tip:" wähle den Umschalt Editor Button um die hinzugefügten Bild- und Beschriftungsstile zu sehen.

=== Using Drag and Drop for Local images ===

In both Joomla 4 and Joomla 3 you can drag an image from the desktop or a file browser directly into the article text and the image will be uploaded to the media folder and placed in the article. The only snag is that all such uploaded images will be placed in the same media folder. The location of the Images Directory used for upload and whether this feature is enabled (On by default) are set in the TinyMCE configuration Options.

== Adding a remote image ==

If the image you wish to use is not in the images folder of your Joomla installation a slightly different procedure is needed.

*'''Select''' {{rarr|Insert,Image}} from the TinyMCE toolbar to open a dialog box. In Jooml 3, use the Image icon and the same dialog as used for local images.
*'''Insert''' the image url in the Source field.
*'''Fill out''' the other fields as required.
*'''Advanced''' provides some formatting options applied as in-line styles. Experiment with 1rem, 2, groove. (This feature is incomplete)

[[File:adding-an-image-to-an-article-insert-edit-image.png|center|border|Data for a remote image]]

=== Using Drag and Drop for Remote images ===

You can drag and drop an image from a remote web site directly into your article text. But be aware that this may also copy the image container html with class statements not valid for your site.

== Bilder einfügen mit dem "Bild-Einfügefenster" ==

<div class="mw-translate-fuzzy">
Du kannst auch Bilder einfügen, indem Du den "Upload-Bereich" im "Bild-Einfügefenster" benutzt.
</div>
Öffne zuerst den Media Browser und gehe zu dem Ordner, in dem du die neuen Bilder für den aktuellen Beitrag speichern willst.
Im Medien Bildschirm wähle den Hochladen Button oben links (in Joomla 3 scroll runter zum Rand zum Durchsuchen Button), um den Dateibrowser zu öffnen.
#Wähle die Bilder aus, die Du hochladen willst. Klicke auf "Öffnen" im Datei-Browser um die Auswahl zu bestätigen. Hinweis: Stil und Layout des Datei-Browsers hängt davon ab, welchen Browser und welches Betriebssystem Du verwendest.
In Joomla 4 wird sofort hochgeladen, in Joomla 3 wähle den Hochladen starten Button.
#Die ausgewählten Datei(en) erscheinen in alphabetischer Reihenfolge im Medien/Bild Fenster.
#*Wenn die Datei fertig hochgeladen ist, erscheint eine grüne Bestätigungsnachricht oben im Fenster.
<div class="mw-translate-fuzzy">
#Du kannst nun das hochgeladene Bild wie zuvor beschrieben auswählen und einfügen.
</div>

<noinclude>
[[Category:Tutorials/de|Tutorials]]
[[Category:Article Management/de|Beitragsverwaltung]]
[[Category:Beginners/de|Einsteiger]]
</noinclude>

Translations:Adding an image to an article/24/de

2023-08-26T10:18:30Z

Quiltgabi:

#*Wenn die Datei fertig hochgeladen ist, erscheint eine grüne Bestätigungsnachricht oben im Fenster.

Adding an image to an article/de

2023-08-26T10:18:12Z

Quiltgabi:

<noinclude><languages /></noinclude>
== Introduction ==

How best to add images to an article depends on which version of Joomla and which editor are in use. This article has illustrations for Joomla 4, with notes on differences in Joomla 3, and TinyMCE the Joomla default editor. To get started, open an article for editing:

*'''Select''' {{rarr|Content,Articles}} in the Administrator menu.
* '''Select''' the title of the article you wish to edit

After inserting the article text, place the cursor at the location where the image should appear.

== Adding a local image ==

If the image is located in the images folder of your Joomla installation you should insert the image using the {{rarr|CMS Content, Media}} button In the TinyMCE edit toolbar (In Joomla 3: Select the Image button):

[[File:adding-an-image-to-an-article-cms-content-media.png|800|Adding an image]]

In the popup window, navigate to the image you want to use and click to select it. On selection a form will appear prompting for additional data. In Joomla 4 the form is to the left. In joomla 3 the form is at the bottom (scroll down):

[[File:adding-an-image-to-an-article-selected-image.png|800|Selecting an image]]

#Wähle die gewünschten Bildeinstellungen: Üblicherweise solltest du unbedingt das Feld Bildbeschreibung (Alt Text) ausfüllen. Die anderen Felder werden benutzt um das Aussehen des Bildes mit der eigenen css festzulegen.
*"Bild Beschreibung": Dies wird als "alt"-Eigenschaft des Bildes dargestellt, eine wichtige Funktion für Barrierefreiheit und die Erfüllung der Web-Standards. In Joomla 3 wurde es als '"Bildtitel"' bezeichnet.
*"Bild Beschreibung": Wenn ein Bild ohne Steuerelemente benutzt wird, können hier einige benutzerdefinierte Klassen eingefügt werden. Z.B. in Joomla 4 "float-end ms-2 mb-1" richtet das Bild rechts aus, umflossen vom Text mit einem Rand links und unten, damit der Text nicht das Bild berührt. In Joomla 3 entspricht das dem Stil "pull-right".
*"Figure Class" : wenn ein Steuerelement festgelegt wurde, könnte eine Ausrichtungs Klasse zur Darstellung hinzugefügt werden. Dies ist ein html tag, der den img tag umschließt. Beachte das in Cassiopeia Ränder über das Template Style Sheet geregelt werden.
#*'''Bildbeschriftung''': Wird unter dem Bild als Bild Titel angezeigt.
'''In Joomla 3'''
#*'''Ausrichtung''': Bildausrichtung festlegen. Standartmäßig ist es auf '''Nicht definiert''' gesetzt.
#*'''Beschriftung Klasse''': Fügt die eingegebene Klasse an das ''figcaption'' Element an.

#Klick den ''Einfügen Media'' Button, um das Bild einzufügen. Das Bild-Einfügefenster wird geschlossen und das Bild erscheint im Editor. Oder klick den "Abbrechen" Button um das Bild-Einfügefenster zu verlassen.

"Tip:" wähle den Umschalt Editor Button um die hinzugefügten Bild- und Beschriftungsstile zu sehen.

=== Using Drag and Drop for Local images ===

In both Joomla 4 and Joomla 3 you can drag an image from the desktop or a file browser directly into the article text and the image will be uploaded to the media folder and placed in the article. The only snag is that all such uploaded images will be placed in the same media folder. The location of the Images Directory used for upload and whether this feature is enabled (On by default) are set in the TinyMCE configuration Options.

== Adding a remote image ==

If the image you wish to use is not in the images folder of your Joomla installation a slightly different procedure is needed.

*'''Select''' {{rarr|Insert,Image}} from the TinyMCE toolbar to open a dialog box. In Jooml 3, use the Image icon and the same dialog as used for local images.
*'''Insert''' the image url in the Source field.
*'''Fill out''' the other fields as required.
*'''Advanced''' provides some formatting options applied as in-line styles. Experiment with 1rem, 2, groove. (This feature is incomplete)

[[File:adding-an-image-to-an-article-insert-edit-image.png|center|border|Data for a remote image]]

=== Using Drag and Drop for Remote images ===

You can drag and drop an image from a remote web site directly into your article text. But be aware that this may also copy the image container html with class statements not valid for your site.

== Bilder einfügen mit dem "Bild-Einfügefenster" ==

<div class="mw-translate-fuzzy">
Du kannst auch Bilder einfügen, indem Du den "Upload-Bereich" im "Bild-Einfügefenster" benutzt.
</div>
Öffne zuerst den Media Browser und gehe zu dem Ordner, in dem du die neuen Bilder für den aktuellen Beitrag speichern willst.
Im Medien Bildschirm wähle den Hochladen Button oben links (in Joomla 3 scroll runter zum Rand zum Durchsuchen Button), um den Dateibrowser zu öffnen.
#Wähle die Bilder aus, die Du hochladen willst. Klicke auf "Öffnen" im Datei-Browser um die Auswahl zu bestätigen. Hinweis: Stil und Layout des Datei-Browsers hängt davon ab, welchen Browser und welches Betriebssystem Du verwendest.
In Joomla 4 wird sofort hochgeladen, in Joomla 3 wähle den Hochladen starten Button.
#Die ausgewählten Datei(en) erscheinen in alphabetischer Reihenfolge im Medien/Bild Fenster.
<div class="mw-translate-fuzzy">
#*Wenn die Datei hochgeladen ist erscheint eine grüne Nachricht zur Bestätigung oben im Fenster.
</div>
<div class="mw-translate-fuzzy">
#Du kannst nun das hochgeladene Bild wie zuvor beschrieben auswählen und einfügen.
</div>

<noinclude>
[[Category:Tutorials/de|Tutorials]]
[[Category:Article Management/de|Beitragsverwaltung]]
[[Category:Beginners/de|Einsteiger]]
</noinclude>

Translations:Adding an image to an article/23/de

2023-08-26T10:18:10Z

Quiltgabi:

#Die ausgewählten Datei(en) erscheinen in alphabetischer Reihenfolge im Medien/Bild Fenster.

Adding an image to an article/de

2023-08-26T10:15:26Z

Quiltgabi:

<noinclude><languages /></noinclude>
== Introduction ==

How best to add images to an article depends on which version of Joomla and which editor are in use. This article has illustrations for Joomla 4, with notes on differences in Joomla 3, and TinyMCE the Joomla default editor. To get started, open an article for editing:

*'''Select''' {{rarr|Content,Articles}} in the Administrator menu.
* '''Select''' the title of the article you wish to edit

After inserting the article text, place the cursor at the location where the image should appear.

== Adding a local image ==

If the image is located in the images folder of your Joomla installation you should insert the image using the {{rarr|CMS Content, Media}} button In the TinyMCE edit toolbar (In Joomla 3: Select the Image button):

[[File:adding-an-image-to-an-article-cms-content-media.png|800|Adding an image]]

In the popup window, navigate to the image you want to use and click to select it. On selection a form will appear prompting for additional data. In Joomla 4 the form is to the left. In joomla 3 the form is at the bottom (scroll down):

[[File:adding-an-image-to-an-article-selected-image.png|800|Selecting an image]]

#Wähle die gewünschten Bildeinstellungen: Üblicherweise solltest du unbedingt das Feld Bildbeschreibung (Alt Text) ausfüllen. Die anderen Felder werden benutzt um das Aussehen des Bildes mit der eigenen css festzulegen.
*"Bild Beschreibung": Dies wird als "alt"-Eigenschaft des Bildes dargestellt, eine wichtige Funktion für Barrierefreiheit und die Erfüllung der Web-Standards. In Joomla 3 wurde es als '"Bildtitel"' bezeichnet.
*"Bild Beschreibung": Wenn ein Bild ohne Steuerelemente benutzt wird, können hier einige benutzerdefinierte Klassen eingefügt werden. Z.B. in Joomla 4 "float-end ms-2 mb-1" richtet das Bild rechts aus, umflossen vom Text mit einem Rand links und unten, damit der Text nicht das Bild berührt. In Joomla 3 entspricht das dem Stil "pull-right".
*"Figure Class" : wenn ein Steuerelement festgelegt wurde, könnte eine Ausrichtungs Klasse zur Darstellung hinzugefügt werden. Dies ist ein html tag, der den img tag umschließt. Beachte das in Cassiopeia Ränder über das Template Style Sheet geregelt werden.
#*'''Bildbeschriftung''': Wird unter dem Bild als Bild Titel angezeigt.
'''In Joomla 3'''
#*'''Ausrichtung''': Bildausrichtung festlegen. Standartmäßig ist es auf '''Nicht definiert''' gesetzt.
#*'''Beschriftung Klasse''': Fügt die eingegebene Klasse an das ''figcaption'' Element an.

#Klick den ''Einfügen Media'' Button, um das Bild einzufügen. Das Bild-Einfügefenster wird geschlossen und das Bild erscheint im Editor. Oder klick den "Abbrechen" Button um das Bild-Einfügefenster zu verlassen.

"Tip:" wähle den Umschalt Editor Button um die hinzugefügten Bild- und Beschriftungsstile zu sehen.

=== Using Drag and Drop for Local images ===

In both Joomla 4 and Joomla 3 you can drag an image from the desktop or a file browser directly into the article text and the image will be uploaded to the media folder and placed in the article. The only snag is that all such uploaded images will be placed in the same media folder. The location of the Images Directory used for upload and whether this feature is enabled (On by default) are set in the TinyMCE configuration Options.

== Adding a remote image ==

If the image you wish to use is not in the images folder of your Joomla installation a slightly different procedure is needed.

*'''Select''' {{rarr|Insert,Image}} from the TinyMCE toolbar to open a dialog box. In Jooml 3, use the Image icon and the same dialog as used for local images.
*'''Insert''' the image url in the Source field.
*'''Fill out''' the other fields as required.
*'''Advanced''' provides some formatting options applied as in-line styles. Experiment with 1rem, 2, groove. (This feature is incomplete)

[[File:adding-an-image-to-an-article-insert-edit-image.png|center|border|Data for a remote image]]

=== Using Drag and Drop for Remote images ===

You can drag and drop an image from a remote web site directly into your article text. But be aware that this may also copy the image container html with class statements not valid for your site.

== Bilder einfügen mit dem "Bild-Einfügefenster" ==

<div class="mw-translate-fuzzy">
Du kannst auch Bilder einfügen, indem Du den "Upload-Bereich" im "Bild-Einfügefenster" benutzt.
</div>
Öffne zuerst den Media Browser und gehe zu dem Ordner, in dem du die neuen Bilder für den aktuellen Beitrag speichern willst.
Im Medien Bildschirm wähle den Hochladen Button oben links (in Joomla 3 scroll runter zum Rand zum Durchsuchen Button), um den Dateibrowser zu öffnen.
#Wähle die Bilder aus, die Du hochladen willst. Klicke auf "Öffnen" im Datei-Browser um die Auswahl zu bestätigen. Hinweis: Stil und Layout des Datei-Browsers hängt davon ab, welchen Browser und welches Betriebssystem Du verwendest.
In Joomla 4 wird sofort hochgeladen, in Joomla 3 wähle den Hochladen starten Button.
#Die ausgewählten Datei(en) erscheinen in alphabetischer Reihenfolge auf dem Medien/Bild Bildschirm.
<div class="mw-translate-fuzzy">
#*Wenn die Datei hochgeladen ist erscheint eine grüne Nachricht zur Bestätigung oben im Fenster.
</div>
<div class="mw-translate-fuzzy">
#Du kannst nun das hochgeladene Bild wie zuvor beschrieben auswählen und einfügen.
</div>

<noinclude>
[[Category:Tutorials/de|Tutorials]]
[[Category:Article Management/de|Beitragsverwaltung]]
[[Category:Beginners/de|Einsteiger]]
</noinclude>

Translations:Adding an image to an article/23/de

2023-08-26T10:15:22Z

Quiltgabi:

#Die ausgewählten Datei(en) erscheinen in alphabetischer Reihenfolge auf dem Medien/Bild Bildschirm.

Adding an image to an article/de

2023-08-26T10:12:47Z

Quiltgabi:

<noinclude><languages /></noinclude>
== Introduction ==

How best to add images to an article depends on which version of Joomla and which editor are in use. This article has illustrations for Joomla 4, with notes on differences in Joomla 3, and TinyMCE the Joomla default editor. To get started, open an article for editing:

*'''Select''' {{rarr|Content,Articles}} in the Administrator menu.
* '''Select''' the title of the article you wish to edit

After inserting the article text, place the cursor at the location where the image should appear.

== Adding a local image ==

If the image is located in the images folder of your Joomla installation you should insert the image using the {{rarr|CMS Content, Media}} button In the TinyMCE edit toolbar (In Joomla 3: Select the Image button):

[[File:adding-an-image-to-an-article-cms-content-media.png|800|Adding an image]]

In the popup window, navigate to the image you want to use and click to select it. On selection a form will appear prompting for additional data. In Joomla 4 the form is to the left. In joomla 3 the form is at the bottom (scroll down):

[[File:adding-an-image-to-an-article-selected-image.png|800|Selecting an image]]

#Wähle die gewünschten Bildeinstellungen: Üblicherweise solltest du unbedingt das Feld Bildbeschreibung (Alt Text) ausfüllen. Die anderen Felder werden benutzt um das Aussehen des Bildes mit der eigenen css festzulegen.
*"Bild Beschreibung": Dies wird als "alt"-Eigenschaft des Bildes dargestellt, eine wichtige Funktion für Barrierefreiheit und die Erfüllung der Web-Standards. In Joomla 3 wurde es als '"Bildtitel"' bezeichnet.
*"Bild Beschreibung": Wenn ein Bild ohne Steuerelemente benutzt wird, können hier einige benutzerdefinierte Klassen eingefügt werden. Z.B. in Joomla 4 "float-end ms-2 mb-1" richtet das Bild rechts aus, umflossen vom Text mit einem Rand links und unten, damit der Text nicht das Bild berührt. In Joomla 3 entspricht das dem Stil "pull-right".
*"Figure Class" : wenn ein Steuerelement festgelegt wurde, könnte eine Ausrichtungs Klasse zur Darstellung hinzugefügt werden. Dies ist ein html tag, der den img tag umschließt. Beachte das in Cassiopeia Ränder über das Template Style Sheet geregelt werden.
#*'''Bildbeschriftung''': Wird unter dem Bild als Bild Titel angezeigt.
'''In Joomla 3'''
#*'''Ausrichtung''': Bildausrichtung festlegen. Standartmäßig ist es auf '''Nicht definiert''' gesetzt.
#*'''Beschriftung Klasse''': Fügt die eingegebene Klasse an das ''figcaption'' Element an.

#Klick den ''Einfügen Media'' Button, um das Bild einzufügen. Das Bild-Einfügefenster wird geschlossen und das Bild erscheint im Editor. Oder klick den "Abbrechen" Button um das Bild-Einfügefenster zu verlassen.

"Tip:" wähle den Umschalt Editor Button um die hinzugefügten Bild- und Beschriftungsstile zu sehen.

=== Using Drag and Drop for Local images ===

In both Joomla 4 and Joomla 3 you can drag an image from the desktop or a file browser directly into the article text and the image will be uploaded to the media folder and placed in the article. The only snag is that all such uploaded images will be placed in the same media folder. The location of the Images Directory used for upload and whether this feature is enabled (On by default) are set in the TinyMCE configuration Options.

== Adding a remote image ==

If the image you wish to use is not in the images folder of your Joomla installation a slightly different procedure is needed.

*'''Select''' {{rarr|Insert,Image}} from the TinyMCE toolbar to open a dialog box. In Jooml 3, use the Image icon and the same dialog as used for local images.
*'''Insert''' the image url in the Source field.
*'''Fill out''' the other fields as required.
*'''Advanced''' provides some formatting options applied as in-line styles. Experiment with 1rem, 2, groove. (This feature is incomplete)

[[File:adding-an-image-to-an-article-insert-edit-image.png|center|border|Data for a remote image]]

=== Using Drag and Drop for Remote images ===

You can drag and drop an image from a remote web site directly into your article text. But be aware that this may also copy the image container html with class statements not valid for your site.

== Bilder einfügen mit dem "Bild-Einfügefenster" ==

<div class="mw-translate-fuzzy">
Du kannst auch Bilder einfügen, indem Du den "Upload-Bereich" im "Bild-Einfügefenster" benutzt.
</div>
Öffne zuerst den Media Browser und gehe zu dem Ordner, in dem du die neuen Bilder für den aktuellen Beitrag speichern willst.
Im Medien Bildschirm wähle den Hochladen Button oben links (in Joomla 3 scroll runter zum Rand zum Durchsuchen Button), um den Dateibrowser zu öffnen.
#Wähle die Bilder aus, die Du hochladen willst. Klicke auf "Öffnen" im Datei-Browser um die Auswahl zu bestätigen. Hinweis: Stil und Layout des Datei-Browsers hängt davon ab, welchen Browser und welches Betriebssystem Du verwendest.
In Joomla 4 wird sofort hochgeladen, in Joomla 3 wähle den Hochladen starten Button.
<div class="mw-translate-fuzzy">
#Die ausgewählten Datei(en) erscheinen im unteren Teil des "Bild Einfügen-Fensters". Klicken Sie auf "Hochladen starten", um mit dem Hochladen der Datei(en) zu beginnen.
</div>
<div class="mw-translate-fuzzy">
#*Wenn die Datei hochgeladen ist erscheint eine grüne Nachricht zur Bestätigung oben im Fenster.
</div>
<div class="mw-translate-fuzzy">
#Du kannst nun das hochgeladene Bild wie zuvor beschrieben auswählen und einfügen.
</div>

<noinclude>
[[Category:Tutorials/de|Tutorials]]
[[Category:Article Management/de|Beitragsverwaltung]]
[[Category:Beginners/de|Einsteiger]]
</noinclude>