Skip to content

Releases: dellermann/springcrm

2.0.15

23 Dec 17:51
Compare
Choose a tag to compare
2.0.15 Pre-release
Pre-release

New features

  • Report about outstanding items for particular customers
  • Terms of payment as global configuration value and organization dependent value. Compute the due date in invoices and reminders using the term of payment (issue #8).

Bug fixes

  • Issue #10: disable installer after some time

2.0.14

23 Dec 09:10
Compare
Choose a tag to compare
2.0.14 Pre-release
Pre-release

Revise the whole code for Google synchronization (currently contacts, only) and make it more stable.

1.5.3

07 Aug 11:50
Compare
Choose a tag to compare

This is a bugfix release that addresses the following issues:

  • Issue #64. Errors saving invoices with lots of items.
  • Issue #3. Duplicate of issue #64.
  • Issue #65. Product/service selector doesn't close.
  • Fix bug that JNDI property springcrmConfig wasn't evaluated.

1.5.2

17 Jan 16:52
Compare
Choose a tag to compare

This is a bugfix release that fixes the following issues:

  • Issue #46 - No valid until date at copying quotes.
  • Issue #48 - Cannot save sequence numbers.
  • Specifying a Groovy file via JNDI property springcrmConfig wasn't possible; it was read as a properties file and thus produced errors
  • Update to i18n-asset-pipeline 0.9.2 which fixes a bug during logging when tag <asset:i18n> is called with null locale
  • Remove sorting for computed properties (here: closingBalance) in invoicing transaction because these properties are stored in user settings and cause further SQL commands are failing

1.5.1

22 Dec 15:54
Compare
Choose a tag to compare

Features

  • Add a calculator to the main navigation.

Bug fixes

  • Update to i18n-asset-pipeline version 0.9.1. This fixes an error that localized files were not correctly loaded in production environment.

Improvements

  • Use i18n-asset-pipeline to generate client-side l10n. This improves speed when generating pages.
  • Improve use of external configurations, especially Log4J configurations.
  • Use bower.json to store necessary Bower components.
  • Add a Grunt task that copies the necessary Bower components to the source folders.