ssossossosso

Release Notes

The Open-Source OroCRM for Commerce and the OroPlatform

OroPlatform 1.0.0-alpha3

Placeholders

This is ability to configurable output position for blocks. Added new twig token ‘placeholder’ which allows you to combine several blocks (templates or actions) and output them in different places in twig templates. Placeholders can be defined in any bundle in appropriate config file and then used in twig templates. More details you can find here.

Developer toolbar works with AJAX navigation requests

Now developer toolbar can be used along with navigation requests that are using AJAX.

Configuring hidden columns in a Grid

Added configuration option for the columns in Grid using which can be disabled output of this column. Data for this column will be still loaded, so you will be able to use it, for example for filtering.

Auto-complete form type

Added new form type based on Select2 to use for dynamically loaded data and customizable output.

Added “address book”

User can add multiple addresses for one entity.

Localized countries and regions

Added localized countries and regions list in default installation.

Enhanced data change log with ability to save changes for collections

Removed dependency on lib ICU

Now it is not necessary to have lib ICU installed.

Fixed issues:

fixed Twig exception “Twig_Error_Runtime: An exception has been thrown during the rendering of a template (“User Deprecated: Overwriting KnpMenuMenuFactory::buildOptions is deprecated.”
fixed issues with missing option “auto_initialize”
fixed issue with root ACL permission
fixed 500 error on optional filter for the groups roles collection “[Semantical Error] line 0, col 71 near ‘roles LIKE :’: Error: Invalid PathExpression. Must be a StateFieldPathExpression.”
fixed JavaScript error on search bar : “TypeError: queryString2 is undefined” (file searchBar.js from the searchBundle, line 104)”
fixed double generating API Key for user

Known issues

sometimes after form submit appears an error message from page state component. It happens because of improper creation of a trigger save state event. To avoid further appearing of this error just do a hard refresh in browser.