Copy Members And Load Members Into A New Dolphin Site

I have two dolphin sites. Site A has over 1000 existing members that I would like to export into Site B. Both sites are installed on separate domains. What is the most strait forward to get this done? Thanks.

back up the entire site file structure and database, and load it on the other domain. edit what you dont want to use on the second instance and that would be the easiest method.

There is more to it that that though.  The profile photos and avatars, the language keys get all screwed up I believe.   I would like to do this also - does anyone have a complete list of how to do this - including any directories that need to be moved.

DosDawg is right. Pretty much everything else is copy the data directories from modules/boonex Avatar, Files, Photos, Sounds, Videos...get the data files from the Flash/modules/videos/files and video/data and copy them over to the same location under the new domain. Make sure you have installed all the boonex modules first before you copy the data over. I have done this several time already in the past....really isnt that bad.

You can't just copy everything, especially if the site you are copying to has a member base, or if that site has media that has been uploaded.  You can only do that with a new, clean installation.  I have to assume that if it were a new, untouched installation, the first poster wouldn't even be asking the question.

The way file names, and database table records are incremented, really requires a migration script, or else you'll have a bunch of errors.  As far as I know, no one has created a migration script that will export/import data from one D7 site to another.

Maybe someone should.... but it's not a trivial task.

Thats what I was referring to. I was assuming Site B was a new install. But if it's not...definitely not an easy task.

i think i will challenge this one, because you can in fact copy siteA to siteB

and i will make a video that anyone that has access to SSH can follow and move a site anywhere at any time and the site will work, and all data will be intact. it happens everyday.

first of all you dont migrate siteA --> siteB you copy siteA file structure (meaning entire site, however you feel like copying it is up to you, zip it from cpanel file manager, login ssh and tar.gz it up, thats up to you. ) move the compressed set of files from siteA --> siteB (which i am going on the premise here that you are referring to siteA and siteB as merely the domain, and not that you have installed dolphin on siteB and then trying to move data into it)

backup the database however you want, phpmyadmin, with the use of a utility --> http://downloads.mysql.com/archives/MySQLAdministrationSuite/mysql-query-browser-1.1.20-win-noinstall.zip

SSH sqldump whatever floats your boat, backup the database

files are copied from siteA --> siteB database is backed up, now we need to have a database created on siteB that you have priveleges on, you can do this with mysql database wizard on cpanel or from SSH mysql, whatever floats your boat.

now you need to import the database from siteA --> siteB using whatever method that floats your boat

wget the sql file (zip it first) from siteA --> siteB

download to your local drive then upload to siteB

using a utility such as --> http://downloads.mysql.com/archives/MySQLAdministrationSuite/mysql-query-browser-1.1.20-win-noinstall.zip

whatever floats your boat.

now you need to dump all cache | cache_public | tmp

edit the header.inc.php file setting the url for siteB and the correct database connection stings for siteB

and that is it in a nutshell

i will try to make some time to create a video of this procedure, and try to show the different methods. i use ssh, and the utility --> http://downloads.mysql.com/archives/MySQLAdministrationSuite/mysql-query-browser-1.1.20-win-noinstall.zip

at any rate, yes you can move one site onto another domain, given that the second domain does not have an install of dolphin, but even then it can be done, just a few more steps to it. :D.

Dawg, your method only works if the site you are moving members into, is a fresh install.  If it has photos, videos, and other media that has been uploaded, you can't just copy things over.  If you are just cloning a site, of course you can copy it... that's a no-brainer.

then that is what i perceived he was asking, since he was asking if he could copy the site with the members. yes, you can do that, and you can follow the procedure outlined, and then remove all data from the directories and from the database. or just pull the profiles table from siteA and use it on siteB's database.

you are correct HL, to some of us, yes its a no-brainer as you mention,

I was going to copy to a fresh install - then delete most of the members, and develop my site from there.  I have found that just configuring a Dolphin site - forget about mods - takes a ton of time, and I was just trying to speed things up a bit.   I may do this one table by table just to see what happens.

This is a more interesting topic than I think we give the original poster credit for. In the case of a member with an active large membership base when 7.1 is released he will have considerable downtime while upgrading/fiddling/faffing/pulling hair out due to the major changes... not just small modifications. When 7.1 is released I am considering installing it as a fresh install in a new subfolder of our domain and migrating our 7.0.5 (or whatever version is immediately before the release of 7.1) members/database/data to that for testing... then (when all is modified to resemble our original site) make the 7.1 the live site. I'm not really looking forward to that!

Well, at least from 7.0.x to 7.1, you'll most likely be able to count n Boonex to provide upgrade tools, if necessary.

i would have to agree with HL on this one. boonex is most likely going to provide a means of upgrading.

just as they provided a means of upgrading from 6.x to 7.x, which i can say i ran the other day from 6.1.4 - 7.0.5 and all went off well.

some of the issues that were faced by many on the upgrade from 6.x to 7.x was that the server was timing out on execution of the script. which falls back to the topic of having equipment that is in compliance with the developers recommended specification. if max execution time is 30 seconds, which i think is default, then such an upgrade script would time out, because of that server setting.

but the topic at hand, really has nothing to do with upgrading, it has to do duplicating one environment to run on another environment. if you have SSH access, the methodology is not as daunting as when trying to do this with just ftp access.