bin/magento config:show(or set) design/theme/theme_id fails

speedupmate commented 2 years ago

Preconditions and environment

Magento 2.4.4
clean installation is enough

Steps to reproduce

in cli try to

bin/magento config:show design/theme/theme_id bin/magento config:set design/theme/theme_id 3

while grepping from config values are present

bin/magento config:show | grep design
design/theme/theme_id - 3
design/head/includes - <link  rel="stylesheet" type="text/css"  media="all" href="{{MEDIA_URL}}styles.css" />

Expected result

config values are set

Actual result

you will get error messages

bin/magento config:show design/theme/theme_id
The "design/theme/theme_id" path doesn't exist. Verify and try again.

bin/magento config:set design/theme/theme_id 3
The "design/theme/theme_id" path doesn't exist. Verify and try again.

Additional information

No response

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.
[X] 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[bot] commented 2 years ago

Hi @speedupmate. Thank you for your report. To speed up processing of this issue, make sure that you provided the following information:

Summary of the issue
Information on your environment
Steps to reproduce
Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

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.

:warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

:clock10: You can find the schedule on the Magento Community Calendar page.

:telephone_receiver: 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.

:pencil2: Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

m2-assistant[bot] commented 2 years ago

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: :point_down:

[ ] 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
Details
If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
[ ] 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
[ ] 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
[ ] 4. Verify that the issue is reproducible on 2.4-develop branch
Details
- Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
- 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 commented 2 years ago

Verified the issue on Magento 2.4-develop branch and the issue is reproducible.

Configured Content - design - Configuration - set the theme and save
Cache flush
Ran sudo php bin/magento config:show | grep design - displayed saved configuration values: design/theme/theme_id - 2
But on running php bin/magento config:show design/theme/theme_id - below error message is displayed: The "design/theme/theme_id" path doesn't exist. Verify and try again. There is no issue when running php bin/magento config:show web/seo/use_rewrites etc -values displayed as expected.

github-jira-sync-bot commented 2 years ago

:white_check_mark: Jira issue https://jira.corp.magento.com/browse/AC-5915 is successfully created for this GitHub issue.

m2-assistant[bot] commented 2 years ago

:white_check_mark: 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.

artskirk commented 1 year ago

@magento I am working on this

ganeddact commented 4 months ago

to be fair I'm reproducing the same issue, but noticed that any config:set instruction issued via CLI doesn't get saved to database (using Magento 2.4.6-p4)

magento / magento2