Advanced search  

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]

Pages: [1]   Go Down

Author Topic: JUpload release 4.0.0rc2 (coppermine 1.5 compatibility + Java 1.5)  (Read 4368 times)

0 Members and 1 Guest are viewing this topic.

etienne_sf

  • Moderator
  • Coppermine addict
  • ****
  • Offline Offline
  • Gender: Male
  • Posts: 908
    • Wiki

Hi,

  Here is the announce for the 4.0.0rc2 Release.


The release is available as attached on this message (see below).


===== Version 4.0.0rc2 =====

Fixes:
  
 * [Major] Compatibility with Java 1.5 is now restored (broken in 4.0rc1). Makes it work on Mac computers.


===== Version 4.0.0rc1 =====

Note for 'old' users:
If you're migrating from a JUpload version older than 2.6.0, you'll have to manually set your JUpload configuration, in the
JUpload configuration file. No more migration for these old versions.

Change:
  * [MAJOR] First JUpload version compatible with Coppermine 1.5

Fixes:
  * [Major] JUpload is now compatible with ImageMagick.
  * [Major] When browsing the upload result, the pictures displayed may not be the correct ones, when there are a lot of uploaded pictures.
  * [Major] When using a proxy, the port number of the postURL was ignored.  
  * [Minor] Picture storage: JUpload now stores pictures exactly where Coppermine would have (no more subfolders). It corrects errors in some environment. Too bad... for big galleries, picture finding by the OS was quicker.
  * [Minor] Session management improved. Now works with google chrome, and should work better in bridge mode.
  * [Minor] All download links (visible on the upload page and in code comments) are now changed to use Coppermine forums.  
  * [Minor] The maxFileSize displayed on the upload page was the Coppermine one, and doesn't depend on the JUpload own configuration.
  * [Minor] The debug output now always contains the server response: I'll stop asking to put the debug on, when something bad occurs.
  * [Minor] More debug output, to understand what's happening, in some particular case, on server side.


Etienne
« Last Edit: November 17, 2009, 11:16:46 am by etienne_sf »
Logged
Pages: [1]   Go Up
 

Page created in 0.023 seconds with 19 queries.