Forums

JoomlaShine supports and discussions

  1. Forums
  2. General Issues
  3. Features Suggestion & Wishlist
  4. My bits of advice on updating your websites to Joomla 4
Personal Note to Joomlashine:
I permit Joomlashine to use anything I post here any way you want, anywhere you want. You can modify, whatever, if it helps you guys (and girls).
—My advice will be to spread the info and the “How to” to your customers and make them understand that this is not a typical “One-click” upgrade & some precautions need to be taken to run smoothly
==============================================================

◉ The passage from Joomla 3 to Joomla 4 should be straightforward If you take a bit of your time to read this and the official channels on the subject.
Important First Basics Concepts:
1• Let’s be calm, Joomla 3.10 will be supported 2 YEARS after the release of 3.10, until 2023, Yes you read right 2023!
— at —> https://developer.joomla.org/roadmap.html#310
2• Joomla 3.10 is the first mini migration and should be easy from the last 3.9 versions. Should be done with the normal precautions taken before any updates.
—Joomla tell us that any extensions working on 3.9.28 should work on 3.10.
Note: I personally test it on few websites without problems. I did experience a small incompatibility with one component on one website now fixed
— Thanks to the fantastic work by Joomla developers, Joomla 3.10 come with a new permanent “Pre-Update Check” tool that will permit to check compatibility of all aspect of your Joomla website and 3rd party extensions before updating anything. (Specially made from pre-check for Joomla 4 but will be part o Joomla now!)
3• From There Joomla 4 should be a non-event update

◉ Official info from Joomla:
These articles should demystify the process and make everybody at ease
In order of Reading:
• From Joomla —> Joomla 3.x to 4.x Step by Step Migration
http://docs.joomla.org/Joomla_3.x_to_4.x_Step_by_Step_Migration
• From Joomla —> Joomla 3.10 Pre-Update Check
http://docs.joomla.org/Pre-Update_Check
• From Joomla —> Planning for Mini-Migration - Joomla 3.10.x to 4.x
http://docs.joomla.org/Planning_for_Mini-Migrat...Joomla_3.10.x_to_4.x

◉ First Basic Precaution:
Please Backup your site before upgrading anything
If you are serious and care about your website (Whatever CMS it is) you should NEVER blindly update anything without at least take a full backup if something goes wrong.
— Can be done at the press of a button, without specials technicals skills with the great free well known Joomla component Akeeba Backup at —> https://www.akeeba.com/products/akeeba-backup.html
Now with this Akeeba backup/clone you can not only revert your main website in seconds to points that you choose, you can also reinstall any of these clones in seconds anywhere on your local server, or even easier (see below) on your own live test environment to test any changes, updates to your heart content without no risk to you REAL Public website.
I never rely entirely on those CPanel server backups because they sometimes fail and mostly when you need them (They still can be a fail-safe in case of bad luck).
My personal update routine:
With Akeeba, it becomes a routine, just before updating anything on my live server or even my local clone, I take a backup. I test all updates on my local copy and check for errors. If ok, I backup & update my live site, check for errors and do another backup of both live and local clone website in the fully Update state.
This simple technique saves my beacon more than one time over many years. Also, Akeeba generates a simple compress file or collection of compress files ( for big websites) that you can manage, name to your liking download for safekeeping and keep your disk space usage quota in check.


◉ Go further, be totally safe:
• Test your upgrade on your website clone by creating a testing dedicated space

◉ • The easy way
Creating a live testing environment on the hosting space you own
1. Create a subdomain and a dedicated database in the CPanel of your hosting company to receive a clone of your website for testing.
Ideally, you want that subdomain to reside at the same level as your live website and NOT INSIDE your website as many Cpanel subdomains creation buttons do. Ask your hosting service to create it for you that way, it will take them few seconds.
It should look like that on the server
server-2.jpg
Note; Subdomains are normally free to add to your account and, no need to buy a domain name.
Example of my hosting space:
With my hosting company, I’m not using the “Subdomain” button but the “Domain” tool to create a new sub-domain and use the real main domain name as a suffix.
— My real site folder and Domain Name —> my-website.com
— My testing website space —> test.my-website.com
Using subdomains (made with subdomain button) normally end-up in your real website public_html. This is not optimal as your clone test website will use the same htaccess and settings of your main website. Also, they can be a cause of breach of security and need to be hidden from Search engines
The way shown here, permit to have more control for testing and at the security and access level.

◉ The not so easy way but really practical
• Creating a local server with MAMP or other software:
— Free on PC & Mac with the well known Mamp software —> Free to download and use —> http://www.mamp.info/en/downloads/
(Need some knowledge of Mamp, servers but relatively easy to install and use)
— Use Akeeba for backup/cloning the same easy way, but on your own computer.
I’m Testing Joomla 4 right now, I can tell that our Joomla CMS is now really the best CMS ever built!
Attachments (1)
Responses (1)


There are replies in this post but you are not allowed to view the replies from this post.
Sorry, the discussion is currently locked. You will not be able to post a reply at the moment.