Please refer first to UPGRADE.md for the most important items that should be addressed before attempting to upgrade or during the upgrade of a vanilla Oro application.
The current file describes significant changes in the code that may affect the upgrade of your customizations.
- Service
oro_commerce_menu.namespace_migration_provider
- Services
oro_frontend.namespace_migration_provider
,oro_frontend.namespace_migration_fix_product_provider
and the logic that used them were removed.
- The field
username
was removed from/admin/api/customerusers
REST API resource. - The
frontend_owner_type
entity configuration attribute for Customer entity is set toFRONTEND_CUSTOMER
. TheFull
access level was changed toСorporate (All Levels)
for Customer entity forROLE_FRONTEND_ADMINISTRATOR
customer user role. For all other customer user roles theFull
access level was changed toDepartment (Same Level)
.
- Changes in
/admin/api/customer_user_addresses
REST API resource:- the resource name was changed to
/admin/api/customeruseraddresses
- the attribute
created
was renamed tocreatedAt
- the attribute
updated
was renamed toupdatedAt
- the relationship
frontendOwner
was renamed tocustomerUser
- the resource name was changed to
- The name for
/admin/api/customer_users
REST API resource was changed to/admin/api/customerusers
. - The name for
/admin/api/customer_user_roles
REST API resource was changed to/admin/api/customeruserroles
. - The name for
/admin/api/customer_groups
REST API resource was changed to/admin/api/customergroups
. - The name for
/admin/api/customer_rating
REST API resource was changed to/admin/api/customerratings
.
- A new email template
customer_user_welcome_email_registered_by_admin
was added. It is sent when the administrator or a customer user manager creates a new customer user with the "Send Welcome Email" option selected or when the administrator confirms a customer user from the management console.
- Removed the
oro_customer.send_password_in_welcome_email
config option to prevent issues with security when a plain password is sent by email. - There is no password provided while rendering the
customer_user_welcome_email
email template. Please update your customization of this email template. It is recommended to use a reset password link in the email template instead of a plain password.
- The
CustomerGroup::customers
relation was removed as well as other related logic.
- Added
frontend
option for datagrids. This option should be set totrue
for all datagrids are used in the store frontend. For details see Frontend Datagrids
- In case when Customer Portal is installed together with CRM, the
Account Manager
role has full permissions for Account and Contact entities. The permissions for theAccount Manager
is not changed if Customer Portal is added to already installed CRM.
- some inline underscore templates were moved to separate .html file for each template.
- removed interface
ConstraintByValidationGroups
[?]. - removed constraint class
OrderAddress
[?]. - removed constraint validator
OrderAddressValidator
[?].
- the DI container parameter
oro_customer.entity.owners
was changed- the option
local_level
was renamed tobusiness_unit
- the option
basic_level
was renamed touser
- the option
- class
RecordOwnerDataListener
[?]- constant
OWNER_TYPE_ACCOUNT
was removed, useOWNER_TYPE_CUSTOMER
instead
- constant