OroCRM is getting better every day! Don’t take our word for it, just check this recap of improvements and bug fixes the Oro team implemented within OroCRM long-term-support (LTS) maintenance releases in April.

New OroCRM LTS Maintenance Releases

OroCRM Enterprise 2.6.11

The changes made within the maintenance release for OroCRM Enterprise 2.6.11 include the following:

Owner and Organization validators used for frontend API have been fixed.
JS validation for radio buttons now works as expected.
When a user selects country without regions, Address Region View works properly.

For the complete list of new changes, visit the respective * GitHub repository and read the 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.10

Symfony ToolBar Layout inspector has been fixed.
Dotmailer works on PostgreSQL with case sensitivity setting.
The bug related to newline character stripped from Magento Address has been fixed.
Magento addresses with street and street2 are now processed correctly.
The issue related to Magento sync creating an account with first and last names limited to 255 chars has been successfully resolved.
The primary address label is translated correctly.

To view the complete list of improvements, visit this GitHub repository and read the release notes.

OroCRM Enterprise 2.6.9

Mass sent emails are attached to a thread in the activity list of relevant contacts.
Mass sending of notifications to application users using the CLI functionality is now possible.
The issue related to user email access rights has been resolved.
The frontend functionality has been changed from FOS rest controllers to new API.

For more details, go to the respective GitHub repository and read the respective release notes.

OroCRM Enterprise 2.6.8

The notes and calls now render HTML tags correctly.
Swiftmailer stream_options are properly passed to email transport.
Grid configurations are now being updated consistently for all cases of Redis usage and allkeys-lru strategy.
IMAP for a user can now be configured properly.
When the application is installed in a subfolder, WYSIWYG editor displays as expected.
When IMAP sync for user and emails is enabled, email body is loaded as a default content-type text.
Users adding product attributes receive a notification informing that the translation cache should be refreshed after the new changes are saved.
Dotmailer works with PostgreSQL case sensitivity settings as intended.

For the complete list of improvements, check out this GitHub repository and read these release notes.

OroCRM Enterprise 2.3.30

Mass sent emails are attached to a thread in the activity list of respective contacts.
The name dictionary filter on a user report works as intended.
Dotmailer works with PostgreSQL case sensitivity settings as intended.
The issue related to newline character stripped from Magento Address has been resolved.
The primary address label is translated correctly.

To view the complete list of fixes, visit the corresponding GitHub repository and read these release notes.

OroCRM Enterprise 2.3.29

Users adding product attributes receive a notification informing that the translation cache should be refreshed after saving new changes.

This GitHub repository and the release notes will provide you with more details.

OroCRM Enterprise 2.0.38

New fields created for entities are labeled properly and are visible on relevant forms.
When email thread is imported from the mailbox, email body is displayed in HTML format.
Performance of ORM search has been improved.
Grid configurations are now being updated consistently for all cases of Redis usage and allkeys-lru strategy.
Additional comments appear in report grouped fields.

For the complete list of fixes, go to this GitHub repository and read the release notes.

That’s it for today’s recap. Stay tuned for more useful changes within the application we’ll share in early June.