Cyclos Files

The following packages are available:

# cyclos_3.7.3.zip
This package contains the following directories/content docs:
Cyclos documentation and change log
src: Cyclos source code
web: Cyclos application (with all libraries)
This version will need Java (JRE), the tomcat webcontainer and a mysql database.

# cyclos_3.7.3_standalone.zip
The quick install contains a complete installation that will run on any platform that supports Java (Linux, Windows, BSD). The Java run time environment (JRE) is needed to run this version. It can be downloaded at http://www.java.com. Java 1.5 (aka 5.0) is required. If you use Java 6 (aka 1.6) ensure the version is 1.6.0_04 or later versions 1.6.0_00 to 1.6.0_03 won't work).
Besides Java the package does not need anything to be re-installed or configured. Just un-zip the file and run the start script in the Cyclos directory (instructions can be found in the readme.txt file in the cyclos directory)

# cyclos_3.7.3_upgrade.war
This package contains the Cyclos application without the libraries. You can use this packages to update Cyclos from version 3.7

Note: Cyclos 3.7.3 is compatible with the SMS version 1.2.1 and 1.2.2


Cyclos 3.7.3 changelog
==================


New / modified functions
 * Changed the hibernate.default_batch_fetch_size to 1 by default (previously, was 20). Now, Cyclos takes up much less memory, at minimum cost of performance.

Bug fixes
 * An unexpected exception could cause the Lucene indexing thread to be interrupted, resulting in no more indexes being updated
 * There was a possible error while indexing members
 * There could be errors when exporting data (member, member records, ads) with custom fields of type member autocomplete
 * On PosWeb receive payment, when selecting the empty option for payment type, an error was being displayed
 * A bug introduced in 3.7.2 prevented members from editing their own profile if there were custom fields marked as unique
 * Custom fields with mask and flagged as unique were not correctly checked for uniqueness, making the validation always pass
 * Payment custom fields which are marked as unique Ignore unique validation on payment custom field when transaction was cancelled or denied
 * Custom fields of type URL were not being correctly validated
 * Caches were not being correctly invalidated when deactivating an advertisement category, leading to inactive categories being shown on the advertisement search