Upgrade Information

Following steps are necessary during updating to newer versions.

Upgrade to 3.3.3

• The bundle no longer registers StatisticsController routes under /pimcore-statistics-explorer and /admin/pimcore-statistics-explorer, and no longer registers the route names pimcore_statisticsexplorer_statistics_*, pimcore_statistics_explorer_load_configs, pimcore_statistics_explorer_load_config and pimcore_statistics_explorer_save_config. If your application used these routes, register the controller yourself, see Setup Routes.
• If your routing.yml imports @PimcoreStatisticsExplorerBundle/Controller (the former Setup Routes example), it also mounts the custom report and Pimcore Studio controllers under your prefix. Import @PimcoreStatisticsExplorerBundle/Controller/StatisticsController.php instead.
• The custom report endpoints of Pimcore Admin Classic (statistics_explorer_custom_reports_*) are now served at /admin/statistics_explorer_custom_reports/... and require the reports_config permission.
• StatisticsController returns 403 for the data sources, data, field collection and field settings actions of a context without a user provider, for example customreports. Only users of the context see the users and roles to share configurations with. The controller does not check who is logged in: Portal Engine protects its routes (/_portal-engine/stats/...) itself, so also update Portal Engine to its next bugfix release.
• The Pimcore Studio endpoints for data sources and fields of the custom report adapters require the reports_config permission.
• Saving and deleting a configuration require a logged-in user. Loading, saving and deleting only accept configurations of the context in the URL.
• Global configurations and configurations from LoadConfigurationEvent listeners that belong to another context are no longer loaded or listed. Those without a context are used for the requested context.
• Configurations saved without a logged-in user have no owner (ownerId IS NULL in bundle_statistics_explorer_configuration) and are listed as global configurations. Review and remove those you did not create on purpose.
• Sort directions in the field settings only accept asc and desc, the order key of aggregations only accepts _key and _count, and the result size (max) only accepts positive integers. Other values fall back to the defaults (MySQL lists now return up to 500 rows instead of none when max is missing).

Upgrade to 2.0.0

• Removed support for Elasticsearch 6 and 7, added Elasticsearch 8 support
• Changed Elasticsearch client configuration, details see Configuration.

Upgrade to 1.3.0

• Execute all migrations of the bundle.

Upgrade to Pimcore X

• Update to latest (allowed) bundle version in Pimcore 6.9 and execute all migrations.
• Then update to Pimcore X.