integration & database confusion integration & database confusion
 

News:

cpg1.5.48 Security release - upgrade mandatory!
The Coppermine development team is releasing a security update for Coppermine in order to counter a recently discovered vulnerability. It is important that all users who run version cpg1.5.46 or older update to this latest version as soon as possible.
[more]

Main Menu

integration & database confusion

Started by Aerin, July 04, 2005, 12:53:34 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Aerin

Hi. I'm trying to integrate CPG 1.3.3 with Invision Power Board 1.2. I read your Documentation, and I noticed that these have to be in the same database to bridge correctly.
Unfortunately, I used Fantastico to install my Coppermine, and now they are in two different databases. Is there any way to move Coppermine into the IPB database?  (without having to uninstall it and then upload it & re-install manually?)
I don't have any other mySQL databases left but I do have phpMyAdmin to work with. I haven't used that function before, and I've never dealt with much mySQL before, either.
???
my gallery site is: http://sweet-okashi.sy2.com/gallery
my IPB is @ : http://sweet-okashi.sy2.com/forum

Any help would be sincerely appreciated.
Thanks very much in advance.
~Aerin

Nibbler

The link to your gallery does not work.

You can move coppermine into the IPB database using phpMyadmin and then edit coppermine's include/config.inc.php so that it contains the information of the ipb database. To move coppermine you need to use 'export' in phpmyadmin while in the coppermine database, that will give you a file of all coppermine's database tables. You then switch to the ipb database in phpmyadmin and click on the SQL tab, upload the file, and that will import the coppermine tables into the ipb database. Then you have to edit coppermine's include/init.inc.php with your FTP client and fill in the new database information. You can get the right information from ipb's conf_global.php file, but don't change the table prefix. Once you have done this, they will be in the same database and should bridge with no problems.