Skip over navigation

Contact us to learn more about OroCRM capabilities

learn more

Developers' Digest

February OroCRM Maintenance Releases Recap

March 6, 2018 | istrutynska

Need an update on how we’ve solved minor performance issues in OroCRM? This February maintenance releases recap highlights all the recent changes. Let’s take a moment and overview the OroCRM long-term-support (LTS) and other maintenance releases the Oro Team has issued in February.

New OroCRM LTS Maintenance Releases

OroCRM Enterprise 2.6.4

The changes introduced within the maintenance release for OroCRM Enterprise 2.6.4 are the following:

  • The maximize/minimize control button works as expected.
  • Once the permissions are disabled, Menu items are no longer available.
  • The option closeOnSelect in Select2 library works properly.
  • Report grouped fields display additional comments.
  • Upon the migration from 1.12 to 2.x versions, the Opportunities functionality works as expected.

For more details, visit the respective * GitHub repository and read release notes.

* Note that all of our GitHub repos for the Oro products’ Enterprise Editions are only available to the logged in Enterprise users.

OroCRM Enterprise 2.6.3

The LTS maintenance release for OroCRM Enterprise Edition 2.6.3 brings the following improvements:

  • The invalid audit query has been fixed.
  • The non-minified JS file detected during the Showing related products feature test has been successfully removed.
  • Redelivery messages work properly on RabbitMQ.
  • The password recovery form has been repositioned on the page to improve user experience.

Check out the GitHub repository and release notes for the complete list of changes.

OroCRM Enterprise 2.6.2

Within this maintenance release, the broken relationship between Opportunities and Customers has been successfully fixed.

Learn more by visiting this GitHub repository and reading release notes that cover all the changes in detail.

OroCRM Enterprise 2.6.1

  • The style and functionality of minimized windows have been improved for a better user experience.
  • A new message has been created to notify users who don’t update their CRM credentials when changing email account credentials about the failed email sync.
  • The CSV import functionality has been improved so that the fields not included in the CSV file are not affected during the import.
  • Default pagination now applies to API cGET requests.
  • The application can now be installed with phpcpd bundle.
  • The export functionality has been improved to allow export of more than 5000 contacts.
  • Global organization users can now import contact records as CSV.

For further details, check out our GitHub repository and read release notes.

OroCRM Enterprise 2.3.25

  • Form label for extended relation works as intended.
  • The maximize/minimize control button works properly.
  • Additional comments are now properly displayed in the report grouped fields.

The complete list of new changes is to be found in this GitHub repository. Read  OroCRM Enterprise 2.3.35 release notes for additional information.

OroCRM Enterprise 2.3.24

  • The option closeOnSelect in Select2 library works properly.
  • Redelivery messages on RabbitMQ work as intended.
  • The invalid query of audit table has been fixed.

OroCRM Enterprise Edition 2.3.24 GitHub repo, as well as the respective release notes, will provide you with more technical details.

OroCRM Enterprise 2.3.23

  • The product attributes fields are now validated correctly.
  • The order totals are calculated properly.

This GitHub repository, as well as the respective release notes, contain more details on the improvements introduced in the maintenance release.

OroCRM Enterprise 2.3.22

  • A customer email address title is no longer displayed as an opportunity name when a new opportunity is being created.
  • The Type filter on reports created using contact address works correctly.
  • The export functionality has been improved to allow to export over 5000 contacts.

The dedicated GitHub repository and release notes provide more information on the new changes.

OroCRM Enterprise 2.0.37

  • Processing of the “calculate_root_job status” message has been improved to ensure faster results.
  • Redelivery messages on RabbitMQ work as intended.
  • Default pagination now applies correctly to API cGET requests.
  • The option closeOnSelect in Select2 works as expected.
  • The Type filter on reports created using contact address works correctly.
  • The  Outlook plugins for 2.0/2.3/2.5/master have been updated.
  • The export functionality has been improved to allow exporting of more than 5000 contacts.
  • Emails in activity lists are only visible to users authorized o see them.

For the complete list of improvements within the OroCRM Enterprise 2.0.37 maintenance release visit this GitHub repository or read the release notes.

OroCRM Enterprise 1.12.36

The maintaining release of version 1.12.36 for OroCRM Enterprise Edition provides the following fixes:

  • Websocket server restrictions have been improved
  • Filters on reports created using user status now work as expected.
  • The Type filter on reports created using contact address works correctly.

For further details check out the respective GitHub repository and view the release notes.

New OroCRM Minor Maintenance Releases

OroCRM Enterprise 2.5.5

  • The invalid query of audit table has been fixed.
  • A new message has been created to notify users who don’t update their CRM credentials when changing email account credentials about the failed email sync.
  • The export functionality has been improved to allow exporting of more than 5000 contacts.
  • The non-minified JS file detected during the Showing related products feature test has been successfully removed.
  • A customer email address title is no longer displayed as an opportunity name when a new opportunity is being created.

For the rest of improvements, check out the respective GitHub repository and read the release notes.

We believe these improvements will make your experience with OroCRM even more enjoyable.

Stay tuned for the March recap!

Back to top