Skip to content

Remove incorrect or outdated information related to the 'bin/magento config:set' command #132

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Remove incorrect or outdated information related to the 'bin/magento config:set' command #132

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions help/configuration/cli/set-configuration-values.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -135,8 +135,6 @@ The following table describes the `set` command parameters:
>[!INFO]
>
>As of Commerce 2.2.4, the `--lock-env` and `--lock-config` options replace the `--lock` option.
>
>If you use the `--lock-env` or `--lock-config` option to set or change a value, you must use the [`bin/magento app:config:import` command](../cli/import-configuration.md) to import the setting before you access the Admin or storefront.

If you enter an incorrect configuration path, this command returns an error

Expand Down
Loading