My site is set up w/ phpnuke. I am aware that Coppermine will no longer be developed to work under that cms. Here is my question.
I don't wish to get rid of Coppermine. Out of all the image programs, I love the diversity of Coppermine. However, because it's no longer being developed for phpNuke, I no longer wish to have the phpNuke version installed on my site because if a hack is discovered, I'm SOL. So... I wish to move Coppermine out of phpNuke and install it as a standalone.
What conflicts can I look forward to? I'm only able to have one database on my server. Will I be able to successfully install Coppermine on a sub-domain and have it use the current nuke database? I'm assume that folks will need to register to access and use the current stand-alone Coppermine, correct?
Is what I want to do feasible?
Thank you for any input you have on this. It's very much appreciated.
I remember seeing a post or two from other nuke users that have converted their nuke Coppermine db into the standalone version. You'll have to search around for it. The dev team isn't familiar with the nuke version and can't give you any good advice. You could also ask your question over at cpgnuke.com and see if they can help you.
Hmmm Don't think I was very clear in my questions.
I don't want to intergrate Coppermine into actual phpNuke. I know at this point, that is beyond my ability.
My main site is on http://www.mysite.com. It has phpNuke installed on it, which is using up my one database that my web host allots me.
I wish to install a standalone version of Coppermine on http://gallery.mysite.com
Obviously it will be seperate from phpNuke.
Can I use the current database or will Coppermine Standalone require a clean database to dump its information into?
I know you don't want to integrate the standalone into your nuke site. I'm saying we don't know what changes the cpgnuke team made to the database structure, so we can't tell you what you need to do to make everything work. That's why I recommended you check out cpgnuke.com and ask your question over there. They know what changes have been made and can probably tell you what you need to do, structure wise, to make the standalone version work with those tables.
If it's possible to use the Coppermine nuke tables with the standalone version, you won't do the standard install. You'll have to make a config.inc.php file (there's an example in the /include directory) with your mysql information.
If it isn't possible to use the Coppermine nuke tables, you'll have to export your table data, make the changes necessary to the sql file so it will work with the standalone version, then import the data back into your database (with a different table prefix, of course), and make the config.inc.php file as I described above.
As I said in my earlier post, I believe a user has successfully converted the nuke version tables to the standalone version tables. Please search the forums for it.