The system now supports the use of created_at, status, and grand_total filters in customer Orders queries, and has resolved an issue where multiple filters were not being applied correctly. Previously, running the re-index command resulted in a “Catalog Search index process error during indexation process” error when PHP was compiled with certain versions of libxml. Deleting a customer now cleans all browser session data from the storefront for logged-in and deleted customers as expected. Previously, it was returning an empty result set when the category preview page was requested. Previously, expanding the ‘Image and Videos’ tab first resulted in the folder tree not being displayed and an error message when attempting to upload an image in the WYSIWYG editor. PHPSESSID no longer regenerates on POST requests on frontend area for a logged-in customer https://best-adobe-commerce-cloud-agencies.com/ if L2 Redis cache is enabled and the customer was updated from the backend
- Previously, these references were causing errors due to the absence of the referenced files.
- Checkout performance has been improved when attributes used in cart price rules conditions are not present for all products and when MAP (Minimum advertised price) feature is enabled.
- The system now ensures consistent image zoom functionality on mobile devices, providing a smooth and predictable user experience.
- As a result, this process should be as automated as possible.
- Your development team should review and resolve all critical errors before proceeding.
Previously to this fix, if the preview image name was missing for a pagebuilder template, the pub/media folder was deleted. Now, the correct count is displayed in both the “Time Used” reflecting the desired values with multi shipping. Now, with HTML minification enabled, the order from admin can be placed successfully. Previously, the authorization transaction was not appearing in the Transaction tab after clicking the “Authorize” button, and no new transaction of type “Authorization” was created. Now, This issue has been resolved, ensuring that TinyMCE 6 operates smoothly without generating any errors, even when JS minification is enabled.
Previously, any error messages within cron processes were not recorded, and STDERR and STDOUT for cron groups running in separate processes were lost. The system now correctly applies a 4-space indent to the composer and auth.json files, following a fix to a syntax error in the editorconfig. Earlier Customer grid was updated instantly but after the fix Customer grid is updated after cron run but not reflect instantly.
Related Services
Previously, the ‘created_at’ field was displayed in the +0 timezone, regardless of the customer’s configured timezone. The system now correctly displays the ‘created_at’ field from shipment comments in the customer’s configured timezone when using the customer Orders query. Previously, attempting to import a product CSV file with special characters would result in an error, preventing the import process. The system now correctly validates and imports product CSV files containing special characters, allowing for successful data transfer. Restricted admin users can now consistently view and manage customers and all shared catalogs to which the products are assigned, provided they have access to the specific store.
Who is this guide for?
Missing error messages are now displayed correctly. This enables easier completion of multiple actions simultaneously and reduces the need for merchandising teams to navigate. This allows teams to set it up and use commands just as they would with Redis. Development teams should review custom modules for these changes early in the development process. On the frontend and admin side, Chart.js is now updated to version 4.5.0.
Previously, an incorrect type error was thrown when encountering an empty LESS file during deployment. Previously, the removal of the Initialization Helper from the constructor in the ProductRepository class resulted in a loss of backward compatibility, forcing users to employ a workaround. The system now consistently handles exceptions between developer and production modes, preventing unexpected redirection to the login page when an exception is thrown. Previously, running the ChangelogBatchWalker on multiple threads would lead to the deletion of tables used by other threads, causing an error during indexer execution. The system now supports process fork for MView indexation, preventing errors during indexer execution when operating on multiple threads. The system now successfully completes the re-index command without encountering any errors, regardless of the libxml version compiled with PHP.
Previously, updating a large number of prices using this endpoint could result in performance issues and site unresponsiveness. The new default ensures that indexers are in the recommended configuration, improving system performance and reducing potential issues. Before upgrading to RabbitMQ 4, Adobe Commerce Cloud and on-premises customers must migrate from classic mirrored queues to quorum queues. When planning your upgrade to Adobe Commerce 2.4.8, consider your business priorities, current version, and plans to adopt the new Adobe Commerce as a Cloud Service. Adobe Commerce (PaaS/On-Prem) offers extensive customization and superior B2B features but has higher TCO and longer implementation. B2B features include custom pricing, quote negotiation, approval workflows, and shared catalogs.
Most certifications can be renewed automatically for two years at no cost by passing two short renewal modules (about 15 minutes each). This matters because CVSS alone should not determine remediation priority. Adobe reports that successful exploitation could ultimately result in arbitrary code execution. It is also classified as an incorrect authorization vulnerability with potential for arbitrary code execution.
Previously, setting a product to ‘Out of Stock’ would result in an empty space appearing in the product listing, disrupting the layout and potentially confusing customers. Previously, users were unable to add a Map content block due to compatibility issues with the Google Maps API version, resulting in a “something went wrong” error message. Resolved the issue with the original_row_total field, which was returning incorrect values when custom options were selected Previously, header processing was executed even if the header value did not pass validation, leading to potential vulnerabilities and unexpected behavior due to double processing of header values. After the fix locked values set from cli with –lock-env or –lock-conf cannot be updated anymore.
Web Designer III Rycca Bicksteth, hailing from Smith-Ennismore-Lakefield enjoys watching movies like Catch .44 and Worldbuilding. Took a trip to Abbey Church of Saint-Savin sur Gartempe and drives a Aston Martin DB3S.