Pre-Update Check: Difference between revisions
From Joomla! Documentation
| Line 32: | Line 32: | ||
'''Q: What do the tags mean?''' | '''Q: What do the tags mean?''' | ||
A: The green '''Yes''' tag means that the extension has been tagged by the developer that the extension | A: The green '''Yes''' tag means that the extension has been tagged by the developer that the extension as ready for Joomla 4. It ''should'' migrate with the one-click from 3.10.x to 4.x. Verifying with the developer is suggested. | ||
The red '''No''' tag means that the extension has been tagged by the developer that the extension is not ready for Joomla 4. Check with the developer on the migration path from 3.10.x to 4.x. | The red '''No''' tag means that the extension has been tagged by the developer that the extension is not ready for Joomla 4. Check with the developer on the migration path from 3.10.x to 4.x. | ||
Revision as of 17:59, 12 June 2020
New to Joomla! 3.10.x is the Pre-Update Check component. This component shows technical specifications of the server the site is on and core and third-party extensions that use the Update Server in a list form.
Note: the Pre-Update Check component continues to change. If you notice that what you see is different from your site in look and feel and perhaps functionality, do update this page.
Technical Specifications
The top portion of the Pre-Update Check shows if your current server environment is compatible with Joomla 4.x for both the required PHP and Database Settings. The data on the Technical Requirements page will be updated to show Joomla 4.x specs when we are closer to GA.
Your site may look different than the screen capture above. What's important is to check if anything is red and not compatible with Joomla 4.x. If it isn't, you'll need to talk to your host or change hosts before migrating to Joomla 4.x. During a migration is a great time to change hosts. See the Migration Funnel for more information on planning and step-by-step instructions (docs from 3.10.x to 4.x aren't ready yet. Use the 2.5 to 3.x funnel as a guide.)
Extensions Pre-Update Check
The extension portion of the Pre-Update Check component pulls Joomla core extensions and third-party extensions.
The list is broken into sections based on the targetplatform tag the extensions are or are not using. For devs, see Deploying an Update Server for more information about these tags and how to deploy an Update Server. For more information about what the Joomla Update System is, see https://extensions.joomla.org/support/knowledgebase/submission-requirements/joomla-update-system-requirement/ and https://docs.joomla.org/Help39:Extensions_Extension_Manager_Update.
The Notice section at the bottom of the list shows the different tags and what they mean. There is more detail below in the Questions and Answers portion of this doc.
The following screen capture shows a website that is small but has been migrated from 2.5 to 3.x and will now go to 3.x to 4. As you can see it's a little messy.
Questions and Answers
Let's break this down into some Questions and Answers.
Q: What do the tags mean?
A: The green Yes tag means that the extension has been tagged by the developer that the extension as ready for Joomla 4. It should migrate with the one-click from 3.10.x to 4.x. Verifying with the developer is suggested.
The red No tag means that the extension has been tagged by the developer that the extension is not ready for Joomla 4. Check with the developer on the migration path from 3.10.x to 4.x.
The yellow/orange Yes (x.x.x) tag means that the extension has been tagged by the developer that the extension may need an update in order to be compatible with Joomla 4. Update the extension and see if it turns to a green Yes. If it doesn't, check with the developer on the migration path from 3.10.x to 4.x.
The gray Missing Compatibility Tag means that the extension doesn't have a tag OR does not use the Update Server. The developer hasn't said yes or no or needs an update. In some cases, a package may have been installed and the component portion has a tag but the additional plugins or modules are missing tags. As always, you'll need to check with each extension developer to verify the migration path from 3.10.x to 4.x.
Q: What about the Joomla core components?
A: Joomla core extensions will migrate from 3.10.x to 4.x on the one-click with the exception of:
The language packs are not yet ready for Joomla 4. Over time, they will be. If your site depends on other language packs, wait to migrate until all the language packs are ready.
The Weblinks component is not yet ready for Joomla 4. If you're going to continue using Weblinks in your Joomla 4 site, wait to migrate until the Weblinks component is ready. Q: What about templates?
A: Because of the changes in Joomla 4, your template may or may not be compatible with Joomla 4. The core templates like Protostar, Beez3, Beez5, etc. will "convert" to the new Cassiopeia template on the one click and the older templates completely removed. If you're using a club template from a third-party developer that is not compatible with Joomla 4, you'll need to change your default template to Protostar (or Beez3) before you do the one-click. If you have older administrator templates or core templates, it's recommended to ininstall all of them except whichever of the core templates you will set as default. This includes Bluestork, Hathor, the other beez templates, etc. You will keep Isis as the administrator template. You will keep either your compatible third-party template, Protostar or Beez3 as default. You will uninstall the rest.
Q: Can I uninstall plg_content_geshi?
A: Yes. This is leftover from the 2.5 life cycle and must be uninstalled.
Q: What about all that FOF, fef, etc.?
A: Many extensions tagged Missing Compatibility Tag WILL make it through the one-click and migrate fine. It is recommended that you go to Extensions -> Manage -> Manage and check all extensions. Typically the ones authored by Joomla will migrate on the one click. Typically the Akeeba extensions will too. Again, check with extension developers to verify the migration path on ALL third-party extensions.
Q: Does the Extensions Pre-Update Check show ALL the extensions installed on my site?
A: The Pre-Update Check will show all extensions. Only extensions that use the Update Server are given compatibility information. Those extensions that do not use the Update Server will show in the list with the Missing Compatibility Tag.
Summary
From a migration perspective, it is my belief that the Pre-Update Check should be used a guide. You'll want to have a second tab open with Extensions -> Manage -> Manage open in order to uninstall any extensions or check who they're authored by so you can contact third-party extension developers on the migration path they've established to migrate their extensions.