Hello dear reader. In this article, I will show you how to properly upgrade Joomla 2.5 to Joomla 3.3.6. Version 3.3.6 was the latest at the time of this writing, therefore it was taken for this article, and I also updated my sites to this version. First, about the general idea of the update.
General idea of the update
The general idea behind the update is... For a safe update, we move the J! 2.5 production site to a "different location" and update it there. We leave the working site in place and do not even turn it off. After the update, we transfer the site back, instead of the "old" site. You can move the site for updating to several "places":
- To a subdirectory of the root directory;
- To another server and update Joomla 2.5 there using a different domain;
- You can create a subdomain and transfer the site to it.
In any case, the idea remains the same. The main site is online and the site backup is being updated. After the update, the site is already in the version of Joomla 3.3.6 is transferred to the main domain, and the site continues to work without interruption.
I do not recommend using a local server like Denver for updating. Also, I do not advise updating on free servers.
Upgrade to Joomla 3.3.6 Preliminary Stage
Let's start by checking the server software, because if you remember, I raised the bar for the minimum PHP version to 5.3.10.
On my server there was a build with PHP 5.3.3, so I had to start the migration by communicating with the technical service of the server (on some servers, the client can change PHP versions on his own).
PHP 5.3.29 was installed pretty quickly, which is completely suitable for installing Joomla 3.3.6. However, you need to check the work of the server's technical service, which means you need to check the PHP version yourself.
It is very easy to check the PHP version of your server.
- In a text editor (for example, Notepad +), create a php file with an arbitrary name and the following content:
- We upload the created file via FTP to the root of the site;
- Next, run the created php file in the browser and read the php version information.
Let me remind you that the minimum PHP version for installing Joomla 3.3.6 is PHP 5.3.10, however, PHP 5.4 is already recommended. Apparently Joomla 3.4 will again raise the bar for server software.
Checking and updating Joomla 2.5
Please update your Joomla 2.5.x version to the latest 2.5.28 before starting the migration. Do it automatically from the tab: Extensions -> Extension Manager -> Updates... Or download the update package HERE (http://joomlacode.org/gf/project/joomla/frs/?action=FrsReleaseView&release_id=19919) and update Joomla 2.5.x manually via FTP.
Preparing the site for updating, the first cleaning
- The next step is to remove all unnecessary (unpublished) articles from the site. It's in the tab: Material Manager → Filter-Status: Unpublished → Add to Cart.
- Empty the trash bin.
- Likewise, remove all unpublished modules. Tab Module Manager → Filter-Status: Unpublished → Add to Cart.
- Empty the trash bin with "trash" modules.
- After preliminary updates and uninstallations, clear the site cache. ( Site -> Maintenance -> Clear cache).
- Clear outdated site cache.
- Check if the version of the database is up to date. This is done in the tab Extension manager -> Database.
Backing up a production site
Now you need to make a full backup of the site, just like when transferring a site to another hosting. Let me name it, its Copy 1, it will "move". The copy should include all files and directories of the site (done via FTP) plus database export (done in phpMyAdmin of your hosting or server). I wrote how to make a backup copy of the site in the article:
Now, we work with the backup, and the main site remains online and working.
Restoring a working site in a subdirectory
To update we use the update option in the site subdirectory.
Next task. It is necessary to restore the working site J! 2.5 from the backup copy in the site subdirectory. I will name the subdirectory: perenos, the name does not matter.
To restore the site J! 2.5 in a subdirectory, do the following:
- In the root directory of the site, create a subdirectory: perenos;
- In the admin. on the server panel, create a new base with our name, new user and our access password. Don't leave the old user.
- Back up folders and files J! 2.5 upload via FTP to the subdirectory: perenos.
- We import the database reserve J! 2.5 into the new database.
- In the configuration.php file, we change the database data and the paths to the tmp and log folders. The paths must be complete, starting with the var directory. For example, for the perenos subdirectory:
- Var / path_to_Joomla / perenos / log
To check the recovery, open a duplicate of the working site, at the address: your-domain / perenos. Then we work in the administrative panel of the site Your-domain / perenos.
Optional, but you can enable debug mode in the site panel: Site → General settings → System → Debug mode. On the Site → General settings → Server → Error message tab, enable error display mode: Maximum. Showing errors can help you figure them out. If you don’t know how to read errors, then it’s better not to turn on the display of errors.
Preparing the migrated site for the upgrade
So, we have moved the production site to the perenos subdirectory. Next, we work with the site in this subdirectory. We continue to prepare, now, Joomla 2.5.28 for the update.
The update I'm describing in this article is called an automatic or quick mini-migration. Mini migration involves using a built-in core component called: Joomla! Update! With it, you can update the site itself and the Joomla core extensions. Third-party extensions cannot be updated.
In the automatic mini-migration, Joomla! Update, only the following extensions will be migrated:
- Site categories;
- Products;
- Menu;
- Non-third party extension modules;
- Banners;
- Contacts;
- Message exchange;
- News feeds;
- Redirection;
- Search;
- Smart search;
- Links.
Now, the very preparation of the site for migration. First, we check all installed plugins. All plugins that are not included in the core of Joomla should at least be disabled, or better removed (uninstalled).
Third party plugins need to look for compatibility with Joomla 3.x. In theory, you don't need to remove plugins that work on both versions 2.5 and 3.3.6. On the sites of third-party plugins, you need to read the specifics of their migration. In practice, I always delete third-party plugins, and after the update I just reinstall them.
Let me remind you that you need to remove plugins from the tab Extensions → Extension manager → Management → Select checkbox → Uninstall button.
Some third-party plugins cannot be removed, because after their installation they became system ones. In this case, select their checkbox and click the "Refresh cache" button. Then turn them off.
Plugins that were installed together with components are removed only after removing their component.
It is critical! Disable the "Remember me" system plugin in the plugin manager. Failure to disable the plugin will result in an update error.
class = "eliadunit">
Remember, Joomla extensions are not limited to plugins. The rest of the extensions also need to be removed or disabled. This is done on the tab: Extension manager -> Manage... On the tab, use Filter: Type. First, we filter the extensions of the Package type, then one after another Component, File, Language, Library, Modules, and again Plugin.
For a perfectly successful automatic update, you need to leave only the extensions of the author of the Joomla! Project. This statement can be disputed, but three unsuccessful updates were enough for me to arrive at it.
It is critical! Be sure to go to any "native" Joomla template in the template manager: Protostar, Beez_20 or Atomic. Delete third-party templates. Removing templates on the Extension manager tab → Manage → Filter: Templates.
Preparing modules for updating
We pass to the site modules and prepare them for updating. To start, disable all site modules.
Remove third party plugin modules. Delete on a tab Extension manager -> Manage -> Filter: Module.
Clear the site cache and make a new backup (Copy 2). This will be a cleaned up copy of your Joomla 2.5.28. It is needed to restore the site in case of an unsuccessful update, then correct errors and repeat the update again.
"Cleansing" the site is done.
The last check. In the tab System Information → Access Rights everything should be green.
Let's proceed to the update.
Updating by built-in component Updating Joomla!
We proceed to automatic updates from the site panel. In the administrative panel of the perenos website, open the tab: Components → Joomla! Update
In the settings (the "Settings" button in the upper right) select: "Short Support Joomla Distribution" and Write files directly.
This window may not appear immediately.
We check, once again, the availability of site backups (Copy 1 and Copy 2) and "praying" press the button "Install update".
Successful upgrade of Joomla 2.5 to Joomla 3.3.6 will be seen by the changed site panel and the message that appears. The panel template is now called isis.
Completing the upgrade from Joomla 2.5 to Joomla 3.3.6
Next, delete the Joomla 2.5.28 site from the root folder and transfer Joomla 3.3.6 from the subdirectory to it. When updating in the subdirectory, go to the subdomain configuration.php file, you only need to change the paths to the tmp and logs folders.
- Var / path_to_Joomla / perenos / logs and
- Var / path_to_Joomla / perenos / tmp
change to
- Var / path_to_Joomla / logs
- Var / path_to_Joomla / tmp
If you updated on a different hosting, then in the configuration.php file, change the database data and paths to the tmp and logs folders.
Completion of migration
After the update, install the plugins you need and are used to that work in the new version of Joomla 3.3.6.
Important! If you used SEF Joomla components, you had to do Export sef URL addresses, and on the new version Import them back after installing SEF components.
Let me remind you that the files with CNC (SEF) links are universal and "suitable" for import into all major SEF Joomla extensions. It is possible to change the SEF component during migration. When migrating five sites, I changed the Sh404 extension to Artio JoomSEF. But this is a separate "song".
After all the work, do not forget to turn off the debug mode (if enabled) and set the error display mode to "System default".
If the automatic update fails, delete the site from the subdirectory, delete the database and user. Restore the site from a backup with a new database and a new user and repeat everything again, remembering your mistakes and being even more careful.
class = "eliadunit">The release of the new version of Joomla 3.7, available for public use, was the reason for writing this tutorial. In it, we will talk in detail about updating the Joomla system, why you need to keep track of updates, how you can update the system and why, there are sites still working on Joomla 1.5.
Joomla version tagging
Correct designation of Joomla version 3.7 - 3.7.0. There are three numbers in the version designation.
- The first digit changes extremely rarely.
- The second number is an important change affecting the core of the system.
- The third number is the release of new security releases and versions with fixes of discovered bugs.
Is it possible not to update Joomla?
According to the description of the J! 3.7 release, the transition from 3.6 to 3.7 is not of fundamental importance for the security of the site. This transition, according to the authors, will improve the functionality of the site, nothing more. Therefore, if there are any good reasons that prevent you from switching to version 3.7, you can work on the latest version 3.6.5, even until the "end of the century". It is important to understand that the authors will no longer release security updates for versions 3.6 and will have to work "at their own peril and risk", more closely monitoring security.
A description of all changes in new versions of Joomla can be found on the official site https://docs.joomla.org, in the version history.
It is worth noting that the next global release is expected to be 3.8; 3.9; 4.0, but there will be many 3.7.x versions before they are released.
How to view a working version of a Joomla site
There are two easy ways to view a working version of your Joomla site.
- From the panel. System tab >>> System information.
- By FTP, at the root of the site, find the file /libraries/cms/version/version.php... On line 33 of this file, you will see the system version (block: Release version).
Joomla update in three ways
Important! Any way to update Joomla can be unsuccessful and can lead to fatal errors as a result of the loss of the site. That is why, before any update, you need to make a backup copy of the site in any available way.
Method 1. Automatic update
The system tools provide the ability to automatically update using the Joomla service. With this update method, the system will contact the Joomla update service, download the update package, the link to which is shown in the paragraph: "URL update package" and wrap the system.
To automatically update, open the Components >>> Joomla! Update tab. Next, the "Automatic Updates" tab. Set (check) "Installation method - Write files directly" and click the "Install update" button.
class = "eliadunit">
Method 2. Download and update from the administrative panel
If your hosting server does not allow a direct update from the Jooomla update server, use the Download and Update update tool. To do this, go to the Components tab >>> Joomla Update !:
- Download the required update archive (ZIP) from the link "... on the official Joomla download page" or "Update package URL" on the Automatic Updates tab;
- After selecting the update archive using the Download and Install button, install the update. You write the files directly. FTP upload requires FTP configuration in general settings.
Note: To successfully use this update method, you must have the correct path to the tmp file in the configuration.php file, as well as the CHMOD rights to the tmp directory, must be at least 644.
Method 3. Via FTP client
This method is similar to the previous one, only the update directory, you need to download it to your computer, and then upload it to the site root via FTP in the "Overwrite" mode.
- Download the update archive using the link "Update package URL";
- Unpack the archive;
- We enter the root of the site through an FTP client;
- Upload the update archive files to the site root in overwrite mode.
System update information
The Joomla system is configured by default in such a way that when new updates are released, both the system itself and all its extensions, it will inform you about this. This information will appear on the home page panel at the top of the page as pink messages.
Two plugins are responsible for displaying these messages:
- Icon Bar - Joomla! New Release Notice! ID = 437
- Icon Bar - Notification of New Versions of Joomla! Extensions ID = 438
They can be turned off. If you need to receive information about new updates by mail, use the plugin: System - Joomla Update Notification (ID = 452). Enter your email in the settings of this plugin. Before that, do not forget to configure "Mail" in the general system settings.
Updating extensions
After installing third-party extensions, the system (by default) activates communication with the update servers of these extensions. When an extension is updated, the system receives a signal about it and, when the plugin ID = 438 is enabled, informs you about it. If you do not need it, go to the tab from the main menu: Extensions >>> Management >>> Update servers (left menu) and disable the unnecessary update server.
Again, by default, all update servers are enabled and when the panel is loaded, they contact the update servers each time. This slightly increases the load on the server.
Do I need to upgrade my Joomla engine from 2.5 to 3.x?
I think it's time to think about it, because If you have updated Joomla 2.5 to the latest version 2.5.28, you could not help but notice a message in the admin panel saying that Joomla 2.5 support ended on December 31, 2014.
I was additionally prompted to update the engine by the need to implement a tagging system on the site. Having learned that the troika has built-in support for the tag system, I decided to start updating the engine.
Prerequisite steps you need to go through to successfully update your Joomla engine.
1. First of all, do not be lazy to check if your hosting meets the system requirements for the normal operation of Joomla 3.x. Now self-respecting hosting services satisfy such requirements, but it is better to check, especially since it will not take long. As you can see from the table, the requirements for the Apache for the third Joomla have not changed (2.x +), but the requirements for PHP and databases have changed. If Joomla 2.5 could still work on PHP 5.2.4+ and MySQL version 5.0.4+, then for Joomla 3.x you already need at least PHP version 5.3.1 and MySQL version 5.1. +. The fastest way to check the PHP and MySQL versions used on your hosting is to go to the Joomla admin panel, then select " Site" => "System information". We will see various information about the system, including the current versions of PHP and MySQL.
If the current versions are below the minimum requirements (which is becoming more and more unlikely every day), you will have to change hosting.
2. Next, you need to make sure that the template used on your site works on jumla of the third series. You can find out information about this on the website of your template developer. Perhaps the template developer has released a separate version for Joomla 3.x. If not, then you may have to worry about finding a template for the third joomla, and delete the current template that does not support the triple. Alternatively, you can of course adapt the template for joomla 2.5 to work in joomla 3.x in order to preserve the appearance of the site. Which is what I had to do.
After upgrading to version 2.5.28, just in case, you have upgraded your database schema to version 5.2.28. To do this, select in the top menu Extensions -> Extension manager-> tab Database... If you see approximately the same picture as in the picture below, then your database was updated normally.
If instead of a green checkmark you have a white "brick" in a red circle and a message appears in red that your database has not been updated, click on the button To correct in the upper right corner.
4. Also, before updating, you need to disable the plugin System - Remember me... Otherwise, there may be a problem with entering the admin area after the update. After the update, this plugin can be re-enabled.
5. In general, all the extensions that are built into the joomla 2.5 distribution will work without problems in joomla 3.x. Problems can arise with third party extensions. The more third-party extensions, the more difficult the transition will be. If you have many third-party extensions, I advise you to draw a plate with two columns on a separate sheet or file: " Extension name" and " Joomla 3.x support". Enter in the table the names of all third-party extensions (components, plugins, as well as modules installed through the extension manager). We update all found extensions to the latest version. It should be borne in mind that not all extensions use the auto-update mechanism ( Extensions -> Extension manager-> tab Updates-> button Find Updates). Better to go to the manufacturer's website for each update and see if the latest version is available. Next, let's see which of them support Joomla 3.x. Those extensions that do not support the triple will have to be removed, otherwise the update may fail and the site may stop opening altogether.
Let's see if extensions that do not support the triple have separate distributions for the triple on the manufacturer's website. In this case, we'll just install them right after the engine update. If the developer has not released a version for Joomla 3.x at all, then you will have to look for analogues of this extension, or you can ask the developer whether he will release a version of his extension for the troika and in what time frame.
Perhaps, in the course of such an inventory, you will find extensions that you once used, but are no longer using. It is also advisable to remove such unnecessary extensions.
To increase the chances of a successful upgrade, you can temporarily disable any remaining extensions that you have installed yourself since the initial installation before upgrading. After the update, we will turn them on in turn and check the site's performance. The exception is third-party templates (if they were installed), which are currently used in the admin panel and on the site. After all, you, as I wrote above, took care of installing a template compatible with Joomla 3.x. To disable, go to Extensions -> Extension manager -> Control... Next, we sort the last column ID descending list. All extensions that you installed yourself have ID starting from 10,000 and above. So you can turn them off before updating.
Joomla 2.5.28 to 3.x Upgrade Guide
First, be sure to read the previous paragraph !!!
I am totally against updating the combat site directly on the hosting. After all, it is not clear how the site will function after the engine update and whether it will be updated at all. I did the following.
I took a backup of my site: database and site files and uploaded it to my computer.
If you followed all the steps from the previous paragraph, then you will receive a message that you already have the latest version of Joomla! 2.5.28 installed.
We press the button " Settings" in the upper right corner.
In the window that appears opposite the " Update Server"select from the drop-down list" Joomla distributions with short term support"
You will be notified that a Joomla! Update has been detected.
In my case, the system detected update 3.3.6.
We press the button " Install update".
If everything went well, then your site will open. Checking the version of the engine from the admin panel.
If you turned off the extensions before updating, as I wrote above, then turn them back on in turn and check the work of the site.
If everything is ok, upload the updated site to the hosting instead of the old one.
If the site does not open after the update.
If you have followed all the recommendations described above, then after updating to the top three, the site should open. But if, nevertheless, the main page of the site stopped opening, this means that some component (which you missed), incompatible with the new engine, interferes with the normal opening of the site. Don't panic! Usually, the site still gives you access to the admin panel. (If your admin panel does not open, read below). We look closely at the message displayed on the screen. Typically, the message contains the path to the problem file and the line number with the problem code.
If the path leads to a file in your template folder, then it is most likely a matter of your template. In this case, you need to change it to another one compatible with Joomla 3.x (if you have not stocked up with a template in advance, you can use one of the built-in templates) and the problem will be eliminated.
If the message displayed on the screen indicates the path to the file of some extension, then you can remove this extension from the admin panel. If there is no access to the admin panel, then you can try to rename the folder with the problematic extension.
If you cannot determine which extension the problem file belongs to, then open this file in any editor (I use notepad ++) and simply delete (or better comment) the specified line of the problematic code. Next, we try to update the main page. After refreshing the main page, the message may already refer to another line in this file or another file. Thus, you continue to comment on the lines of code in the problem files until the site opens. After that, you can ask a question on any of the joomla support forums or in the comments to this article which extension the problem files belong to, indicating the path to them and remove this extension.
If the admin panel does not open after updating Joomla to version 3.x.
If you cannot get into the admin panel after updating the site, then you missed any extension or template that is not compatible with the third Joomla. As I already wrote above, the path to the problematic file that prevents opening is usually displayed on the screen. If the path leads to a template file, then you need to change it, for example, to one of the templates built into the jumla: Atomic, Beez5 or Beez_20... If the path to the file leads to a different location, you need to determine which extension this file belongs to and remove this extension. But how to remove an extension or template if you can't get into the admin panel? We will edit the database. To do this, go to phpmyadmin.
Across phpmyadmin we cannot remove the extension, but we can disable it. This is enough to get into the admin panel, and then delete the extension from the admin panel. Information about all installed extensions is stored in the xxx table _extensions, where xxx is the table prefix, which can be different for each.
To disable the extension, look for its name in the column Name tables and in column Enabled instead of one, put a zero.
To change the template to another from phpmyadmin, open the xxx_ table template_styles... This table lists all the templates installed on the site. Column client_id shows which part of the site the template is intended for (0 - for the public part, 1 - for the admin panel). Column Home shows which template is currently used by default (it costs one).
BackYou have no rights to post comments
To migrate from Joomla 2.5 to Joomla 3, the CMS authors created the core Joomla! Upgrade component. Now you don't need to use third-party plugins to update. Automatic update of Joomla 2.5 to 3.3.6 is done from the admin panel of the site. How to do this without errors, I will tell you in this article.
Checking the service for Joomla 3.3.6 requirements
Check your hosting server build. They must meet the minimum requirements to run Joomla 3.3.6. The PHP version is crucial. It should now be PHP 5.3.10+.
Getting Started Automatic Upgrade of Joomla 2.5 to 3.3.6
Task. We have a website. CMS version of Joomla site 2.5.x. You need to update Joomla to version 3.3.6.
First of all, we are updating to Joomla version 2.5.28. You won't be able to update from version 2.5.27. After a successful update, we clear the site cache and check the relevance of the database on the “Database” tab in the “Extension Manager”.
- We remove unnecessary articles and unnecessary modules.
- We clean all trash cans.
- We do not touch site extensions yet.
We make a full backup of our working site. Let's call it "Reserve 1".
We will not use third-party hosting for the update. Let's update the site in the subdirectory of the root directory on our hosting. Let me explain. We can restore a backup copy of our site on any third-party server and, by updating it there, transfer it back.
To update, create an update directory in the root folder of our domain. Let's call it. The name can be anything. In phpmyadmin hosting, create a new database. The database should have everything new: Name, User, Password.
If you need to re-upgrade after a failure, do not use the old database. For a new update, create a new database with new data, including the user. The failed database must be removed from the hosting.
In the created subdirectory, we restore our site. How to restore a site from a backup, read. We will update this particular restored site in the created directory. His address:
Second site cleaning
Now we clear the site of unnecessary extensions. Ideally, only the Joomla! Project extensions should remain. Third-party extensions must be disabled. Extensions that are incompatible with Joomla 3.3.6. need to be removed. The extensions in the extension manager are removed.
The likelihood that the site will crash when deleting, especially "corrosive" extensions, is high. Therefore, we do the following.
As you know, extensions are removed from the Extensions tab → Extension Manager → Manage. Here, we use the filter. Filter by extension type.
First, remove the Components. To be completely safe, after each removed component, we clear the cache and check the site's performance. If the site crashes, use FTP to upload the folder with the problematic component from the "Reserve 1" backup.
After removing the Components, disable / remove plugins, modules, libraries, files, packages.
It is possible that when you remove some extensions, the site crashes. In this case, download the folder of problematic extensions from the backup copy of the site: plugins, modules, libraries, etc. Disable the problematic extension instead of deleting it.
The plugin can be disabled from the database: table [_extentions]. In the table row, click Structure, look for the required plugin in the structure plugins_name from the plugin, and in the enable column, instead of, put.
class = "eliadunit">
You cannot disable a component from the database. To prevent the "capricious" component from interfering with the update, disable it from the site panel, but rather rename its folder, like com_XXXX_okl.
Once again about the steps that we took in preparation for the automatic update of Joomla 2.5 to 3.3.6 to be successful:
- Updated to version 2.5.28. Final version of Joomla long-playing release J! 2.5;
- We did the first site cleaning and restored the site in the subdirectory of the site root folder;
- At a minimum, we removed extensions that do not have versions for J3.3.6;
- Disabled other extensions;
- Didn't disable Joomla! Production modules and plugins running in the control panel;
- We switched to "native" joomla templates;
- Checked the status (relevance) of the database from the site panel;
- Cleared the website cache, panels and update cache;
- Cleared outdated cache;
- Disabled the "cache" plugin (optional).
- We made a backup copy of the cleaned site (Reserve 2).
- Checked the backup of the production site and database.
When cleaning the cache, clean not only the site cache, but the cache of the administrative panel.
Let's proceed to the automatic update.
Automatic upgrade of Joomla 2.5 to 3.3.6 - the process itself
Go to the tab: Components → Joomla! Update
On the "Settings" button, select "Short-term version ..."
If you don't see any changes on the page, clear the update cache (Extensions → Extension Manager → Updates → Button: Clear Cache).
If you see a message about the need to update to 3.3.6, update using the "Write files directly" method.
May good luck not leave you.
If the failure befell you, demolish the site, create a new database, restore Reserve 1 or Reserve 2 and try all over again. Before repeating, read the error.logs in the panel of your hosting (server).
If the update is successful, you will see a corresponding message and the default admin panel template will change. you can start getting to know the Joomla 3 admin panel.
or how to renew the system using the file manager
Before proceeding withJoomla version update, consider some of the nuances.
On the popular web site joomla.ru you will find information regarding updates: available for download Joomla! with “localized demo materials and pre-installed Russian interface language. Traditionally, the localized distribution does not differ from the standard one, except for the pre-installed Russian-language localization packs, materials in Russian, language files and the text of the license displayed during installation "and this means that it is time to update. New versions of Joomla, including Russian ones, are located in the right column of the portal, at the very top.
Joomla step by step update
We update an earlier version to a more modern one
If you have Joomla 1.5, you will first have to upgrade using the jUpgrade component.
Suppose you are using Russian Joomla. In this case, there is no point in looking for a Russian service pack. With a standard update, and this is the method presented in this chapter, the CMS settings made earlier will not change. The same goes for all other system settings and extensions. Usually, the Joomla update process proceeds without any complications.
Before, we will make a backup copy of the entire content of the site.
Loading ...