Joomla 3.10 To 4

[Michelle Benitone]

The following are step-by-step instructions to migrate your 3.10.x site to Joomla! 4.x. While there are different scenarios, this will give you the basic procedure to follow. Complex migrations will likely be a result of installed third-party extensions. You are encouraged to contact the developers of third-party extensions installed on your Joomla site for their suggested migration path.

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 -extensions/.

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 Official Extensions.

Legacy routing will not be available in Joomla 4.x. Only Modern will be available. When you do the migration, if you are using Legacy routing, the system will automatically change them to Modern routing. You will want to run a broken link checker on your site after migrating to Joomla 4.x and before you go live.

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 third party extension.

Migrations are a great time to reassess goals, clean up, and develop other areas/elements of your site. The more organised you can be with your ideas/thoughts/plans the better. Plan, plan, plan. Planning makes execution easier.

Start planning by asking the following questions or doing the tasks listed below. You may have more items to plan for depending on the complexity of your site. Sadly, there is no way we can list every possible scenario. Please post to the Migrating and Upgrading to Joomla 4.x Forum for assistance.

Joomla 3.10.x is intended to be a bridge between the Joomla 3 life cycle and the Joomla 4 life cycle. Joomla 3.10.x will primarily be a release containing backports of API changes from the Joomla 4.x development branch to help ease the transition to the next major release for the community.New to Joomla 3.10.x is an excellent feature to the Joomla! Update component to help you with your mini-migration process: the Pre-Update Check.Once your website is updated to 3.10, the pre-update check will allow you to check the compatibility with Joomla 4.0 of your PHP and SQL options, settings, and the extensions you are using as long as extension developers utilised the targetplatform tag. See Pre-Update Check documentation for more.

Within this release, we update the cacert.pem files shipped with the core and bump the version number. Those files are used to check SSL certificates depending on the host setup and should be as up-to-date as possible. Given that 4.3.4 would be released after the communicated EOS of 3.10, this release has been done together with 4.3.3. More details within the 3.10.12 release FAQ

There are some tutorials to help you with Joomla 4. You can find the existing ones, like creating a Plugin or a Module for Joomla 4, namespaces conventions, prepared statements, using the new web asset classes and many more in :Joomla!_4.x

Written by volunteers from every sector, it's used all over the internet for all kinds of projects: from blogs and intranets to national government sites. From small shops to world-leading brand sites, Joomla is capable of growing to fit your needs.

There are a variety of ways in which you can get actively involved with Joomla. It doesn't matter if you are a coder, an integrator, or a user of Joomla. You can contact any of our volunteer engagement team to get more information, or if you are ready, you can jump right into the Joomla! Bug Squad.

The Joomla! Bug Squad and the CMS Release Team are some of the most active teams in the CMS development process and are always looking for people (not just developers) that can help with sorting bug reports, coding patches and testing solutions. A great way to increase your working knowledge of the Joomla code base and also a great way to meet new people from all around the world.

If you are an extension developer, please make sure you subscribe to the general developer mailing list, where you can discuss extension development. News that may affect custom development will also be posted there from time to time.

Most importantly, Joomla 4.0 is built for you, designed for all! Joomla4All!

To build new sites with, to migrate from Joomla RC to Joomla stable and also from the Joomla 3.10 series as well as from Joomla 2.5 series.

As documented in the announcement of Joomla 3.10 as well in a recent magazine article, Joomla 3.10 is a bridge between the Joomla 3.x series and 4.x. It will be initially released together with 4.0.0 and starting from there gets two years of official support.

We as a project have learned from the lessons from the last major upgrade from 2.5 to 3.x and for that reason changed our approaches in many ways in the development of Joomla 3.10 and 4.0. This also includes that we make early plans for the End of Support (EOS) and how we want to improve the messaging to our existing users. This article here covers the EOS messaging we are shipping with 3.10.

The EOS Plugin shipped with 3.10 has a rolling approach where a message is shown in the backend that changes over the time that the end of support date comes closer. This way we want to be proactive to inform our users about the upcoming end of support of the currently used version of Joomla.

We can fully understand this request and we have you covered here too. In order to give you full control over the message to the clients you can use the core language override feature to create language overrides for the language strings used within the plugin:

As mentioned above our solution is plugin-based and therefore you can disable the plugin when you wish to ignore the warnings but at this point, you are on your own to communicate to your users. We strongly recommend keeping this plugin active and just choose to overwrite the specific messages.

Hi,I have a big (at least for me) problem with migrating from joomla 3.10.x to 4.0.3.In the list of information unanavailable I have many items that refer to the SP page builder.Days ago I updated sp page builder, but the automatic update never went well so I installed it again.There are currently several versions of the "SP page builder" modules.If I launch the upgrade to 4.0 the installation ends with an error.Do you have any tips to solve the problem?

Hi Rob,If you manage more than few websites - you can imagine that this kind of migration/upgrade can be problematic and as we all know support for J3.10 is planned for next 1,5-2 years, so we all have time for it. I am glad that you agree with me. Something else is to create a new one on J4 from scratch than upgrade from J3.x.

Hi Paul, Yes a clean install is also a good option. I gues we in Europe have become upgrade freeks specialy on devises and software. like we starting a new race to the next version every time. And you are so right, everything is working well and there is no hurry at all. Nothings broke and the sun is shining, I going have a sit outside. Have a nice weekend!

SP page builder:Search - SP Page Builder Plugin 1.5 July 2015 JoomShaperSmart Search - SP Page Builder Plugin 1.6.1 March 2018 JoomShaperSP Page Builder Administrator Component 3.7.15 Sep 2014 JoomShaperSP Page Builder Admin Menu Administrator Module 1.4 August 2014 JoomShaperSP Simple Portfolio - SP Page Builder Plugin 1.1 Mar 2019 JoomShaperSystem - SP Page Builder Pro Updater Plugin 1.1 Jul 2015 JoomShaper.comSystem - SP PageBuilder Plugin 1.4 Sep 2016 JoomShaper.com

I don't know if I have to uninstall all modules for which there are no compatibility information available, but in this case what guarantee do I have that everything will continue to work fine?La verifica di aggiornamento non danno nessuna segnalazione

I am agree with you about the opportunity to postpone the upgrade waiting for a stable version of joomla 4.x.x.However, the compatibility problem will come back sooner or later and I would like to solve it with peace of mind and not in the middle of the migration.

You guys really need to do something on your communication. In the happy emails we read that, the world is so beautifull with the new helixultimate, followed by new templates new tepmlates and more and more new templates. maybe the "new template" team should first work on fixter? or arino?

Joomla 3.10 is soon to be at its End of Life (EoL) stage and so all Joomla 3.10 sites are now warning administrators to migrate to Joomla 4 as soon as possible. In this article we'll quickly run you through the scope of that process so you can get started migrating or ask for help where needed. At The Joomla Expert, we have provided Joomla migration services since the very beginning of Joomla, from 1.0 through to today's Joomla 4 migration needs.

The short answer is no - the Joomla 3 CMS is very stable and tends to degrade gracefully - i.e. when there is a failure it typically presents a message that tells us what the problem is. In fact, we even have some past clients still running Joomla 1.5 sites, the codebase for which has been EoL since January 1st 2012, and is still running 11 years later! That said, older versions of Joomla are slower and can be vulnerable to malware because no new security patches are to be released for these versions. The main reason we find people requesting Joomla 4 migrations are when their hosting company upgrade the PHP or MySQL version on the server, which causes PHP code deprecation to run and either display issues or make the software throw a server error. This is really the worst scenario, when your live site is no longer available. Which leads us to the long answer.

3a8082e126