e.sy History Log
Description
Highlights
- Comprehensive change history: Records all changes to Shopware data (Currently, the entities of the Shopware default settings are not captured because a different structure/technique is used. We are working to implement this feature as quickly as possible.)
- Additional tab: Easy display of history in customer and product overviews
- Central management: Quick and easy configuration of the change history
- Maximum flexibility: Tracks all database entries without limitations
Features
- Records all changes stored in the database
- Integration of an additional history tab for customers and products
- Clear interface for configuration and evaluation
- No restrictions on specific areas/functions within the system
- User-friendly management and analysis of data history
- Seamless traceability of important data changes
- Optimized performance and easy handling
- Compatibility with all common Shopware versions
- Regular updates and continuous development
About the Extension
Whether corrected product texts, customer data, price adjustments, changes in shipping, or new images in products or in shopping experiences – e.sy History Log allows a complete change history and seamless tracking and management.
The plugin automatically creates a comprehensive, detailed change history of all user-defined Shopware data. All changes of database entries can be recorded and documented accordingly. Through a central interface, the data to be recorded in e.sy History Log can be quickly and easily configured, providing a change history tailored to individual needs.
This clearly arranged history can be easily viewed via an additional tab in the customer data and product overview.
The plugin has a central interface that allows for convenient configuration of data recording. e.sy HistoryLog offers unlimited flexibility and numerous application possibilities.
What makes e.sy History Log special?
With our extension, you are not limited to specific endpoints in Shopware. This allows you to track all information in a customized manner.- Media
- Themes
- Vouchers / Discounts
- Plugin Configurations
- Settings (currently, the entities of the Shopware default settings are not captured because a different structure/technique is used. We are working to implement this feature as quickly as possible.)
- Properties
- Manufacturers
- Plugin Configuration
- Shopware Settings
How does e.sy History Log work?
Plugin Settings
Under “Settings > Extensions > Esy - Entity Change History,” you can view and configure the following options:
1. All Changes
2. Entity Settings
3. Property Mapping
All Changes
Here, you can view all changes made to entities. You can search for a specific entity or ID using the general search function. Additionally, there are advanced filter options in the right-hand sidebar, such as limiting results to a specific time period. The list of changes also displays which user made the change, and if the change is language-specific (e.g., product description), the language in which the change was made will also be shown.
Entity Settings
Here, you can configure whether changes to each entity in Shopware should be logged and how long they should be stored. The storage duration must be specified in seconds, but for readability, it is converted and displayed in minutes, hours, and days.
By default, all entities (except for mapping entities such as product_category) are logged by the plugin. However, there are fixed exceptions that the plugin does not log:
EsyEntityChangelog
With each change recorded by the plugin, an entry is created in the EsyEntityChangelog. Without this exception, the plugin would enter an infinite loop.
Plugin
When the plugin is installed, the subscriber that tracks all changes is activated. However, the necessary database tables do not yet exist at that time. Without this exception, the plugin installation would fail.
ScheduledTask
During the execution of scheduled tasks, values are regularly changed. Without this exception, the plugin would log these changes every time.
Property Mapping
For example, when the manufacturer of a product is changed, only the ID of the manufacturer changes in Shopware. To prevent cryptic IDs from being displayed in the change history, you can specify which property should be displayed instead.
You can decide whether the mapping should be applied only to specific entities, such as manufacturer changes, or to all entities. Then, using “Reference Entity,” you select the entity that should be displayed in the change. Under “Property,” you specify the entity property that should be shown instead of the ID. This property can be specified in the same way as in API calls, where the field is used in filters.
Changes to the property mapping only affect new entity changes.
Whether corrected product texts, customer data, price adjustments, changes in shipping, or new images in products or in shopping experiences – e.sy History Log allows a complete change history and seamless tracking and management.
The plugin automatically creates a comprehensive, detailed change history of all user-defined Shopware data. All changes of database entries can be recorded and documented accordingly. Through a central interface, the data to be recorded in e.sy History Log can be quickly and easily configured, providing a change history tailored to individual needs.
This clearly arranged history can be easily viewed via an additional tab in the customer data and product overview.
The plugin has a central interface that allows for convenient configuration of data recording. e.sy HistoryLog offers unlimited flexibility and numerous application possibilities.
What makes e.sy History Log special?
With our extension, you are not limited to specific endpoints in Shopware. This allows you to track all information in a customized manner.- Media
- Themes
- Vouchers / Discounts
- Plugin Configurations
- Settings (currently, the entities of the Shopware default settings are not captured because a different structure/technique is used. We are working to implement this feature as quickly as possible.)
- Properties
- Manufacturers
- Plugin Configuration
- Shopware Settings
How does e.sy History Log work?
Plugin Settings
Under “Settings > Extensions > Esy - Entity Change History,” you can view and configure the following options:
1. All Changes
2. Entity Settings
3. Property Mapping
All Changes
Here, you can view all changes made to entities. You can search for a specific entity or ID using the general search function. Additionally, there are advanced filter options in the right-hand sidebar, such as limiting results to a specific time period. The list of changes also displays which user made the change, and if the change is language-specific (e.g., product description), the language in which the change was made will also be shown.
Entity Settings
Here, you can configure whether changes to each entity in Shopware should be logged and how long they should be stored. The storage duration must be specified in seconds, but for readability, it is converted and displayed in minutes, hours, and days.
By default, all entities (except for mapping entities such as product_category) are logged by the plugin. However, there are fixed exceptions that the plugin does not log:
EsyEntityChangelog
With each change recorded by the plugin, an entry is created in the EsyEntityChangelog. Without this exception, the plugin would enter an infinite loop.
Plugin
When the plugin is installed, the subscriber that tracks all changes is activated. However, the necessary database tables do not yet exist at that time. Without this exception, the plugin installation would fail.
ScheduledTask
During the execution of scheduled tasks, values are regularly changed. Without this exception, the plugin would log these changes every time.
Property Mapping
For example, when the manufacturer of a product is changed, only the ID of the manufacturer changes in Shopware. To prevent cryptic IDs from being displayed in the change history, you can specify which property should be displayed instead.
You can decide whether the mapping should be applied only to specific entities, such as manufacturer changes, or to all entities. Then, using “Reference Entity,” you select the entity that should be displayed in the change. Under “Property,” you specify the entity property that should be shown instead of the ID. This property can be specified in the same way as in API calls, where the field is used in filters.
Changes to the property mapping only affect new entity changes.
Details
- Available: English, German
- Latest update: 6 December 2024
- Publication date: 17 September 2024
- Version: 2.0.2
- Category: Administration
Resources
Reviews (0)
About the Extension Partner
bgp e.media GmbH
Partner Status
-
Shopware
Extension Partner
Details
-
Ø-Rating:
5
Average rating of 5 out of 5 stars
- Partner since: 2020
- Extensions: 6
Support
- Based in: Germany
- Speaks: German, English
Installation via Plugin Manager
How does e.sy History Log work?
Plugin Settings
Under “Settings > Extensions > Esy - Entity Change History” you can view and configure the following options:
1. All Changes
2. Entity Settings
3. Property Mapping
All Changes
Here, you can view all changes made to entities. You can search for a specific entity or ID using the general search function. Additionally, there are advanced filter options in the right-hand sidebar, such as limiting results to a specific time period. The list of changes also displays which user made the change, and if the change is language-specific (e.g., product description), the language in which the change was made will also be shown.Entity Settings
Here, you can configure whether changes to each entity in Shopware should be logged and how long they should be stored. The storage duration must be specified in seconds, but for readability, it is converted and displayed in minutes, hours, and days.
By default, all entities (except for mapping entities such as product_category) are logged by the plugin. However, there are fixed exceptions that the plugin does not log:
EsyEntityChangelog
With each change recorded by the plugin, an entry is created in the EsyEntityChangelog. Without this exception, the plugin would enter an infinite loop.
Plugin
When the plugin is installed, the subscriber that tracks all changes is activated. However, the necessary database tables do not yet exist at that time. Without this exception, the plugin installation would fail.
ScheduledTask
During the execution of scheduled tasks, values are regularly changed. Without this exception, the plugin would log these changes every time.
Property Mapping
For example, when the manufacturer of a product is changed, only the ID of the manufacturer changes in Shopware. To prevent cryptic IDs from being displayed in the change history, you can specify which property should be displayed instead.
You can decide whether the mapping should be applied only to specific entities, such as manufacturer changes, or to all entities. Then, using “Reference Entity,” you select the entity that should be displayed in the change. Under “Property,” you specify the entity property that should be shown instead of the ID. This property can be specified in the same way as in API calls, where the field is used in filters.
Changes to the property mapping only affect new entity changes.
1.0.3
- fix: Text overflow in changelog comparison
2.0.2
- fix: Text overflow in changelog comparison
1.0.2
- change: Default ChangelogDisplayType changed to Diff
- fix: Added missing userName for other Context Source types
2.0.1
- change: Default ChangelogDisplayType changed to Diff
- fix: Added missing userName for other Context Source types
1.0.1
fix: Empty dropdown field in PropertyMapping Modal
2.0.0
Release Version for Shopware 6.6
1.0.0
Release Version for Shopware 6.5