Cloudscraper Software - Magento 2 development

How to use and develop the Cloudscraper system

Release 2.4.3-3.1

TAG: R2.4.3-C3.1

branch: main

Release date: September 23rd 2021

This release upgrades version R2.4.3-C3.0

Contents

New in this version

This release is an internal release for the public. This means the release only contains updates from the Cloudscraper development team.

Frequently asked questions

We have added an extra item to the “about us” menu: frequently asked questions. In the section, we collect issues that our customers or we came across when using the platform. Where possible, we include solutions or workarounds for the problems. We will extend the section with new subjects over time.

We maintain the FAQ content in app/code pages.xml and the individual HTML files that hold the actual content. We define the menu addition in the app/code blocks.xml file.

You need to add the URL rewrites for the faq pages in the database. We maintain the code for this in sqlInsertCustomUrlRewrites.sql.

Maintaining the FAQ in this fashion ensures that you can always restore the data when someone accidentally removes the pages from the system. This way, the pages become part of the installation package.

Home pages services block

In the “Services Block” on the home pages we added button functionality so the icons now work as a button, and point to relevant information.

Icon for account menu

We have added an icon to the user account menu button in the top-right corner of the desktop version of the platform.

Asynchronous Message Queue

The system log contains many (informational) messages about the asynchronous message queue. We have disabled the Magento Web Api Async module (magento/module-webapi-async):

bin/magento module:disable Magento_WebapiAsync

On a development platform, you need to perform a rebuild after you disable the module. Disabling the module updates the config.php file of the system. As a result, the module will not be used when deploying the platform for the new version.

robots.txt corrected

Google Merchant Center showed numerous errors on the product feed we produce every night. We have added some lines to the robots.txt file to allow Google to correctly handle the links as they appear in the feed.

Essentials for release

  1. After deployment, you need to import the blocks and pages.
  2. Check that you have the URL rewrites for the Dutch and English FAQ pages defined correctly in the backend.
  3. Robots.txt update: the repository has the file and the appropriate symlink. No further action required.
  4. Remove old robots.txt data: Content -> Design Configuration -> Webstore - remove robots.txt content.
  5. Check: Verify the robots.txt file

Goto the webstore release notes site

Home