Support

Akeeba Backup for Joomla!

#29785 Site Transfer Wizard - Data Base details required ?

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by dunwin on Wednesday, 06 June 2018 06:44 CDT

Tuesday, 05 June 2018 07:46 CDT

dunwin
Description of my issue:
I want to use SITE TRANSFER WIZARD to copy a site (SITE A) to another location (SITE B).
We will then do some development work on SITE B. Once we are happy with SITE B we will then transfer SITE B back to the location of SITE A

The location (SITE B) is where I am copying to already has a joomla site on it with a data base and password

When I do the site transfer from SITE A to SITE B do I enter the Data Base credentials of SITE B in the Transfer and are all the existing files on SITE B erased so that it only contains the contents of SITE A?

Then when I want to transfer the site back ie SITE B to SITE A do I enter the Data Base credentials of SITE A in the Transfer back??

Kind regards

David

 David Unwin - London UK

Edited by dunwin on 2018-06-05 07:46 CDT

Tuesday, 05 June 2018 10:36 CDT

tampe125
Hello,

the main question here is: what are you going to change in your dev site?
Since Joomla 1.6 inside the database we have the #__assets table, which holds all permissions of every Joomla item (articles, menus, extensions etc etc).
If you want to transfer new articles or template changes (new menu being added or modules being moved), you're out of luck.
If however you have only user data, stored in their own tables, you can do that perfectly fine using the Site Transfer Wizard, we do that all the time with our site.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Wednesday, 06 June 2018 01:25 CDT

dunwin
Hi Davide,
Thank you for your reply and information.
Maybe I did not explain my question very well.
SITE B is essentially a testing site where we have tried out new Joomla components in the past. At the moment it just has some components .
What we would like to do is Replace SITE B with our Production Site (SITE A) so we then have a MIRROR of our production site on SITE B. This will include all our existing users, articles components and other data etc.
Then on SITE B we would make some changes ie add a New Component, test that it to see if it works fine.
Then we would transfer SITE B (with the newly tested component) Back to SITE A.
So my question is two fold
1) Does SITE B have to have an empty database before it can receive SITE A?
2) when we transfer SITE B back to SITE A, do we have to clean out SITE A's database?

or will SIte Transfer take care or that?
We will of course use Akeeba backup to take a backup of the Joomla sites before we do anything.

Kind regards
David

 David Unwin - London UK

Wednesday, 06 June 2018 05:34 CDT

tampe125
What we would like to do is Replace SITE B with our Production Site (SITE A) so we then have a MIRROR of our production site on SITE B. This will include all our existing users, articles components and other data etc.
No problems with that

Then on SITE B we would make some changes ie add a New Component, test that it to see if it works fine.
That's ok

Then we would transfer SITE B (with the newly tested component) Back to SITE A.
That's the whole point of the discussion. If that component alters the #__assets table, adds new permissions, modules or plugins, you can't do that. That's because every item has an entry inside #__assets table: if you make any change on the SITE A site (like adding an article/menu/component/module/plugin/user etc etc) you'll get a corrupted assets table, with a broken site.
For what is worth, if you have to do some tests, usually you can do that on the test site, then perform the same actions on the live site. So you already know which parts and which options you need to enable.

Regarding the database, Site Transfer will drop and replace the tables, so there's no need to manually empty any database.

Davide Tampellini

Developer and Support Staff

🇮🇹Italian: native 🇬🇧English: good • 🕐 My time zone is Europe / Rome (UTC +1)
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Wednesday, 06 June 2018 06:44 CDT

dunwin
Thanks Davide!

Sorry if my question sounded a "Bit Dumb". I am not a developer just an administrator. I can see now how site transfer works.
Thank you for your patience and understanding.

Kind regards

David

 David Unwin - London UK

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!