[Forwardport] Fixed issue #13480 - Unable to activate logs after switching from production mode to developer

[mage2pratik]

Original Pull Request

#15335

Description

Set the ENV value of dev/debug/debug_logging to null when deployment mode is "developer"

Fixed Issues (if relevant)

1. Unable to activate logs after switching from production mode to developer  #13480: Unable to activate logs after switching from production mode to developer

Manual testing scenarios

1. Set deployment version to "production"
2. Clean the cache (if necessary)
3. Set deployment version to "developer"
4. Check the "Log To File" field under Stores > Configuration > Advanced > Developer > Debug
5. "Log To File" field should be enabled

[magento-engcom-team]

Hi @mage2pratik. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento-engcom-team give me test instance - deploy test instance based on PR changes
• @magento-engcom-team give me {$VERSION} instance - deploy vanilla Magento instance

For more details, please, review the Magento Contributor Assistant documentation

[magento-engcom-team]

Hi @VladimirZaets, thank you for the review.
ENGCOM-2729 has been created to process this Pull Request

[VladimirZaets]

Hi @mage2pratik. Thanks for the collaboration.
We tested your fix, but the issue is still reproduced.

Steps:
Run php bin/magento deploy:mode:set production
Clean the cache
Run php bin/magento deploy:mode:set developer
Action result: "Log To File" field is disabled.

[magento-engcom-team]

Hi @mage2pratik. Thank you for your contribution.
We will aim to release these changes as part of 2.3.0.
Please check the release notes for final confirmation.