Releases: plentymarkets/plugin-io
Releases · plentymarkets/plugin-io
5.0.43
v5.0.43 (2021-11-30) Overview of all changes
Fixed
- We fixed an error in the CategoryService.
v5.0.42 (2021-11-15) Overview of all changes
Changed
- The meta data for files in the webspace are now collected from the plentymarkets core, which leads to an improved TTFB.
- Additional category data is now loaded via the lazyloader, in order to reduce database traffic.
- The performance of data procurement for linked variations in ShopBuilder has been improved.
Fixed
- Invalid items were not removed from the shopping cart when a user changed the country of delivery. This has been fixed.
- The data of properties is now correctly displayed for items in Last seen item lists.
- If errors occur during the initialisation of the context classes, the corresponding page is no longer cached in ShopBooster.
5.0.42
v5.0.42 (2021-11-15) Overview of all changes
Changed
- The meta data for files in the webspace are now collected from the plentymarkets core, which leads to an improved TTFB.
- Additional category data is now loaded via the lazyloader, in order to reduce database traffic.
- The performance of data procurement for linked variations in ShopBuilder has been improved.
Fixed
- Invalid items were not removed from the shopping cart when a user changed the country of delivery. This has been fixed.
- The data of properties is now correctly displayed for items in Last seen item lists.
- If errors occur during the initialisation of the context classes, the corresponding page is no longer cached in ShopBooster.
5.0.41
v5.0.41 (2021-10-20) Overview of all changes
Fixed
- Package components are now added to the shopping cart with the correct quantity if the option Replace item package with basic item is active.
- When adding set items to the shopping cart, the set components were not included the first time. This has been fixed.
- Due to an error, no value was displayed for order properties of the type Selection. This has been fixed.
- When a value was selected from the category facet, it was not displayed as selected.
5.0.40
v5.0.40 (2021-10-05) Overview of all changes
ToDo
- In order to provide the redirect upon detected diverging browser langage to your customers, you need to implement the ShopBuilder widget Language detection.
Changed
- plentyShop is now able to react to a future order setting with which prefixes for item bundles and components can be customised. Note that changing these prefixes may lead to a faulty display of older orders.
- The redirect for automatic browser language detection has been deactivated.
Fixed
- Tag result pages were not always treated as search result pages. This behaviour has been fixed.
5.0.39
v5.0.39 (2021-09-13) Overview of all changes
Changed
- It's no longer possible to send the contact form if reCaptcha is active and the corresponding cookie was not accepted by the user.
5.0.38
v5.0.38 (2021-08-31) Overview of all changes
Changed
- For the changing of payment methods, the
accessKey
for the order is now also passed.
5.0.37
v5.0.37 (2021-08-17) Overview of all changes
Fixed
- The pagination on the results page of a tag route was partially faulty. This has been fixed.
- The pagination on the search results page was partially faulty. This has been fixed.
5.0.36
v5.0.36 (2021-08-05) Overview of all changes
Changed
- Category data is now loaded via new interfaces in order to improve performance.
- The loading of customer data, the shopping cart, and shopping cart items are now subsumed under a single query.
Fixed
- The correct canonical URL is now generated for the homepage category.
5.0.35
v5.0.35 (2021-07-13) Overview of all changes
Fixed
- It was not possible to save an empty string in the input field Thousands separator if the option No had been selected for the setting Use customer-specific price format in then number formats section of the IO settings. This has been fixed.
- An incorrect canonical URL was used for the search results page. This has been fixed.
5.0.34
v5.0.34 (2021-06-28) Overview of all changes
Changed
- When creating and updating addresses, the field Email can now be used to influence address options.