General issue

Description

This section contains stray HTML tags and isn't formatted correctly:

1. </code><p><code>
2. <p>

**For Pro** mysql -P 3304 -h $MYSQL_HOST -u $DB_USER --password=$MYSQL_PWD $DB_NAME -e "SELECT table_name,row_format FROM information_schema.tables WHERE table_schema='$DB_NAME' and row_format='compact'"|wc -l</code><p><code>mysql -P 3304 -h $MYSQL_HOST -u $DB_USER --password=$MYSQL_PWD $DB_NAME -e "SELECT table_name,row_format FROM information_schema.tables WHERE table_schema='$DB_NAME' and row_format='compact'"|less
...
Build the ALTER table list file, and make sure it's complete: **For starter** use 3306 as there is only one MySQL instance. **For Pro**
mysql -P 3304 -h $MYSQL_HOST -u $DB_USER --password=$MYSQL_PWD $DB_NAME -e "SELECT table_name,row_format FROM information_schema.tables WHERE table_schema='$DB_NAME' and row_format='compact'"|grep -v table_name|awk '{print "alter table "$1" ROW_FORMAT=DYNAMIC; "}' > ~/var/alter.txt<p>fw0ef0jqfdlwdj@i-f5w6ef4w6e5f4we6f4:~$ wc -l ~/var/alter.txt
612 /app/fw0ef0jqfdlwdj/var/alter.txt
fw0ef0jqfdlwdj@i-f5w6ef4w6e5f4we6f4:~$ mysql -h $MYSQL_HOST -u $DB_USER --password=$MYSQL_PWD $DB_NAME -e "SELECT table_name,row_format FROM information_schema.tables WHERE table_schema='$DB_NAME' and row_format='compact'"|grep -v table_name|wc -l
612

Possible solutions

For Pro:

mysql -P 3304 -h $MYSQL_HOST -u $DB_USER --password=$MYSQL_PWD $DB_NAME -e "SELECT table_name,row_format FROM information_schema.tables WHERE table_schema='$DB_NAME' and row_format='compact'"|wc -l
mysql -P 3304 -h $MYSQL_HOST -u $DB_USER --password=$MYSQL_PWD $DB_NAME -e "SELECT table_name,row_format FROM information_schema.tables WHERE table_schema='$DB_NAME' and row_format='compact'"|less

...

Build the ALTER table list file, and make sure it's complete:

• For starter use 3306 as there is only one MySQL instance.
• For Pro

mysql -P 3304 -h $MYSQL_HOST -u $DB_USER --password=$MYSQL_PWD $DB_NAME -e "SELECT table_name,row_format FROM information_schema.tables WHERE table_schema='$DB_NAME' and row_format='compact'"|grep -v table_name|awk '{print "alter table "$1" ROW_FORMAT=DYNAMIC; "}' > ~/var/alter.txt
fw0ef0jqfdlwdj@i-f5w6ef4w6e5f4we6f4:~$ wc -l ~/var/alter.txt
612 /app/fw0ef0jqfdlwdj/var/alter.txt
fw0ef0jqfdlwdj@i-f5w6ef4w6e5f4we6f4:~$ mysql -h $MYSQL_HOST -u $DB_USER --password=$MYSQL_PWD $DB_NAME -e "SELECT table_name,row_format FROM information_schema.tables WHERE table_schema='$DB_NAME' and row_format='compact'"|grep -v table_name|wc -l
612

Additional information

This article need markdown format fixing on "Magento 2.4.0: Checkout error selecting local payments"- it is an easy fix. This impacts https://support.magento.com/hc/en-us/articles/360047139331

Underlining not working and headers not rendering:

General issue

Description

Possible solutions

Additional information

Article URL

https://support.magento.com/hc/en-us/articles/360044482152

Description

Add a clarification on this point for Adobe Commerce Cloud:

You can turn on merging or bundling in Magento’s Admin UI

e.g,

• You can turn on merging or bundling in Magento’s Admin UI (On-Premises or local environment only) ...

Adobe Commerce Cloud: You would only be able to configure this from the backend when the deployment mode is set to default or developer as indicated by app/etc/env.php

  'MAGE_MODE' => 'production',

However, the deployment mode is always set to production mode in the Cloud environment and would cause errors if you attempt to modify it.

Thus, the configuration can only be achieved/modified from the command line (refer to the next point)

• You can also enable Magento’s built-in bundling (basic bundling) from the command line ...

Content checklist

• The topic provides troubleshooting/best practices for configuring JS/CSS minification.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ALL Versions.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

General issue

Description

Possible solutions

Additional information

General issue

Compilation error. Same installation yesterday produced no error.

Blocking issue.

Description

Clean installation Magento 2.4.2-p1 Jul 27 2021 No extension installed.
Oracle Linux 8.4 Php 7.4 Apache 2.4 Mysql 8

Compilation error. Same installation yesterday produced no error.

Clean installation Magento 2.4.2-p1 Jul 27 2021 No extension installed.
Oracle Linux 8.4 Php 7.4 Apache 2.4

Please see the screen shot
https://prnt.sc/1gjybrr

✘ magento2@stage5  /var/www/magento2/html  magento se:di:c -vv
Compilation was started.
Interception cache generation... 6/9 [==================>---------] 66% 25 secs 346.0 MiBErrors during compilation:
Magento\Framework\Setup\Option\AbstractConfigOption
Incompatible argument type: Required type: int. Actual type: string; File:
/var/www/magento2/html/vendor/magento/framework/Setup/Option/AbstractConfigOption.php

Total Errors Count: 1

In Log.php line 92:

[Magento\Framework\Validator\Exception]
Error during compilation

Exception trace:
at /var/www/magento2/html/setup/src/Magento/Setup/Module/Di/Compiler/Log/Log.php:92
Magento\Setup\Module\Di\Compiler\Log\Log->report() at /var/www/magento2/html/setup/src/Magento/Setup/Module/Di/Code/Reader/Decorator/Interceptions.php:85
Magento\Setup\Module\Di\Code\Reader\Decorator\Interceptions->getList() at /var/www/magento2/html/setup/src/Magento/Setup/Module/Di/App/Task/Operation/InterceptionCache.php:59
Magento\Setup\Module\Di\App\Task\Operation\InterceptionCache->doOperation() at /var/www/magento2/html/setup/src/Magento/Setup/Module/Di/App/Task/Manager.php:56
Magento\Setup\Module\Di\App\Task\Manager->process() at /var/www/magento2/html/setup/src/Magento/Setup/Console/Command/DiCompileCommand.php:216
Magento\Setup\Console\Command\DiCompileCommand->execute() at /var/www/magento2/html/vendor/symfony/console/Command/Command.php:255
Symfony\Component\Console\Command\Command->run() at /var/www/magento2/html/vendor/symfony/console/Application.php:1009
Symfony\Component\Console\Application->doRunCommand() at /var/www/magento2/html/vendor/symfony/console/Application.php:273
Symfony\Component\Console\Application->doRun() at /var/www/magento2/html/vendor/magento/framework/Console/Cli.php:115
Magento\Framework\Console\Cli->doRun() at /var/www/magento2/html/vendor/symfony/console/Application.php:149
Symfony\Component\Console\Application->run() at /var/www/magento2/html/bin/magento:23

Possible solutions

Additional information

Article URL

https://support.magento.com/hc/en-us/articles/360052293411

Description

The opening statement needs some clarity:

Adobe technical support may require access to your Adobe Commerce-related data in order to provide support. The primary Adobe Commerce account holder can choose to provide this authorization in their Adobe Commerce account privacy settings. Allowing this access prior to support request creation will help ensure the issue can be properly investigated and/or help increase the speed of resolution.

The primary Adobe Commerce account holder can choose to provide this authorization in their Adobe Commerce account privacy settings. If you are the Project Owner of an Adobe Commerce Cloud project, note that it doesn't mean that you are the Primary Account Holder - you will have to contact the account holder to provide their consent.

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version All.
• Magento Commerce Cloud version All.
• Magento Open Source version N/A.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Article URL

https://support.magento.com/hc/en-us/articles/4410911888013

Description

The article indicates that this change is for Magento 2.3.6+ and 2.4.2+. However, I've checked the Commerce Base files and noticed that references to this new queue consumer only exists in 2.3.7+ and 2.4.3+.

Please verify and update the article accordingly

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Issue: Topic clarification/correction

Topic Link

https://support.magento.com/hc/en-us/articles/360049171211-Best-practices-for-render-blocking-resources-in-Magento-

Description

1. Replace "Best practices for render-blocking resources in Magento" with "Best practices for render-blocking resources in Adobe Commerce" in title.
2. Replace "Magento Commerce, all supported versions" with "Adobe Commerce on-premise, all supported versions"
3. Replace "Magento Commerce Cloud, all supported versions" with "Adobe Commerce on our cloud infrastructure, all supported versions".
4. Replace "submit a Magento Support ticket." with "submit a support ticket."
5. Replace "Magento User Guide > Optimizing Resource Files" with "Adobe Commerce User Guide > Optimizing Resource Files".

(don't change other links in Related reading for now)

Article URL

https://devdocs.magento.com/cloud/project/set-cache.html

Description

The guidance in this article is to set expires headers to -1 when in reality this doesn't tell cache to not expire, it tells nginx to NOT cache those files.

For a cross reference, in another piece of documentation here https://devdocs.magento.com/cloud/project/magento-app-properties.html

we see

expires | Set the number of seconds to cache content in the browser. This key enables the cache-control and expires headers for static content. If this value is not set, the expires directive and resulting headers are not included when serving static content files. A negative 1 (-1) value results in no caching and is the default value. You can express time value with the following units: ms (milliseconds), s (seconds), m (minutes), h (hours), d (days), w (weeks), M (months, 30d), or y (years, 365d)

So setting cache headers to -1 is doing the opposite of what it says it does in the Set cache TTL for images and other static content

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

We found this out the hard way on our magento cloud instance to not follow this recommendation and this documentation should be updated

Code of Conduct

• I agree to follow this project's Code of Conduct

Article URL

https://support.magento.com/hc/en-us/articles/360048061192-SSL-TLS-certificates-for-Magento-Commerce-Cloud-FAQ

Description

The current wording on this article suggests a ticket needs to be created; however, this is incorrect:

If you have not launched a website yet, you may have received ACME Challenge CNAME from your Customer Technical Advisor (CTA). You only need an ACME challenge if you cannot immediately point your DNS to you production URL and need to get the SSL сertificates created in advance.

Once you add them to your DNS panel, submit a support ticket . We will validate that the CNAME has been added and apply the SSL certificate in response.

SSL Certificates are staged by automation within 12 hours of the addition of the CNAMEs. See https://devdocs.magento.com/cloud/cdn/configure-fastly.html#provision-ssltls-certificates for reference.

Content checklist

This article provides quick answers to questions about getting SSL (TLS) certificates for your Magento Commerce Cloud site.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

General issue

Description

All the letters in the file names should be in lower case. Need to change those that are in upper case.

1. MDVA-34680-customer-account-created-time-is-not-filtered-correctly-in-customers-grid.md
2. MDVA-37068-incorrect-tax-rate-displays-on-checkout-for-virtual-products.md
3. MDVA-38308-error-after-adding-vimeo-videos-to-disabled-products.md
4. MDVA-38468-error-when-saving-cms-pages.md

Possible solutions

1. mdva-34680-customer-account-created-time-is-not-filtered-correctly-in-customers-grid.md
2. mdva-37068-incorrect-tax-rate-displays-on-checkout-for-virtual-products.md
3. mdva-38308-error-after-adding-vimeo-videos-to-disabled-products.md
4. mdva-38468-error-when-saving-cms-pages.md

Article URL

https://support.magento.com/hc/en-us/articles/360037591172

Description

This statement has a "First" designation - so is there a "Second" or subsequent point to this article?

First, check if there is a lack of disk space. ...

Maybe remove First - or follow through to the rest of the article with Next steps:

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

k;alsknf;lsdnf;

Article URL

https://support.magento.com/hc/en-us/articles/360000913794-Magento-Help-Center-User-Guide#no-submit-link

Description

In this section:

Issue
You access the Magento Help Center and want to submit a support request, but the Submit a ticket link is not displayed on the Help Center start page.

Cause
One of the following might be the cause:
* You have not logged in to the Help Center.
* If using shared access, you have not performed steps required to ensure that Magento Help Center is configured properly via the SSO call from Magento.com.
* Your account is not entitled for Magento Support (for example, you are not a paying Commerce customer or you are an Open Source customer).

This point needs to be fleshed out/expanded upon

If using shared access, you have not performed steps required to ensure that Magento Help Center is configured properly via the SSO call from Magento.com.

For example, emphasis on the for the first time:

If using shared access for the first time, you have not performed the steps required to ensure that Magento Help Center is configured properly via the SSO call from Magento.com.

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

General issue

Description

The Issue section is incomplete - it just says this:

https://mydomain.com.c.

Possible solutions

https://mydomain.com.c.<projectid>.magento.cloud/ is no longer accessible

Additional information

Bla bla bla bla

General issue

Description

Affected products and versions
The patch was designed for Magento Commerce Cloud 2.3.5-p1.
The patch is also compatible with Magento Commerce / Magento Commerce Cloud 2.3.2-2.4.0.

Possible solutions

The patch is also compatible with Magento Commerce / Magento Commerce Cloud 2.3.2-2.4.1-p1

Additional information

Article URL

https://support.magento.com/hc/en-us/articles/4403024155917-MDVA-34330-Orders-not-filtered-according-to-admin-timezone

Description

The article says:

"Please note that the issue is scheduled to be fixed in Adobe Commerce 2.4.3."

However, we're running 2.4.3-p1 and this issue still persists.

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Article URL

https://support.magento.com/hc/en-us/articles/360040296392

Description

Customers get reminders and also get a 30 day grace period, so normally when credentials stop working, it has been almost 60 days since payment should have been received. You can't open a new support ticket and deploy the application. After you get your license activated again, you still can't deploy the application.

^This is not accurate, our Entitlements Team does not provide any official grace periods at this time. Also, the last sentence is incorrect - once a customer's license is re-activated, they WILLL be able to deploy the application and do all the normal functions they usually do. This should be edited to:

*If you find this is due to an invoicing or lapsed contract issue, please contact your CSM for guidance to get this resolved. After your license is re-activated, your support and deployment entitlements will be restored.

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

General issue

magento/magento2#28159

We are getting this issue, while we are reindexing. Can you pls help?

Possible solutions

Additional information

General issue

Description

This needs to be in a code block and formatted accordingly:

yaml: "/media": root: "pub/media" allow: true scripts: false expires: 1y passthru: "/get.php"

Possible solutions

        "/media":
            root: "pub/media"
            allow: true
            scripts: false
            expires: 1y
            passthru: "/get.php"

Additional information

Article URL

https://support.magento.com/hc/en-us/articles/360043032152

Description

Hello Team,

The wording in this article is slightly confusing regarding the required project branches and many merchants and engineers have been thrown off by this.

the main Integration branch is included in the 2 total). Note: Do not count the primary branch in this total. The primary branch is not considered an integration branch

Primary is a little misleading as this is not used within the cloud project UI, having discussed with the L1 team we believe this refers to Master and the doc should probably be updated to replace Primary with Master, to help avoid any confusion in future.

Content checklist

• The topic provides troubleshooting/best practice for Enhanced Integration requests.
• Information in this topic is relevant for
• Magento Commerce version N/A.
• Magento Commerce Cloud version N/A.
• Magento Open Source version N/A.
• Extension or technology (Fastly, New Relic etc) version N/A.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Article URL

https://support.magento.com/hc/en-us/articles/360030568432

Description

The links for Customize php.ini settings do not seem to be valid any longer as they simply direct to: https://devdocs.magento.com/cloud/project/magento-app.html.

I believe the correct path should now be: https://devdocs.magento.com/cloud/project/magento-app-php-ini.html, which contains the current php.ini configuration documentation.

Additionally, the php.ini configuration documentation does not contain reference to this solution:
Make sure you do not remove the windows-style endings in the php.ini file.

So if the associated error is still valid, this should probably be added to that article also:
On Windows, line-endings are terminated with a combination of a carriage return (ASCII 0x0d or \r) and a newline(\n), also referred to as CR/LF.

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

General issue

Description

Possible solutions

Additional information

Article URL

https://support.magento.com/hc/en-us/articles/360025901132

Description

Correct the grammar of the subject heading to this:

Products not selected for mass action deletion are [erroneously] being deleted together with those that had been selected.

Or use the original subject of the Jira in which the issue was reported:

More products were deleted from Magento than what was initiated in the admin

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Article URL

https://support.magento.com/hc/en-us/articles/4409245779725

Description

Adjust this paragraph to indicate that the credits are reset monthly for integration and Staging

SendGrid credits refer to the number of allowed emails that can be sent. Only 12,000 emails can be sent per month from the integration **and Staging** branches. Once you have reached that limit, you will have to wait until the next month to send emails again. There are no hard limits on the number of emails that can be sent in **Production**, as long as the Sender Reputation is over 95%.

In addition, append this paragraph/sentence:

Credits are renewed at the start of the month, so if you run out of credits, you will have to wait for the renewal.

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Issue: Topic clarification/correction

Topic Link

https://support.magento.com/hc/en-us/articles/4402349423757-Error-purging-cache-in-Magento-Commerce-Admin

Description

1. Replace " Magento Commerce Admin" with "Adobe Commerce Admin" in title and intro.
2. Replace "Magento Admin" with "the Admin".
3. Replace "Magento cache" with "Adobe Commerce cache".
4. Replace
   "Magento Commerce and Magento Commerce Cloud: 2.3.0-2.3.7, 2.4.0-2.4.2-p1"
   with
   "Adobe Commerce on-premise and Adobe Commerce on our cloud architecture: 2.3.0-2.3.7, 2.4.0-2.4.2-p1"
5. Add "Adobe Commerce" label in metadata.

Don't delete the "Magento" labels.

Article URL

https://support.magento.com/hc/en-us/articles/360044674792

Description

Add clarification to the article:

Note: For Adobe Commerce on cloud, the best practices apply specifically to the Production environment [and possibly Staging on Cloud Pro, subject to resource constraints] which would have more resources than the integration/development environments. For integration (Pro and Starter) and Staging environments (Starter), you should reduce the number of store views to less than 5 or 10 (subject to technical review) 

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version All versions.
• Magento Commerce Cloud version All versions.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Article URL

https://support.magento.com/hc/en-us/articles/360051598831-Database-errors-related-to-max-allowed-packet-on-Magento

Description

This solution will not work for Adobe Commerce on Cloud (the article currently says Magento Commerce Cloud) - any changes to max_allowed_packet value are not currently supported and would require a feature request.

Example case (not for public consumption) https://magento.zendesk.com/agent/tickets/387967

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Issue: Topic clarification/correction

Topic Link

https://support.magento.com/hc/en-us/articles/360058863531

Description

1. Add these labels: Adobe Commerce,Adobe Commerce on our cloud architecture,Adobe Commerce on-premise
2. Make Actual result > Actual results
3. Make Expected result > Expected results

Note: don't give space after commas in labels, and don't add a comma after the last label.

Test

trying again

Article URL

https://support.magento.com/hc/en-us/articles/360049292532

Description

This needs to be fleshed out more:
If you have ece-tools 2002.1.1 or higher, use the REDIS_BACKEND deployment variable to set this:

E.g.,

### Content checklist

* The topic provides troubleshooting/best practice for ____.
* Information in this topic is relevant for
* Magento Commerce version  ____.
* Magento Commerce Cloud version  ____.
* Magento Open Source version  ____.
* Extension or technology (Fastly, New Relic etc) version   ____.


### Additional information/resources

_No response_

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct

General issue

Description

The current syntax is slightly misleading as inserting the 'project_id' directly will not return any results.
'%' should be used as a wildcard with the LIKE operator, for '=' these are not required.

Possible solutions

Correct command should be as follows:

SELECT TABLE_NAME AS `Table`,
  ROUND((DATA_LENGTH + INDEX_LENGTH) / 1024 / 1024) AS `Size (MB)`
FROM information_schema.TABLES
WHERE TABLE_SCHEMA = "project_id"
ORDER BY (DATA_LENGTH + INDEX_LENGTH) DESC;

OR

SELECT TABLE_NAME AS `Table`,
  ROUND((DATA_LENGTH + INDEX_LENGTH) / 1024 / 1024) AS `Size (MB)`
FROM information_schema.TABLES
WHERE TABLE_SCHEMA LIKE "%project_id%"
ORDER BY (DATA_LENGTH + INDEX_LENGTH) DESC;

Additional information

Nothing further.

Article URL

https://support.magento.com/hc/en-us/articles/360000262174

Description

Add a clarification that this issue does not relate to Previewing the Scheduled Update.

Accessing any storefront page or the Admin results in the 404 error (the "Whoops, our bad..." page) after performing operations with scheduled updates for store content assets using Content Staging (updates for store content assets scheduled using the Magento_Staging module). For example, you may have deleted a Product with a scheduled update or removed the end date for the scheduled update.

For example:

This article doesn't apply to the situation in which you get a 404 error when trying to preview the staging update. If you run into that issue, please open a support ticket.

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Issue: Topic clarification/correction

Topic Link

https://support.magento.com/hc/en-us/articles/360059785811

Description

1. Remove the paragraph space after, "The MDVA-19640 Magento patch fixes the issue when Advanced Reporting shows no data." Make it one paragraph.

Like,

The MDVA-19640 Magento patch fixes the issue when Advanced Reporting shows no data. This patch is available when the Magento Quality Patch (MQP) tool 1.0.20 is installed. The patch ID is MDVA-19640. Please note that there is no current plan to fix this issue in future versions.

ewewew

Article URL

https://support.magento.com/hc/en-us/articles/360040296392

Description

Not sure if this is correct - needs further review:

Customers get reminders and also get a 30 day grace period, so normally when credentials stop working, it has been almost 60 days since payment should have been received. You can't open a new support ticket and deploy the application. After you get your license activated again, you still can't deploy the application.

In my experience, the credentials stop working the day the active entitlements end

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Article URL

https://support.magento.com/hc/en-us/articles/360029351531

Description

Step 16. Yes path takes you to https://dev.mysql.com/doc/refman/5.5/en/server-error-reference.html which is a dead link. Not sure what to do about it other than update the link (here would be an appropriate replacement): https://dev.mysql.com/doc/mysql-errors/5.7/en/server-error-reference.html

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Article URL

https://support.magento.com/hc/en-us/articles/360041456192#zd-accordion-2

Description

I believe Step 2 is incorrect and that it's not the correct way to check the issue.

php bin/magento config:show currency | grep 'currency/options'
a. YES – You cannot use Advanced Reporting, as we only support one currency.
b. NO – Output shows only one currency. Example:
currency/options/base - USD
currency/options/default - USD
currency/options/allow - USD

This command only checks if a single currency is currently configured - it does not check if the orders over the store's lifetime are placed using other currencies and Advanced Reporting does not work when there are orders in multiple currencies.

If you click on the link under Step 1 and then go down further in the article, it states

To determine if your store has multiple base currencies, you can query your Commerce database from the command line using the following MySQL example. You might need to change the table names to match your data structure:

select distinct base_currency_code from sales_order;

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Article URL

https://support.magento.com/hc/en-us/articles/4409425285901-View-number-of-vCPUs-in-your-cluster-on-Adobe-Commerce

Description

A marketing person at Adobe asked a question and I had to do some testing to answer it. The question was ... Can I look at Observation for Adobe Commerce and see the vCPU sizing for a year?

The answer is: Yes but there are some caveats...

The vCPU view use timecharts, which are broken up into 365 buckets maximum. So if you choose a time range greater than a week, the graph will either not show data or it will be a meaningless graph. The vCPU data is metric data, which is summary data. You can set a timeline back one year, but don't choose a duration longer than one week. For example you could set the date from October 1, 2020 to October 8, 2020 and it will display the vCPU data from that date/time range (if it is less than 1 year).

You can word this whatever way you want to, I just wanted to add this clarifying information to the article.

Yarlene Kourt would also like "vCPU" replaced with "vCPU tier" were ever it occurs.

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Article URL

https://support.magento.com/hc/en-us/articles/360037391972

Description

Missing text in Project URL

For scaled architecture (split architecture), Redis slave connections SHOULD NOT be enabled. You can check if you are on scaled architecture by doing the following:

Go to your project URL, e.g. https://us.magento.cloud/projects/<MISSING>/environments/production

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

Article URL

https://support.magento.com/hc/en-us/articles/360049045351

Description

The title should mention Mysql connection, i.e.,

Adobe Commerce on cloud architecture best practice for Mysql slave connection

Content checklist

• The topic provides troubleshooting/best practice for ____.
• Information in this topic is relevant for
• Magento Commerce version ____.
• Magento Commerce Cloud version ____.
• Magento Open Source version ____.
• Extension or technology (Fastly, New Relic etc) version ____.

Additional information/resources

No response

Code of Conduct

• I agree to follow this project's Code of Conduct