I found some problems on my CPG 1.4

[lamsoft01]

After I upgraded the newest version of CPG from CPG 1.4.1

I found some bugs..(probably)


The file "minibrowser.php" is able to browse the files and folder outside the gallery root folder.

On windows platform, the CPG is automatically add a "/" on the Gallery root path, which make the system is unable to search the files and folder in the "batch add files" section. The correct root path should be something like "C:/HTTP/CPG", but CPG add a slash, and it becomes "/C:/HTTP/CPG/"

My CPG is using UTF-8 Encoding, and while I am using the traditional "batch add tools", the "searchnew.php" display the filename and folder in incorrect encoding (the browser detected it as UTF-8, while the filename and folder are in BIG5 encoding.)

The "update.php" has bugs, it shows that all queries has updated already, but I found that some queries has not been processed, and I have to manually add them.

Thanks

[Lucas Novae]

I'm having exactly the same problem, on CPG 1.4.9 installed under Windows (FRESH install). There's a preceding slash that's automatically added to the base directory in the Batch Upload section of the admin interface.

The folder should normally be "D:/Web/gallery/albums/" but is in fact detected as "/D:\Web\gallery\albums/" , which is pretty messed up.

Shouldn't this be repaired? What code can I change to do this?

[Sami]

@Lucas Novae:
Batch add will not work on windows box

[Stramm]

open the batch add interface, scroll down and click
Browsable interface (recommended)     -    No   

you'll use the classic batch add interface than which will work together with win

[Joachim Müller]

Not related to upgrading though. The browsable batch-add interface didn't work in cpg1.4.1 neither for Windows-driven servers.

[Lucas Novae]

Thank you Stramm, I had not noticed this little option - I was just expecting it to work just like the last time I had used coppermine, over a year ago.

GauGau and bmossavari - If the "new" interface doesn't work, then why aren't you detecting the OS, and automatically switching to the classic interface? That would be the logical course of action...

I'm sorry to have replied to an old post in the upgrading forum by the way, I had not noticed this little detail.

[Joachim Müller]

So your question basically is "why don't you fix all existing bugs?" then. Hm, not sure. Maybe because we're not capable to do so. Try Batch Upload under Windows Server - Problem and its solution and see if it helps.