batch add doesnt work

[benjam]

when i try to batch add a group of photos to the site i get the 'no new pictures' error, but its a new directory, with new pictures.

what can i do about this?

and i also just noticed today that the one time that it did work, it only added about half of the pictures in the directory.

thanks for the info and a very big thank you for takin over where the original developer left off, i was gettin a little upset about it, until i found this oasis.

[Joachim Müller]

could you be more specific about the folder...?

GauGau

[benjam]

when i first installed 1.1.0 a few months ago, i did it because of the batch add feature, which is great.  and i added my directory (Birthday_Party_04-05-2003) to the albums directory of the site.

I clicked the batch add button, and everything seemed to work fine, as far as i can remember.

I tried to add a new folder about a week ago (escalante_trip) to the albums directory of the site and when i clicked batch add, it gave me back the error 'no new pictures'

so today i've been rummaging through my SQL db tryin to figure out if there is a way to quickly add them directly to the db, when i noticed that about half of the pics that were in the birthday folder werent added

all of the images are named DSCN####.JPG where the #### is the number of the image

and i changed the names of the escalante pics to SCN####.JPG to see if that was the problem, but it didnt work, and i also tried renaming the folders, files, etc. to no avail.

not sure whats wrong, but it's just not working

the directory (escalante_trip) is visible when i first click batch add, but when i click the directory...   nothing.

i also upgraded to 1.1.1 to see if that fixed the problem, but its still not working.

[Joachim Müller]

should be a permission problem...
Anything fancy with .htacces (or the equivalent on Windows/IIS, if you're running M$)? Turn it off (at least for the moment). If part of a folder has been indexed, your browser has probably run into a time out during batch-add.

GauGau

[benjam]

and how do i do that?

[Joachim Müller]

do what? You put the .htaccess file there sometime - you remove it now! What is exactly your question?

GauGau

[benjam]

exactly my question is...  i never put a .htaccess file in there, and there isnt one there now.

must be something else...

[moorey]

I'm at lost to what you're describing.  Do you have a link with some passwords where we could have a look?

It does sound like a permission problem - if you're on Windows,  make sure the albums folder is readable and writable by CPG.

[benjam]

does it matter if i'm on windows or not?  

the folder is online on my website, through my webhosting...

shouldn't matter what os i'm using, but if you mean is it CHMOD to 777 then yes it is.

i have sent you both a PM with login information in it.

thanks for the help.

[benjam]

does anybody else have any thoughts on the matter?

if you would like to see if you can help, please send me a PM and i will get you an admin login so you can check it out.

thanks for the assistance.

[Zarsky]

benjam,

Please explain your hosting setup....OS, PHP ver, mysql ver, etc.  Are your running yoru own webserver?  This sounds like a permission issue.  We need more information to help you.

[benjam]

My hosting is through dr2.net

with the following System Information
Operation System - Linux
Apache Version - 1.3.28 (Unix)
Kernel Version - 2.4.20-19.7smp
Perl Version - 5.006001
PHP Version - 4.3.2
MySQL Version - 4.0.15-standard

if you need to know anything else, please let me know.

[Zarsky]

OK....this really sounds like a permissions issue to me.  Otherwise I would try re-installing a new version of Coppermine with a new DB and see if it works then.  It could be you messed up one of the script files by accident.  It is not enough to just chmod -r 777 a directory.  You must be sure you are the owner as well.  Many cheap hosts mess up ownership all the time because the have scripts which crawl user webspace etc.

[benjam]

I'll try deleting everything; DB, scripts, everything, and see if that works...

i'll keep you posted...

[benjam]

that worked, it must have been a conflict between something that was on there from 1.0 and something that was from 1.1.0

thanks for the info