Advanced search  

News:

CPG Release 1.6.26
Correct PHP8.2 issues with user and language managers.
Additional fixes for PHP 8.2
Correct PHP8 error with SMF 2.0 bridge.
Correct IPTC supplimental category parsing.
Download and info HERE

Pages: [1]   Go Down

Author Topic: CPGmassImport after changes to DB - what could go wrong?  (Read 3629 times)

0 Members and 1 Guest are viewing this topic.

rivers

  • Coppermine novice
  • *
  • Offline Offline
  • Posts: 20
CPGmassImport after changes to DB - what could go wrong?
« on: January 05, 2008, 06:14:26 am »

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.


« Last Edit: January 05, 2008, 11:57:52 am by Joachim Müller »
Logged

Joachim Müller

  • Dev Team member
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 47843
  • aka "GauGau"
    • gaugau.de
Re: CPGmassImport after changes to DB - what could go wrong?
« Reply #1 on: 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
Logged
Pages: [1]   Go Up
 

Page created in 0.016 seconds with 20 queries.