Annoying problem uploading into folders.

[Riccardo83]

When you try to upload photos into an existing album, e.g. Press section 2006 in my alizee gallery, you can do so via FTP or Online. When I created the gallery I uploaded all files via FTP and used Batch Add Files.

However if you want to upload more photos at a later point into the same gallery via coppermine(not ftp), it won't put the photos into the same album I added them via Batch add. Which is ANNOYING.

Means it would put the file into a folder like /albums/userpics/16092/ instead of the desired /albums/promo200x_xxx/ folder.

[Joachim Müller]

Is this a rant or are you asking for help? In fact, the location of the file doesn't matter: the database keeps track of it and "knows" that it resides within a particular album. The human doesn't have to "know" where the pic resides. Coppermine doesn't move pics around on the webserver's disk space for reasons of stability and maintainability.
If this bothers you, always use the same upload method (i.e. FTP-upload plus batch-add) and stick to it.

[Riccardo83]

Well. It is quite important as we link certain images on a fansite, for examples all the press article we know in which folder they are. Also if u would download the whole pictures from ftp it would be still sorted.

Problem is, not only me is adding photos, loads of people, i cnat give em all access to ftp. Isn't there a way to change that, i know that 4images gallery i used before was putting all user uploads in a temporary folder, and then as soon as the admin accepts it it moves those pictures to the right folder.

I really do think it would make things easier..

[Joachim Müller]

No, you can't change this without severe modifications in Coppermine's core code. As I said already: coppermine doesn't move files around. If you need all files to reside in the same folder, then coppermine probably is not the proper app for you, sorry.

[Riccardo83]

mhhh unfortunately but i love the rest of it, greap app. don't u think it could be considered a feature request? or not at all?

[Joachim Müller]

Won't be considered, as it would mean adding a lot of instability - with a lot of people not being aware of the impact this would have and 90% of all coppermine users not fully understanding the file/folder permissions concept, which would be a pre-requisite for such a feature to work. Such a feature would help a minority (sadly, you belong to that minority), but the majority of coppermine users would have no benefit. Instead, many would have issues with files being lost when the movement of files fails due to improperly set up permissions (keyword "CHMOD"). Coppermine has got a good reputation for ease of use, stability and maintainability - I would not sacrifice this for the sake of a feature that would only help a minority of users who use coppermine for something it hasn't initially been designed for.