Skip to main content
Version: 2023.2

Upgrade Information

Following steps are necessary during updating to newer versions.

Upgrade to 3.1.0​

  • (only relevant if not already upgraded to version 2.6.0) [Indexing] - Filters based on the asset metadata with relations to objects which have localized fields are now indexed with all the localized values. The index structure is therefore changed (from single string to array) and it is necessary to run the migration that recreates all the indexes after updating to 3.1.0.

Upgrade to 3.0.0​

  • BEFORE UPGRADE: First upgrade to last 2.5 version and make sure all migrations are executed properly.
  • BEFORE UPGRADE: Upgrade directly to 3.1.0 if you already upgraded to 2.6 versions.
  • BEFORE UPGRADE: Activate Generate Type Declarations for PortalUser and PortalUserGroup classes and save them to regenerate the php class files. This will break portals until portal engine is upgraded to v3.0.0 via composer.
  • Removed Pimcore 6.9 support.
  • If you are upgrading to pimcore 11, then please install the pimcore/admin-ui-classic-bundle bundle.
  • [Security] Removed support of old authentication system (not setting security.enable_authenticator_manager: true in security.yaml) and related Guard authenticators.
  • [OpenId Connect] Bumped required version of openid-connect bundle to ^1.1.
  • [Elasticsearch] Removed ES 6 and ES 7 support, added ES 8 support.
  • [Elasticsearch] Changed elasticsearch client configuration.
  • Adapted installation process, see docs for details.
  • Added additional parameter for the DataPoolConfigInterface in methods of WorkspaceServiceInterface, SearchServiceInterface, FolderService and PreConditionService.
  • [Indexing] Added option to re-create index or update index via settings page
  • [DataObject][Layout] - fixed layout of Field Container (vbox is now vertical and hbox horizontal layout)
  • [Security] Changed the return type of Pimcore\Bundle\PortalEngineBundle\Service\Security\DirectEditPermissionService::getUserId to null|int.
  • [Translations] Introduced separate translation domain for frontend translations - portal-engine-frontend.
  • [Translations] Implemented PO Editor workflow for shared and admin translations (they are now under src\Resources\translations in .yaml format).

Upgrade to 2.6.0​

  • [Indexing] - Filters based on the asset metadata with relations to objects which have localized fields are now indexed with all the localized values. The index structure is therefore changed (from single string to array) and it is necessary to run the migration that recreates all the indexes after updating to 2.6.0.

Upgrade to 2.3​

  • From now on, out of the box Statistics Explorer data sources and trackers use same ES configuration as portal engine itself. If you want to change that, you need to overwrite service definition of pimcore.portal_engine.statistics_explorer.client_factory

Upgrade to 2.1.0​

  • Execute all migrations of the bundle.

Upgrade to 2.0.0​

  • First upgrade to last 1.x version and make sure all migrations are executed properly.
  • Migrate Pimcore to Pimcore 6.9
  • Migrate controller references to new naming scheme (e.g. ), for example by using migration command bin/console migration:controller-reference
  • Add following line to your firewalls configuration in the security.yml of your app after the pimcore_admin firewall.
security:
    firewalls:
        pimcore_admin: 
            # ...
        portal_engine: '%pimcore_portal_engine.firewall_settings%'
  • Clear Pimcore Caches (bin/console pimcore:cache:clear)
  • Elasticsearch mapping has changed to fix deprecations. Rebuild your index by running following commands:
bin/console portal-engine:update:index-recreate
bin/console portal-engine:update:process-index-queue