Table prefix is not taken into account

[Rorshah22]

Preconditions and environment

• Magento version 2.4.8
• In the file app/etc/env.php, to have a table prefix, set

Steps to reproduce

1. In the admin panel, go to the Content tab, then open Design > Configuration.
2. Check the list of themes.

Expected result

There is a grid with the themes.

Actual result

Error. The table prefix is not being taken into account.

Additional information

Fix missing table prefix usage https://github.com/magento/magento2/pull/39846/files

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @Rorshah22. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-Bravo. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Bravo]

Hi @Rorshah22,

Thanks for your reporting and collaboration.

We have tried to reproduce the issue in Latest 2.4-develop instance and 2.4.8 magento instance as well and we are not able to reproduce the issue.

There is a grid with the themes.

kindly recheck the issue in latest magento and check if any third party modules can causing this issue.

Thanks.

[Rorshah22]

Hi @engcom-Bravo The tables need to have a prefix as shown in the screenshot; otherwise, an error will occur when trying to access the themes page. A clean Magento 2 installation without any third-party modules.
After running the command
bin/magento setup:install --base-url=http://localhost.com --db-host=mysql --db-name=docker_ee248pref --db-user=docker --db-password=docker --db-prefix=pref_ --admin-firstname=admin --admin-lastname=admin --admin-email=[email protected] --admin-user=admin --admin-password=a111111 --language=en_US --currency=USD --timezone=America/Chicago --use-rewrites=1 --search-engine=opensearch --opensearch-host=opensearch2 --opensearch-port=9200 --opensearch-index-prefix=magento2 --opensearch-timeout=15

[m2-assistant]

Hi @engcom-November. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-November]

Hello @Rorshah22 ,

Thank you for your report and collaboration.

We attempted to reproduce the issue in the latest 2.4-develop and 2.4.8 instances. We are able to reproduce the issue. Please refer to the attached screenshot for details.

Steps to Reproduce:

1. In the admin panel, go to the Content tab, then open Design > Configuration.
2. Check the list of themes.

Note:
After running the command
bin/magento setup:install --base-url=http://localhost.com --db-host=mysql --db-name=docker_ee248pref --db-user=docker --db-password=docker --db-prefix=pref_ --admin-firstname=admin --admin-lastname=admin --admin-email=[email protected] --admin-user=admin --admin-password=a111111 --language=en_US --currency=USD --timezone=America/Chicago --use-rewrites=1 --search-engine=opensearch --opensearch-host=opensearch2 --opensearch-port=9200 --opensearch-index-prefix=magento2 --opensearch-timeout=15

We followed the preconditions and steps as provided and encountered the issue.

Therefore, we are marking this ticket as "Issue: Confirmed."

Thank you!

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-14556 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-November. Thank you for verifying the issue.
Issue Available: @engcom-November, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.