Joomla! 3.x nach 4.x: Migration - Schritt für Schritt

From Joomla! Documentation

This page is a translated version of the page Joomla 3.x to 4.x Step by Step Migration and the translation is 26% complete.

Outdated translations are marked like this.
Copyedit.png
This Article Needs Your Help

This article is tagged because it NEEDS UPDATING. You can help the Joomla! Documentation Wiki by contributing to it.
More pages that need help similar to this one are here. NOTE-If you feel the need is satistified, please remove this notice.

Reason: Upload screenshots


Other languages:
Deutsch • ‎English
Stop hand nuvola.svg.png
Warning!

In dieser Anleitung wird davon ausgegangen das Du Joomla 3.10.x verwendest. Wenn Du eine frühere Version nutzt, gehe sicher das Du erst auf Joomla 3.10 updatest bevor du auf Joomla 4 wechselst.


Diese Dokumentation enthält eine Schritt für Schritt Anleitung, um Deine 3.10.x Webseite nach Joomla! 4.x zu migrieren. Zwar gibt es hunderte von verschiedenen Szenarien, aber hier zeigen wir die grundlegende Vorgehensweise zum nachvollziehen. Sehr komplexe Migrationen werden wahrscheinlich eine Folge von installierten Erweiterungen von Drittanbietern sein. Nehme Kontakt zu den Entwicklern der installierten Erweiterung(en) auf, um den bestmöglichen Migrationsweg zu erfahren.

Einführung

Die Migration von Joomla! 3.10.x nach 4.x gilt als Mini-Migration. Das ist weil die Joomla! Kernerweiterungen über die Joomla! Update-Kompontente auf der Backend-Administratoren-Seite per "One-Click" Upgrade aktualisiert werden. Viele Drittanbieter Erweiterungen sind ebenfalls One-Click aktualisierbar. Einige jedoch nicht. Du musst dir jede einzelne ansehen und bestimmen welchen Weg Du gehen musst, um von 3.10 auf 4.x zu gelangen. Wenn du das noch nicht getan hast, dann könnte dich Schritt für Schritt Migration - Selbsteinschätzung und Planen für die Mini-Migration - Joomla 3.10 nach 4.x interessieren zu lesen, bevor Du die folgenden Schritte ausführst.

Joomla! Kern-Erweiterungen:

  • Kategorien
  • Beiträge
  • Menüs
  • Module (Kern Module - keine Drittanbieter)
  • Banner
  • Felder
  • Inhalts Versionen
  • Kontakte
  • Nachrichten
  • Newsfeeds
  • Redirect
  • Search (Entkoppelt in 4.x. Verwende den Suchindex für die Zukunft. Siehe die Hinweise unter "Jede Erweiterung einschätzen")
  • Suchindex
  • Schlagwörter (Tags)
  • Weblinks (entkoppelt, ab deine Seite verwendet es vielleicht und wird migriert. Siehe die Hinweise unter "Jede Erweiterung einschätzen")

Schritt für Schritt

Eine Entwicklungsumgebung einrichten

  1. Sei Dir sicher das Du letzte Version 3.10.x ausführst bevor du fortfährst.
  2. Mach ein Backup deiner 3.10.x Live-Umgebung. Du kannst eines der empfohlenen Werkzeuge (siehe Ende der Seite) nutzen oder du machst es manuell.
  3. Mach dich darüber im Klaren das deine Umgebung die technischen Voraussetzungen für Joomla 4 erfüllt, bevor du fortfährst.
  4. Erstelle eine neue Datenbank und einen neuen Benutzer, um Deine 3.10.x-Website wiederherzustellen
  5. Erstelle eine Testseite oder eine Arbeitsumgebung in der du arbeiten kannst, um die Kopie deiner 3.10.x Website an einer der folgenden Orten wiederherzustellen:
    • Einer Subdomain.
    • Einem Unterverzeichnis.
    • Einem lokalen Laufwerk. Für Joomla gibt es eine detaillierte Anleitung (XAMPP) wie Du es unter XAMPP installieren kannst. Darüberhinaus gibt es mit WAMP, MAMP, LAMP andere geeignete Alternativen.
    • Einen neuen Hosting-Account mit einer temporären Domain im Wurzelverzeichnis. (Wenn du während der Migration den Host wechseln möchtest).
  6. In deiner Testumgebung: Update dein Joomla! 3.10.x Instanz auf die letzte Vorabversion.
  7. Gehe sicher das du auf das letzte Datenbankschema für due Version 3.10.x aktualisiert hast. Gehe dazu unter: Erweiterungen →Verwalten→ Datenbank. Sollte Dein Schema nicht wie im Bild aktuell sein, dann klicke den Reparieren-Knopf:
    J310-admin-extension-database-fix-en.png
  8. Papierkorb leeren: Hast du irgendwelche Beiträge im Papierkorb? Wenn dem so ist, dann lösche sie (und alle anwendbaren Medien, die mit diesen verknüpft sind, sofern sie nicht anderweitig benötigt werden). Für eine Migration ohne Fehler, können Beiträge (auch Kategorie- und Menüeinträge), die im Papierkorb verblieben sind, Probleme verursachen.
  9. Testen.
  10. Nochmal ein Backup machen.

Jede Erweiterung einschätzen

In your planning, you determined which third-party extensions were staying or going and how they migrate. For this portion of the Step by Step, you’ll be using two different sections of the site extensively; The Pre-Update Check in Components -> Joomla! Update and Extensions -> Manage -> Manage. You are going to be looking at every single extension installed on your site. You will be determining if they need to be updated to the latest version or uninstalled.

  1. Using the Pre-Update Check: in order to use the Pre-Update Check, you will need to set the Joomla! Update component to Joomla 4. To do this follow:
  2. Go to Components → Joomla Update. (It should say no updates found. If it doesn’t, update Joomla to the latest version (must be 3.10.x) and test. Then do another backup.) Click on the Options button at the top right corner.
  3. Select Joomla Next (This is the current text - it may be different in the future) from the drop-down for Update server.

Need an image just like below in go to j4 but the thing will not let me do it.

  1. Click Save & Close
  2. You will then see your Installed Joomla Version, the latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.

Need an image just like below in the going to 4 section but the thing will not let me do it.

BIG NOTE: DO NOT UPDATE TO JOOMLA! 4 RIGHT NOW. THIS IS ONLY TO PREPARE YOUR THIRD-PARTY EXTENSIONS AND GET THE SITE COMPATIBLE WITH JOOMLA 4.

  1. Look at the Pre-Update Check and the Extension Pre-Update Check in the Pre-Update Check tab of the Joomla Update component. If any extension that isn’t in your planning is listed here, add it to your list of extensions to investigate.
  2. If you migrated from Joomla! 2.5 to 3.x in the past, there may be some leftover extensions that need to be cleaned up. The following are older 2.5 or 3.x extensions that need to be uninstalled before updating to Joomla 4:
  • plg_content_geshi
  • Bluestork Administrator Template
  • Beez_20
  • Beez5
  • Atomic
  • When it comes to templates, uninstall all core frontend or backend templates except Protostar or Beez3 (frontend templates) and Isis or Hathor (administrator templates)
  • If you come across other files that need to be uninstalled, please add them to this page. This is a wiki so anyone can add to the page. Thank you in advance for your service.
  1. You will notice the tags for whether an extension is compatible or not. These tags generally tell a true story if they say No or Yes. If they say “Missing Compatibility Tag” it means that the extension developer didn’t use a tag in their extension so we don’t know if it is or isn’t compatible with Joomla 4. Talk to the developer to verify.
  2. Update Extensions: update any extensions that you will keep in your website. In Joomla! 3.10.x you can go to Extension Manager  Update tab and click Find Updates which will add a tooltip in the Version column, under the Manage tab, giving some compatibility information from the backend. This functionality only supports extensions that update via the Extension Manager Update tab. If you have extensions installed that do not use the Joomla extension update then they need to be assessed manually as detailed below. The same goes for those extensions that have a tooltip. You will still need to check the type of package and migration path with the extension developer to verify how to upgrade/migrate.
  3. Uninstall and Investigate Extensions: go to Extension Manager  Manage tab
  4. Click the drop-down for Type.
  5. Select Package from the drop-down.
    J310-admin-extension-manage-package-en.png
    Selecting Package first is recommended because if there is something you need to uninstall in a package, it will automatically uninstall the associated Modules, Plugins, or anything else in the package at one time.
  6. Uninstall any Packages that are no longer needed or will not be migrating to Joomla 4.
  7. Repeat this process of going through the Manage tab for all Types in the drop-down: Component, File, Language, Library, Module, Plugin and Template. If the Author states Joomla! Project, then leave those extensions alone. For all others, make sure that you uninstall those not in use or not compatible with Joomla! 4.x.
    NOTE! You will not be able to uninstall any Template that is set as default. You will need to select a Core supported template like Beez3 or Protostar and then uninstall the template if you need to do so.
  8. Make a note of any versions of Packages and Components currently running that you will be keeping on your site. You can use the Third Party Extension Checklist and Inventory Sheet or just copy/paste them into a document for reference.
  9. For any extensions you are keeping but don't use the Extension Manager to one click update (Extensions -> Manage -> Update) update all extensions to the latest versions.
  10. Before and as you update, note if the extensions have both 3.10.x & 4.x versions in the same package. If so, they will be fine to "one-click update." If not, and 3.10 and 4.x have different packages, you need to look at them case by case. They will normally fall into one of the following scenarios:
    • The extension has separate packages but upon upgrading to 4.x, they automatically detect this and still work. Make sure the developer confirms this.
    • The extension has separate packages that need to be uninstalled in 3.10.x and then installed with the Joomla 4.x version once the site is migrated. An example of this might be a content plugin. It is very simple to uninstall it in 3.10.x and then install it again in 4.x.
    • See Template Considerations for more specific information on templates and Converting a previous Joomla! Version template

Notes on Search (com_search)

Search (com_search) will be decoupled in Joomla 4.x. Search (com_search) will migrate to Joomla 4. After migration, you'll need to update it to the Joomla 4.x version via com_installer. It will continue to be maintained, but more the same way a third-party extension is by receiving updates via com_installer. It is recommended to use Smart Search (com_finder) going forward. Search will still be available at https://extensions.joomla.org/category/official-extensions/.

Notes on Weblinks

Weblinks was decoupled back in Joomla 3.4. If it was in use on a 2.5 site, the migration process would note this and migrate the Weblinks component and data. For the migration from 3.10.x to 4.x, it will be the same. It is still available and maintained on the JED at https://extensions.joomla.org/category/official-extensions/.

Going to Joomla! 4.x

Once you have either updated or uninstalled your third-party extensions so that only those compatible with Joomla! 4 remain in your installation, continue with the following steps:

  1. Go to Site  Global Configuration  Server tab and turn Error Reporting from System Default to Maximum. Make sure to Save & Close.
    J310-system-global-config-server-tab-en.png
  2. Take another backup.
  3. Go to Components  Joomla Update. (It should say no updates found. If it doesn’t, update Joomla to the latest version and test. Then do another backup.) Click on the Options button at the top right corner.
  4. Select Joomla Next (This is the current text - it may be different in the future) from the drop-down for Update server.
    J310-component-joomla-update-select-support-en.png
  5. Click Save & Close.
  6. You will then see your Installed Joomla Version, the Latest Joomla! version and the URL for the update package. Joomla will show you the requirements again for Joomla 4. If it flags that you have either an incompatible system or extensions it will tell you here. Take a moment to review this page.
    J310-to-j4-dev-update-found-en.png
  7. If the update is not showing up, go to Extension manager  Update and press Purge Cache from the toolbar. Now the update to Joomla! 4 should show up.
  8. Cross your fingers, and make sure you have that backup available in case.
  9. Click the Install the Update button.
  10. Make tea whilst the spinning circle goes round and round. The amount of time the wheel spins is dependent on your site, Internet connection and server speed. The process takes about two minutes. When the update is finished, you will probably be logged out of the Administrator. Sign in again. Twice.
  11. If all goes well, you will get to a totally new look to the backend administrator panel.
    J4-administrator-overview-en.png
  12. Click the Clear Cache button. You will now see a A Joomla update was found notice for a later version of Joomla. Postpone this update temporarily.
  13. Go to Extensions  Manage  Database and click Fix if any errors show.
  14. In the Extension Manager, go to Discover and see if there are any extensions to install (there shouldn't be any!).
  15. Go to the frontend of your site and see if it shows up even if it’s not the right template. If so, continue. If not, see common errors during migration.
  16. Take a backup.
  17. Install your new template or other extensions if you have them to install. Back up often.
  18. Configure them. Back up often.
  19. Test everything. Back up often.
  20. If everything works as expected, turn Error Reporting back to System Default (System  Global Configuration  Server tab). Make sure to Save & Close.

Going Live with your Joomla! 4.x Site

  1. When you’re ready to go live, back up your 3.10 site for the last time. Restore it in a subdirectory or subdomain if you would like to.
  2. Back up your Joomla! 4.x site and move or restore your Joomla! 4.x site to the root (or change nameservers if you were building on a temporary domain at a new hosting account root).
  3. Test again.
  4. Remove the Joomla! 3.10 site from the server within a couple of days unless you have edited your robots.txt file to block the search engine spiders.
  5. Remove all development sites you may have been working with or keep them up-to-date if they are running a current version in order to ward off hack attempts on your server.

If you had data change on the 3.10 site while you were migrating to 4.x, you will want to get that data moved over to the 4.x site before going live. You can do this manually (make sure you keep the same user IDs - go in order) or by using a transfer tool/third-party extension.

Suggested Tools