XAMPP for Windows 5.6.30 to 7.1.1

[mike_300zx]

Hi, I have just started to use XAMPP on my local PC so I can develop some Joomla sites before uploading (Akeeba backup) to SiteGround.
I used the XAMPP for Windows 5.6.30 / PHP 5.6.30 (can't remember why, it was a few weeks back.)
I now note that SiteGround host for my sites has PHP 7.0.15
So I guess I should upgrade XAMPP to XAMPP for Windows 7.0.15 /PHP 7.0.15

I have read a few posts here and it seems there is no official upgrade path. So my plan is to
- use AKB to back up the local site entirely.
- Then uninstall XAMPP completely.
- Then do fresh install of XAMPP 7.0.15
- create new folder in htdocs for each local site I want
- install joomla 3.6.5 fresh in each folder under htdocs
- Use AKB to restore the site

Does that sound the right plan? Is there anything else I should note for using XAMPP for multiple local joomla sites?

Thanks, Mike

[Nobbie]

I dont know "AKB", but anyway, this is not a safe upgrade. There is no safe upgrade, as you not only have to upgrade your HTML/PHP files, you also have to adapt the old configuration changes (if there were any) to the new configuration files, you also have to export/import all SQL data (it may work only to overtake the old data folder, but there is no guarantee, it also may fail due to changes in the MySQL/MariaDB definitions for SQL databases).

Most important is a really clean backup, if you destroy anything, you would be unhappy to the rest of your life if you cannot restore your envirvonment. And then simply have good luck and try it. There is no upgrade procedure, of course due to the many many things that may have changed from one release to another, and because of user changes and user data involved.

[Altrea]

AKB stands for Akeeba Backup. That is a well known backup plugin for Joomla and Wordpress:
https://www.akeebabackup.com/

Akeeba backups contain static data as well as the database dump and makes it really easy to migrate a working site to a different server (including the url change needed).

[Nobbie]

Akeeba backups contain static data as well as the database dump and makes it really easy to migrate a working site to a different server (including the url change needed).

Each site? Or only Joomla & WordPress? What if have SMF Forum 2.x installed or phpBB3 or Magento or any shop system or or or .... all easily done with Akeeba?

And what about changes in configuration files (i.e. changes in php.ini, in httpd.conf etc.), and what about code changes due to different server releases (as it is given here for example)? I think Akeeba may be usefull for a simple server change (but with similar or same infrastructure), which only requires the data and some patches to the WordPress/Joomlay configuration. But it does BY FAR not solve all problem which may arise, when changing the whole infrastructure. Akeeba is only "die halbe Miete" or less.

[Altrea]

Each site? Or only Joomla & WordPress?
What if have SMF Forum 2.x installed or phpBB3 or Magento or any shop system or or or .... all easily done with Akeeba?

I know Akeeba specificly from Joomla and Wordpress because that are preconfigured modules/plugins nearly each beginner is able to use.
But there is also a component called Akeeba solo which is a more generic approach you can use to backup other scripts too )never used it so i cannot say really much about it).

And what about changes in configuration files (i.e. changes in php.ini, in httpd.conf etc.), and what about code changes due to different server releases (as it is given here for example)?

Which code changes do you mean?
Of course Akeeba is not the holy grail of backup mechanisms at all. It can only backup and restore a script from scripts side of view because it is a webapplication backup script. Any configuration changes needed to be done on the server components or compatibility issues needs to be solved by the user.
But Akeeba makes some things very easy especially for beginners.
You have a single minimalistic interface, you can start a backup with one click and the output will be a single backup file. No need to export your database with phpmyadmin, no need to file transfer 10000 files from the server.
This single file, a Akeeba kickstart file and the new informations for database connection and URL is enough to restore your whole site to a different server.

I think Akeeba may be usefull for a simple server change (but with similar or same infrastructure), which only requires the data and some patches to the WordPress/Joomlay configuration. But it does BY FAR not solve all problem which may arise, when changing the whole infrastructure. Akeeba is only "die halbe Miete" or less.

Thats correct. If you are doing a full backup manually (like "the common way") this checks and adjustments to the new infrastructure needs to be done too.

[Nobbie]

Which code changes do you mean?

Such things when (for example) register_globals is removed, or when HTTP_GET_VARS is changed to $_GET or or or. Or when in Apache "Allow From" is changed to "Require....". Or when in MySQL "Engine=" is changed to "Type=..." (or was it vice verse - i dont know), all these things require "code" changes, either Programming Code or configuration code. AKB cannot solve these problems and honestly, i dont have any clue if there are any similar changes from PHP 5.x to PHP 7.x (we had a problem here due to the upgrade, but i do not remember exactly).

That is what i mean with (necessary) "code" changes, when going from one server to another.

But Akeeba makes some things very easy especially for beginners.

Is is a Joomla/WordPress plugin only and that is really *nothing* in comparison to all problems that may raise if you are going to change Apache release, PHP release, MySQL release and (finally) the whole server environment. Exactly what "mike" is going to do. There is no simple "do this and that and now you are done", it is a huge and complex process which requires a lot of knowledge and a carefully administrator.