Release 2.4.6-p7-15.13
TAG: R2.4.6-p7-15.13
branch: main
Release date: September 2024
This release upgrades version R2.4.5-p1-13.9
Introduction
As you note from the update numbering, this version skips one Cloudscraper version. This is correct, and intentional. The 14th release of the software system was an update to Magento 2.4.5-p5. Since there is a major version upgrade from Magento available (2.4.6) we chose to upgrade to the newer Magento version.
One of the major issues we came across switching to version 2.4.6 was the removal of the Zend framework. A number of the extensions we use were not upgraded for this yet. Therefore, we have created a number of small Cloudscraper modules that fix these discrepancies.
The fix is actually simple, as the Zend framework is replaced by the Laminas framework.
The modules are:
- BSS Commerce Popup module
- Mageplaza PdfCreator
- ElasticSuite Blog
- Shoppingfeeder
Updates
Page not found 404
On mobile devices the layout was incorrect. The font size was too big to have the layout fit on the smaller screens of phones. This has been corrected.
Customer lock out
We’ve developed a module that enables assigning a customer to the ‘locked’ customer group. Upon assignment, these users are prohibited from logging into the system. While this may seem like an odd feature, it was necessary to implement due to certain users exhibiting improper behavior, and thus needed a mechanism to prevent system contamination.
In order to utilize this feature, an administrator is required to establish the ‘locked’ customer group within the Magento back-end. Following this setup, users, denoted as customers, can then be designated to this group.
Translations
Testing revealed that in case of an error during the payment process, the message always comes back in English, even when the site was in Dutch. This is corrected. The Dutch translation is added.
CSP preparations
The CSP (Content Security Policy) implementation is becoming stricter and essential with the Magento 2.4.7 release. As a result, we have activated the CSP module in this version and established a unique whitelist for components necessary to ensure the platform operates correctly.
Captcha on blog comments
In the past, we allowed guests to comment in our blog section. But recently, too many malicious entries have been attempted in our comment section. As a counter measure, we stopped allowing guests to comment. But, as we are in a free world, we think this is too strict. So, in this version we have added a captcha on the comment section of our blog to keep out the unwanted comments.
Shoppingfeeder observer
With the move to 2.4.6-p7 and the newer version of the Shoppingfeeder extension, the compiler yielded an error in the observer code that we had created to resolve the Zend references in Shoppingfeeder. The compiler complains about an argument type that is expected but used differently.
We rewrote the observer code such that it completely replaces the original observer code. Our version uses dependency injection to avoid the use of creation of objects, and it has been refactored to be more efficient. On top of that, all variables used in the observer code have been set to private variables rather than protected.
Bugfixes
Shipments in customer account not visible
When a customer is logged in and retrieves the details of an order from the order history, it appeared the shipments for the order were not visible anymore. We corrected this, and you can also view the shipment details on past orders.
Release notes
We fixed the incorrect links that lead to a “Page not found - 404” error in the release notes site.
Payment test system
The database we use in the development version has been changed. Therefore, the payment test system is now instructed to use the new development database.
New
GLS carrier tracking
We added another carrier as a module to the system. With this module, you can choose GLS as a carrier, fill in the tracking code, and the correct link with all data necessary is created and used in transactional mails, but also in the backend of the system for both the user and admins.
Opensearch
With Magento version 2.4.6 we move to Opensearch for our internal search engine. This requires to setup Opensearch on the server. Setup is easy, you can find the details below with a link to the Hypernode release information where the developers explain what to do on the Hypernode.
We continue to use ElasticSuite on top of Opensearch to offer a richer search experience.
Essentials for release
- Temporarily switch off cron.
- With Magento 2.4.6 we moved to Opensearch.
- See: Hypernode information
- Activate Opensearch
- Verify the search engine settings in the backend
- Verify the indexes have been cleared and re-instated.
- Verify the search engine yields results.
- Switch on cron.
- Create new sitemaps in pub/sitemaps.
- Warm cache after the software is released.
Goto the webstore release notes site