importing database of profiles

Hi All,

I'm considering importing existing dating profiles into my newbie site at least to boost early attention from visitors.  However my php script writing is pretty embryonic, so does anyone know of a good website to help me create a simple script to link the database to my site, or even some examples of script themselves?  The alternative is to pay a programmer to write some script for me but I would rather muddle through myself...with a little help from my wonderful Boonex friends of course

Tom

Hi,

there is a 5$ mod from Sneha that helps you import users via CSV

http://www.boonex.com/m/import-users-via-csv-from-admin-panel

If you want to export profiles then Modzzz has a module for that.

 Awesome thanks!

does this import photos as well?

if not, does anyone know the file structure of Dolphin for photo storage?

thanks

felix

No; to import photos associated with profiles you would have had to exported the information, albums; objects from the database and then exported the associated files, thumbs, resized images, original images, into an archive.  Image the size of your export file if you have a few thousand members and they each have hundreds of photos they have uploaded over time.

Is your existing site that you are exporting data from a dolphin site or something else?

 sys_ablums, and sys_albums_objects

Dolphin stores photos with a hash for the name.  You could skip the original but you would need to create the thumbs.   Also, you set the sizes of the resized photos in the admin; you would probably need to run the photos through something that resizes down any photos that are larger than what you want for your site.  Lots of things to think about with photos and you need to read up on how Dolphin handles photos and albums.

bx_photos_main also??

i don't see how sys_ablums, and sys_albums_objects work without bx_photos_main.... am i missing something obvious ??

--------

i am importing from an OsDate site that was modded rather heavily...

Yes, of course.

So what you need to do is to see how OSDate structured the members' photo and then write a script that will go from OSDate to Dolphin.  Dolphin stores the file names with a hash; that is important to know as well.  There are some people in the market that offers migration services.

thanks....

about 90% done with the migration.... just the photos left to do, and understanding how they should be input into the Dolphin database is the last step....  i will have to look at the code to see how the hash applies. --ie is it just a random hash to confuse those who would hot link to all photos? ...or something more...

bx_photos_main seems to hold a unique id for each uploaded photo, its size, and a name/descrition, and the hash

once that table is populated:

every imported user must have an album created in sys_ablums, and  then

the images given a token value in each album created that correlates back to each owner/creator...

I am going to keep it simple and simply upload an image for each user into a 'Profile photos' album with the 'Caption' and 'Url" for the album "user's photos" and "user-s-photos.

sys_albums_objects then becomes:

id_album   id_object  obj_order

1                     1               0

2                    1               0

3                    1               0

4                    1               0

...etc keeping the id_album the same as the ID:bx_photos_main and ID:Profiles

hope that makes sense....

In the photo module, you can set the name for the user's profile photo album.  The first photo in that album will be the photo that is displayed in the profile photo block on the home page.  Make sure the name you set in your migration matches what you set in the photo module for the default name of the profile album.

I don't know the rule for creating the hash for the file name as stored on the server.

Geek_Girl: thanks.....

i had not yet found that setting.... i will be inputting that data via mysql, but nice to know where it is input from the php...

the hash for the filename (i believe) is:

 $sHash = md5(microtime());

since microtime is symbolic of a distinct moment in time all files should end up with a unique hash (except for time travelling computers)....

cheers, 

and thanks again...

david