adobedocs/commerce-operations.en

Content for Adobe Commerce system administration documentation on Experience League

Adobe Commerce technical documentation

We welcome contributions from the community as well as from Adobe employees from outside the documentation teams.

Adobe Open Source Code of Conduct

This project has adopted the Adobe Open Source Code of Conduct or the .NET Foundation Code of Conduct. For more information, see the Contributing article.

About your contributions to Adobe content

See the Adobe Docs Contributor Guide.

How you contribute depends on who you are and the sort of changes you'd like to contribute:

Minor changes

If you are contributing minor updates, visit the article and click the feedback area that appears at the bottom of the article, click Detailed feedback options, and then click Suggest an edit to go to the markdown source file on GitHub. Use the GitHub UI to make your updates. See the general Adobe Docs contributor guide for more information.

Minor corrections or clarifications you submit for documentation and code examples in this repo are covered by the Adobe terms of use.

Major changes or new articles from community members

If you're part of the Adobe community and you want to create a new article or submit major changes, please use the Issues tab in the Git repository to submit an issue to start a conversation with the documentation team. Once you've agreed to a plan, you'll need to work with an employee to help bring that new content in through a combination of work in the public and private repositories.

Major changes from Adobe employees

If you are a technical writer, program manager, or developer from the product team for an Adobe Experience Cloud solution and it's your job to contribute to or author technical articles, you should use the private repository at https://git.corp.adobe.com/AdobeDocs.

Tools and setup

Community contributors can use the GitHub UI for basic editing or fork the repo to make major contributions.

See the Adobe Docs Contributor Guide for details.

How to use markdown to format your topic

All the articles in this repository use GitHub flavored markdown. If you are not familiar with markdown, see:

• Markdown basics
• Printable markdown cheatsheet

Templates

For some topics, we use data files and templates to generate published content. Use cases for this approach include:

• Publishing large sets of programmatically generated content
• Providing a single source of truth for customers across multiple systems that require machine-readable file formats, such as YAML, for integration (e.g., Site-Wide Analysis Tool)

Examples of templated content include, but are not limited to, the following:

• CLI tools reference
• Product availability tables
• System requirements tables

Generate templated content

In general, most writers only need to add a release version to the product availability and system requirements tables. Maintenance for all other templated content is either automated or managed by a dedicated team member. These instructions are intended for most writers.

NOTE:

• Generating templated content requires working on the command line in a terminal.
• You must have Ruby installed to run the rendering script. See _jekyll/.ruby-version for the required version.

See the following for a description of the file structure for templated content:

• _jekyll—Contains templated topics and required assets
• _jekyll/_data—Contains the machine-readable file formats used to render templates
• _jekyll/templated—Contains HTML-based template files that use the Liquid templating language
• help/_includes/templated—Contains the generated output for templated content in .md file format so it can be published in Experience League topics; the rendering script automatically writes generated output into this directory for you

To update templated content:

1. In your text editor, open a data file in the /jekyll/_data directory. For example:

   • Product availability tables: /jekyll/_data/product-availability.yml
   • System requirements tables: /jekyll/_data/system-requirements.yml

2. Use the existing YAML structure to create entries.

   For example, to add a version of Adobe Commerce to the product availability tables, add the following to each entry in the extensions and services sections of the /jekyll/_data/product-availability.yml file (modify version numbers as needed):

   support:
      - core: 1.2.3
        version: 4.5.6
   

3. Navigate to the _jekyll directory.

   cd _jekyll
   

4. Generate templated content and write the output to the help/_includes/templated directory.

   rake render
   

   NOTE: You must run the script from the _jekyll directory. If this is your first time to run the script, you must install Ruby dependencies first with the bundle install command.

5. Navigate back to the root directory.

   cd ..
   

6. Verify that the expected help/_includes/templated files were modified.

   git status
   

   You should see output similar to the following:

   modified:   _data/product-availability.yml
   modified:   help/_includes/templated/product-availability-extensions.md
   

7. Push your changes.

   git add
   git commit -m "_descriptive message of the intended commit_"
   git push
   

See the Jekyll documentation for more details on Data Files, Liquid filters, and other features.

commerce-operations.en's Issues

Bug report: test

Description

Steps to reproduce

1. First Step
2. Second Step
3. Etc.

Expected result

Possible solutions

Additional information

GJSS TEST ISSUE (AMY) GITHUB TO JIRA

GJSS Test Issue to export Jira issues to Github

Global Search is not working on this page for Firefox mac os

Issue in ./help/release/release-notes/commerce/2-4-5.md

attached the video for evidence

https://www.awesomescreenshot.com/video/14946938?key=8e1fc60ba130c9af991f16e54eb6d79b

Error on sql query

Issue in ./help/implementation-playbook/best-practices/maintenance/commerce-235-upgrade-prerequisites-mariadb.md

Where it says:

SELECT table_name, row_format FROM information_schema.tables WHERE table_schema=DATABASE() and row_format 'Compact';
should say:
SELECT table_name, row_format FROM information_schema.tables WHERE table_schema=DATABASE() and row_format = 'Compact';

(note the '=' added)

Regards

GJSS TEST ISSUE #2

Topic Link

Description

Possible solutions

Additional information

Integrate S3 remote-storage with fastly is poorly described

It appears that the documentation provided for configuring remote storage using Magento Cloud and Fastly is insufficient and confusing.
The paragraph in the Magento documentation regarding Fastly configuration simply refers to the Fastly Magento 2 Module, which is intended for shops that want to bring in specific URL prefixes, rather than providing clear instructions on how to configure remote storage.

Additionally, the links provided in the Magento documentation to docs.fastly.com and developer.fastly.com do not offer further clarification on the topic.

It is unclear how someone is supposed to understand and successfully implement this configuration based on the current documentation.

Feature request - Stop GEO locate by IP AND browser language in Experience League devdocs for Magento

Description

Stop choose what language I will get. Most of us professional developers reads technical documentation in English. I think there is less than 1% that enjoys reading technical documentations in their own language as most of development environments is in english.

Expected result

To choose by my self if I want to translate the site to Swedish or other languages.

Benefits

The benefits is obviously that its easier to grasp the content when its in correctly english than a localized version that translates words poorly.

Possible solutions

Stop automatic translation both by IP and browser language

Additional information

I think i provided enough information to make it clear that a person should be in charge of what language he och she prefers.

Mismatching versions & instructions

Issue in ./help/upgrade/implementation/perform-upgrade.md

This page should be overhauled. It refers to update methods going back to 2.4.1 and also examples and commands have mismatched versions

Example - Minor release
Text refers to 2.4.3 :
Minor releases contain new features, quality fixes, and security fixes. Use Composer to specify a minor release. For example, to specify the Magento Open Source 2.4.3 metapackage:

Instruction refers to 2.4.0
composer require-commerce magento/product-community-edition 2.4.0 --no-update

Example - Quality patch
Text refers to 2.4.1 :
Quality patches primarily contain functional and security fixes. However, they can sometimes contain new, backward-compatible features. Use Composer to download a quality patch. For example, to specify the Magento Open Source 2.4.1 metapackage:

Instruction refers to 2.4.3
composer require-commerce magento/product-community-edition 2.4.3 --no-update

And so on. ALL examples should be updated to refer to a SINGLE commerce version. EG 2.4.6 (as latest)

Also 'composer require-commerce' method throws an error when executed on Composer 2.

Deprecation Notice: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /private/var/www/abb-motions-ecommerce-frankfurt/vendor/magento/composer-root-update-plugin/Utils/PackageUtils.php:128
Deprecation Notice: VersionSelector::findBestCandidate with ignored platform reqs as bool|array is deprecated since Composer 2.2, use an instance of PlatformRequirementFilterInterface instead. in phar:///usr/local/Cellar/composer/2.4.4/bin/composer/src/Composer/Package/Version/VersionSelector.php:80

Normally I use 'composer update magento/product-enterprise-edition' version

Finally, updating on Cloud is slightly different too. This should be mentioned.

No link provided.

Issue in ./help/commerce-at-scale/caching.md

The last line "An example manual cache clear operation for AEM and Adobe Commerce is shown here." of https://experienceleague.adobe.com/docs/commerce-operations/deliver-commerce-at-scale/caching.html?lang=en has no any link for "shown here".

GJSS TEST ISSUE #1

Description

Content checklist

• The topic provides an explanation of how ____ works.
• The topic provides steps for ____.
• The topic contains code samples that shows ____.
• Other (please specify)

Additional information

How to use field node source_service option on system.xml ?

Topic Link

https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/files/config-reference-systemxml.html?lang=en

Description

In the official documentation, the field node has source_service, but there is no example of how to use it, and there is no place for using it in the framework vendor. How to use this?

COMDOX-372: test issues board

This issue is a test for the backlog project.

Share more specifications on benchmarks.md

Description

The benchmarks.md article leaves some open questions about the testing conditions.

Expected result

As much detail as possible about the testing conditions are specified....

• Which payment method was used to place orders?
• Which shipping methods was used?
• How was tax calculation handled?
• Was reCAPTCHA enabled during order placement?
• Were any extensions installed on the storefront (I assume no, but it would be good to explicitly specify this)

These lab conditions, while they sound good on paper, are likely not reality for any merchants -- it would be interesting if there were a few permutations of benchmarks showing how the system performed under different condition. FYI we did publish some real world benchmarks about a year ago: https://www.rightpoint.com/thought/article/high-scale-adobe-commerce-in-the-wild

Benefits

Ensures clarity and understanding of the data presented.

Possible solutions

As much detail as possible about the test conditions is provided.

Typo On Page

Issue in ./help/implementation-playbook/planning/ownership.md

RASI Framework - title should say RACI Framework

Request for documentation on models in Magento 2

Description:

As a developer working with Magento 2, I have found that the documentation on models is somewhat lacking. While there are some resources available on the Magento 2 developer documentation website, I believe that more in-depth documentation would be beneficial for those looking to use models in their custom extensions and customizations.

Models are an important part of Magento 2, as they allow developers to interact with the database and perform various actions such as retrieving and saving data. However, the current documentation does not provide enough information on how to use models effectively, and I have had to rely on community resources and trial and error to learn how to use them.

I am requesting that the Magento 2 documentation team consider adding more comprehensive documentation on models, including best practices, examples, and troubleshooting tips. This would greatly improve the developer experience and make it easier for developers to use models in their projects.

Thank you for your consideration.

Steps to reproduce:

N/A

Expected result:

Improved documentation on models in Magento 2

Actual result:

Limited documentation on models in Magento 2

SWAT agent install script uses wrong domain

Issue in ./help/tools/site-wide-analysis-tool/installation.md

The script mentioned in the scripted install is using the outdated domain updater.swat.magento.com (line 12), which is not working (https://updater.swat.magento.com/launcher/launcher.linux-amd64.tar.gz), instead of the new one - updater.supportinsights.adobe.com.

https://raw.githubusercontent.com/magento-swat/install-agent-helpers/main/install.sh

Thank you for updating this.

Config guide: system.xml Tab type options need review

Topic Link

https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/files/config-reference-systemxml.html#tab-attribute-reference

Description

This issue is based on magento/devdocs#9554

Error message states "Element 'tab' attribute 'type' is not allowed."

Possible solutions

Investigate system.xml Tab attributes to confirm correct configuration options; correct topic as needed.

Cloud Commerce Does Not Have Anti-Virus

Issue in ./help/implementation-playbook/infrastructure/cloud/managed-services.md

The first image indicates that Cloud Commerce has Anti-Virus - it does not. It is not part of the architecture, this should be removed

Remove conflicting statements in High Throughput Processing

There's a conflicting statement in this document:

'All features work independently. You can use all the features simultaneously or enable and disable features in any combination.'

However, under 'Negotiable Quote Async Order', there is a dependancy on two items to be used together, as stated:

The Negotiable Quote Async Order B2B module enables you to save order items asynchronously for the NegotiableQuote functionality. You must have AsyncOrder and NegotiableQuote enabled.

The dependancy on having Negotiable Quote Order Async is both Async Order, and Negotiable Quotes.

Suggested remediation of the statement:
I'd suggest removing 'All features work independently. You can use all the features simultaneously or enable and disable features in any combination.' altogether, and have the documentation speak for itself as the statement of using all independently isn't valid, and is dependant on another condition being enabled before Negotiable Quote Order Async can be used.

Issue in ./help/performance/high-throughput-order-processing.md

Broken links in Search engine overview page

Issue in ./help/configuration/search/overview-search.md

Hello,

Some links in this file (first 4 in the list) are broken and don't work in the web version: https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/search/overview-search.html?lang=en

user feedback on the benchmark figures

Issue in ./help/implementation-playbook/infrastructure/performance/benchmarks.md

Dear team
We received this comment at AdobeDocs/commerce-operations.fr-FR#2

it says the figures are not correct, should be 2M page views per hours and 208k orders per hours

Can you please verify?
Please also feel free to reply directly in the fr-FR issue if that is more convenient for you.

Search Engine user guide link goes to a 404 page

Issue in ./help/configuration/search/configure-search-engine.md

In this sentence "For additional details about configuring your search engine, see the User Guide." That link goes to a 404 page.

Elasticsearch is no longer supported on cloud after Adobe commerce 2.4.4

Issue in ./help/installation/system-requirements.md

Hello Team,

Please could you update this article to mention that Elasticsearch is only supported for on-premise customers and cloud customers need to switch to opensearch from adobe commerce version 2.4.4. Currently this article does not mention this clearly and customers are getting confused. Please see the support article on which is is stated: https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/announcements/commerce-announcements/switching-to-opensearch-for-adobe-commerce-on-cloud-2.4.4.html?lang=en

If you have any further questions please reach out to me.

Thanks
Ishwar

Varnish 7.0 already EOL

Topic Link

https://github.com/AdobeDocs/commerce-operations.en/blob/main/help/_includes/templated/system-requirements-table.md

Description

Varnish 7.0 is listed as the latest tested Varnish version for Magento >= 2.4.4 but Varnish 7.0 is already EOL. This leads to people wanting to install Varnish in a version which is already not supported anymore.

This is a followup of magento/magento2#35536 which documents that the admin backend doesn't even provide the Varnish 7.0 configuration template.

Possible solutions

Stick to a Varnish LTS release (currently 6.0) until a feature of a newer version is required.

COMDOX-327: test issues board take two

This issue is a test for the backlog project.

What about the use of shared catalog on the calc of the "Effective SKU" numer

Issue in ./help/implementation-playbook/best-practices/planning/product-sku-limits.md

Please, it would be good to clarify how the uses of shared catalog influence the value of the "Effective SKU" numer

Incorrect URL for account login

Issue in ./help/tools/site-wide-analysis-tool/installation.md

1. Under the Commerce Services Connector heading:

Log into accounts.magento.com - the URL should be account.magento.com (without the S)

2. I also suggest adding a hint about what you should do if you are unable to log into the account:
   Unable to log in to Adobe Commerce support or cloud account

Configure GJSS app for COMDOX project and doc repos

We shouldn't have to manually create Jira tickets for issues reported in our GitHub repos.

Configure the GitHub Jira Synchronization Service for the COMDOX Jira project and the following repo (not meant to be comprehensive):

• AdobeDocs/commerce-operations.en (git.corp & github.com)

We anticipate using this to collaborate with partners on the Implementation Best Practices initiative. We're designing the intake workflow now, but it requires all work to be tracked in Jira.

MySQL version >= 8.0.29 is no longer compatible with Magento <= 2.4.5

Topic Link

https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/system-requirements.html

Description

The system requirements page
https://experienceleague.adobe.com/docs/commerce-operations/installation-guide/system-requirements.html

Mentions MySQL 8.0 being compatible.

Unfortunately, MySQL starting with version 8.0.29 is no longer compatible until Magento 2.4.6 is released.
More info here: magento/magento2#35671

Possible solutions

It would be good to update requirements for Magento versions <= 2.4.5 and inform that only MySQL versions >= 8.0 and <= 8.0.29 are supported.

Additional information

GJSS TEST ISSUE #2 (AMY)

Description

Content checklist

• The topic provides an explanation of how ____ works.
• The topic provides steps for ____.
• The topic contains code samples that shows ____.
• Other (please specify)

Additional information

Wrong information about app/etc/config.php

Issue in ./help/configuration/reference/deployment-files.md

As of the 2.2 release, the app/etc/config.php file is no longer an entry in the .gitignore file.
This was done to facilitate [pipeline deployment](https://experienceleague.adobe.com/docs/commerce-operations/configuration-guide/deployment/technical-details.html?lang=en).

See your latest version of .gitignore: https://raw.githubusercontent.com/magento/magento2/2.4/.gitignore

Footer year is still 2021

Topic Link

https://experienceleague.adobe.com/docs/

Description

Footers of every page of https://experienceleague.adobe.com/docs/ have "Copyright © 2021 Adobe. All Rights Reserved."

Possible solutions

Change "2021" to "2022"

GJSS TEST ISSUE JIRA TO GITHUB EXPORT

GJSS TEST ISSUE

db_schema.xml file, column type is int type, padding attribute not working

Description

In the db_schema.xml file, when the field is set to int type, the padding attribute set after executing the command does not working

Content checklist

Add an int type field to a table and set the padding attribute. After running the setup:upgrade command, I found that the padding attribute was ignored and had no effect.

Additional information

The file we refer to for setting attributes is the official Magento xsd file:

vendor/magento/framework/Setup/Declaration/Schema/etc/types/integers/integer.xsd

Magento 2.4.6 does not support MariaDB 10.6 and docs specify 10.6.

Issue in ./help/installation/system-requirements.md

I'm getting this message when upgrading to MariaDB 10.6 for Magento 2.4.6:

Current version of RDBMS is not supported. Used Version: 10.6.13-MariaDB-1:10.6.13+maria~ubu2004. Supported versions: MySQL-8, MySQL-5.7, MariaDB-(10.2-10.4) 

More documentation

There is no need to contact Support until you have done your due diligence and still encounter authentication errors

Issue in ./help/installation/prerequisites/authentication-keys.md

For access entitlement to Adobe Commerce and Magento Open Source packages, you must use keys associated with a MAGEID that has been granted access to those packages. The MAGEID is typically the Billing Contact on the Adobe Commerce account and may not always be the Project Owner of the Adobe Commerce on cloud infrastructure project. If you encounter [errors](https://support.magento.com/hc/en-us/articles/360040296392), you may not have authorization to access the package or the access entitlement has expired due to an outstanding invoice on the account. Contact [Adobe Commerce Support](https://support.magento.com/hc/en-us) for assistance with your MAGEID.

Firstly, the MAGEID is not always the Billing Contact - it's the Primary Contact listed on the contract and does not necessarily have to be the Billing Contact.

Recommendation:

For access entitlement to Adobe Commerce and Magento Open Source packages, you must use keys associated with a MAGEID that has been granted access to those packages. The MAGEID is typically the Primary Contact on the Adobe Commerce account and may not always be the Project Owner of the Adobe Commerce on cloud infrastructure project. 

If you encounter [errors](https://support.magento.com/hc/en-us/articles/360040296392), you may not have authorization to access the package or the access entitlement has expired due to an outstanding invoice on your account. 

- If you are the Primary Contact person on the account, please make sure that there is no outstanding invoice listed on the account.
- If the keys provided by the Primary Contact are not working and there are no outstanding invoices on the account, contact [Adobe Commerce Support](https://support.magento.com/hc/en-us) for assistance with the Primary Contact's MAGEID.

The db_schema.xml file sets the timestamp type field according to the document. The nullable attribute value does not working.

Description

In the 2.4.X env, if the timestamp type field in db_schema.xml modifies the nullable value,
executing the command (php bin/magento s:up --dry-run=1) will not trigger db DB modification.

origin db_schema.xml:

<schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="urn:magento:framework:Setup/Declaration/Schema/etc/schema.xsd">
    <table name="dev_example_entity" resource="default" engine="innodb" comment="Dev Example Entity">
        <column xsi:type="int" name="entity_id" unsigned="true" nullable="false" identity="true"
                comment="Entity ID"/>
        <column xsi:type="varchar" name="username" nullable="true" length="255" comment="Username"/>
        <column xsi:type="varchar" name="email" nullable="true" length="255" comment="Email"/>
        <column xsi:type="bigint" name="review_id" unsigned="true" nullable="false" identity="false"
                comment="Review ID"/>
        <column xsi:type="timestamp" name="created_at" on_update="false" nullable="true" default="CURRENT_TIMESTAMP" comment="Created Date"/>
        <column xsi:type="timestamp" name="updated_at" on_update="true" nullable="true" default="CURRENT_TIMESTAMP"
                comment="Updated Date"/>
        <constraint xsi:type="primary" referenceId="PRIMARY">
            <column name="entity_id"/>
        </constraint>
    </table>
</schema>```


modified db_schema.xml:

```<?xml version="1.0"?>
<schema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:noNamespaceSchemaLocation="urn:magento:framework:Setup/Declaration/Schema/etc/schema.xsd">
    <table name="dev_example_entity" resource="default" engine="innodb" comment="Dev Example Entity">
        <column xsi:type="int" name="entity_id" unsigned="true" nullable="false" identity="true"
                comment="Entity ID"/>
        <column xsi:type="varchar" name="username" nullable="true" length="255" comment="Username"/>
        <column xsi:type="varchar" name="email" nullable="true" length="255" comment="Email"/>
        <column xsi:type="bigint" name="review_id" unsigned="true" nullable="false" identity="false"
                comment="Review ID"/>
        <column xsi:type="timestamp" name="created_at" on_update="false" nullable="false" default="CURRENT_TIMESTAMP" comment="Created Date"/>
        <column xsi:type="timestamp" name="updated_at" on_update="true" nullable="true" default="CURRENT_TIMESTAMP"
                comment="Updated Date"/>
        <constraint xsi:type="primary" referenceId="PRIMARY">
            <column name="entity_id"/>
        </constraint>
    </table>
</schema>```


![image](https://github.com/AdobeDocs/commerce-operations.en/assets/14126358/15b8caa8-f4c3-4b26-9a8a-5ce4b7d86b75)

Azure availability map may be incorrect

Issue in ./help/implementation-playbook/infrastructure/cloud/regions.md
https://experienceleague.adobe.com/docs/commerce-operations/implementation-playbook/infrastructure/cloud/regions.html?lang=en#azure-regions

The Azure availability map is different (showing more availability zones) to the one provided on Field Readiness https://fieldreadiness-adobe.highspot.com/items/5f1885ada4dfa07661acaa35?lfrm=srp.5#3

Jay Chaudhury advised that FR is the accurate source which he updates, so the public page may be inaccurate and need a revision.

It is also ambiguous what 'potential availability zones' means, or the 'local' zone marked on the AWS map means - will be worth updating to a clearer statement

In Knowledge Base article, it said for regular customers mysql slave connection is not recommended.

commerce-operations.en/help/implementation-playbook/best-practices/planning/configure-mysql-slave-connection-on-cloud.md

Line 22 in a0bef93

## Configure MySQL slave connection

In https://experienceleague.adobe.com/docs/commerce-knowledge-base/kb/troubleshooting/databas[…]-load-bottleneck-in-magento-commerce-cloud.html?lang=en, it said mysql slave connection is not recommended for the regular customers. Can we update the documentation to include the different case usage?

GJSS TEST ISSUE (AMY)

Description

Content checklist

• The topic provides an explanation of how ____ works.
• The topic provides steps for ____.
• The topic contains code samples that shows ____.
• Other (please specify)

Additional information

COMDOX-327: test issues board take three

This issue is a test for the backlog project.

fantastic

Issue in ./help/release/release-notes/security/2-4-6-p3.md

Convert the run-on sentence in the headings of each section to include the original links provided in New Relic

Issue in ./help/tools/observation-for-adobe-commerce/bots.md

The heading of each section that's copied from New Relic contains links, - but currently, they are just run-on sentences, so we should convert them, i.e.,

https://experienceleague.adobe.com/docs/commerce-operations/tools/observation-for-adobe-commerce/bots.html?lang=en#total-bot-traffic-by-bot-name%2Fip-address-during-selected-time-period-how-to-block-bot-traffic-on-fastly-level-or-manage-bots-through-your-robots.txt-file-best-practices-for-adobe-commerce-robots.txt

Total Bot Traffic by Bot name/IP address during selected time period How to block bot traffic on Fastly level OR manage bots through your robots.txt file

For example, with the links included:

Total Bot Traffic by Bot name/IP address during selected time period How to block bot traffic on Fastly level OR manage bots through your robots.txt file Best practices for Adobe Commerce robots.txt

Bug report

Description

This is about the default setting to have changed from being enabled in 2.4.5 and earlier to disabled in 2.4.6 and later .
Based on the commit message in magento/magento2@e2ab9c0, it looks like this was done for improved performance, which I agree with, it's much faster to have this setting disabled.

So, in my opinion, this is more a bug in the documentation, where it wasn't specified in the release notes.It is better get it added to the release notes for Magento 2.4.6

I can't see the option My Profile

Issue in ./help/installation/tutorials/extensions.md

Every time that I'm trying to get the My profile the site is have some kind of issue. Please advise, this is really urgent. Thanks

Testing issue

Testing the best-practices feature

GJSS TEST ISSUE EXPORT TRIGGER

Topic Link

Description

Possible solutions

Additional information

Lack of information about pcntl extension

Issue in ./help/configuration/cli/manage-indexers.md

There is no information about requirements for Parallel Reindex functionality.
It requires pcntl (Process Control) extension on PHP (https://www.php.net/manual/en/pcntl.installation.php)

Official PHP documentation says:

Process Control support in PHP is not enabled by default. You have to compile the CGI or CLI version of PHP with --enable-pcntl configuration option when compiling PHP to enable Process Control support.

Emphasize that Elasticsearch 7.16 and newer is not supported on Cloud

Issue in ./help/installation/system-requirements.md

There is some confusion regarding the system requirements for Elasticsearch on Cloud vs. Open Search - this page implies that 7.16 and 7.17 can be also used on Cloud, but that is not the reality.

The granular requirement for Cloud is that Open Search must be used/installed in place of Elasticsearch 7.16+

More information: https://experienceleague.adobe.com/docs/commerce-cloud-service/user-guide/configure/service/opensearch.html?lang=en

Incorrect export DATA_CONVERTER_BATCH_SIZE command

Description

The current upgrade documentation says to run:

export DATA_CONVERTER_BATCH_SIZE 100000

before running the upgrade. Running this in bash 5.1.16(1)-release gives the following error:

bash: export: `100000': not a valid identifier

The correct command should be:

export DATA_CONVERTER_BATCH_SIZE=100000

Steps to reproduce

Run command:

export DATA_CONVERTER_BATCH_SIZE 100000

Expected result

You shouldn't get any errors from bash and the environment variable is set:

echo $DATA_CONVERTER_BATCH_SIZE

Possible solutions

Documentation updated to correct command:

export DATA_CONVERTER_BATCH_SIZE=100000