CPGmassImport after changes to DB - what could go wrong? CPGmassImport after changes to DB - what could go wrong?
 

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

CPGmassImport after changes to DB - what could go wrong?

Started by rivers, January 05, 2008, 06:14:26 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Print
Go Down Pages1
User actions

rivers

January 05, 2008, 06:14:26 AM Last Edit: January 05, 2008, 11:57:52 AM by Joachim Müller
Hi

I've used CPGmassImport for over 10,000 images a few weeks ago.  Since then, I have made changes to the categories of many images.  So, the database now reflects the new categories for several hundred images, but the file structure on the server is identical to when I first used CPGmassImport.  Here's an example

After initial use of CPGMassImport:
Folder1/Image1-->Cat1
Folder2/Image2-->Cat2
Folder3/Image3-->Cat3

Now subsequent to changes:
Folder1/Image1-->Cat2
Folder2/Image2-->Cat2
Folder3/Image3-->Cat1

I believe most of you are familiar with CPGmassImport and this situation where file structure no longer reflects database associations between images and categories.

My question:

If I was to use CPGmassIMport again to add more files to existing folders, would this destroy the changes I made and revert to the original "FOLDER=CATEGORY" structure?  What could possibly go wrong here?

Looking for anyone's experience with this

Thank you kindly.


Joachim Müller

#1
January 05, 2008, 11:57:42 AM
The reply I posted today on another request fits for your question just as well: http://forum.coppermine-gallery.net/index.php?topic=49508.msg237903#msg237903
Print
Go Up Pages1
User actions