Advanced search  

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]

Pages: [1]   Go Down

Author Topic: Re: Direction/Tutorial for phpbb & CM intergration  (Read 3070 times)

0 Members and 1 Guest are viewing this topic.

villin

  • Coppermine newbie
  • Offline Offline
  • Posts: 3
Re: Direction/Tutorial for phpbb & CM intergration
« on: September 04, 2005, 03:04:55 am »

I currently run my forum(phpbb2.0.17) and gallery(cpg1.3.2) independently with two separate sql databases obviously. In step 5.2.5 of the integration procedure, it is stated that it is mandatory that the cpg and bbs tables be in the same database. How should I handle this situation? Should I replicate all the tables in my coppermine sqldb and insert them in my forum database?

The remainder of the integration procedure is easy for me to understand and execute but this database issue is preventing me from implementing this mod. Sorry if this question is out of line but i'm very unfamiliar with working with databases and I would really like to get this integration set up.
« Last Edit: September 04, 2005, 03:08:56 pm by GauGau »
Logged

Nibbler

  • Guest
Re: Re: Direction/Tutorial for phpbb & CM intergration
« Reply #1 on: September 04, 2005, 03:12:39 am »

Replicating the tables would get confusing. The best way is just to move coppermine into the phpbb database. Make sure the tablename prefixes are different, then backup the coppermine tables and import them into the phpbb db. Then adjust include/config.inc.php with the new db details.
Logged

villin

  • Coppermine newbie
  • Offline Offline
  • Posts: 3
Re: Direction/Tutorial for phpbb & CM intergration
« Reply #2 on: September 04, 2005, 03:17:49 am »

Thanks for the assistance.
Logged
Pages: [1]   Go Up
 

Page created in 0.014 seconds with 15 queries.