[Issue] Fix a PHP error being thrown on a Magento error being thrown

[m2-assistant]

This issue is automatically created based on existing pull request: #32814: Fix a PHP error being thrown on a Magento error being thrown

---

Description (*)

I ran into a small problem with the product media (because my pub/media wasn't writable). But I did not get the actual error that is thrown, I got a PHP error because 'directory' was not set (as you can see by my fix).
I thought, why not have my first contribution be a simple fix

Related Pull Requests

Fixed Issues (if relevant)

Manual testing scenarios (*)

1. Have a simple magento shop with X (might as well be 1) product including images
2. Change the pub/media to incorrect permissions/owners
3. Try to visit the product detail page in the backend

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @krishprakash. 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).

  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.

[magento-engcom-team]

✅ Confirmed by @krishprakash
Thank you for verifying the issue. Based on the provided information internal tickets MC-42960 were created

Issue Available: @krishprakash, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[sidolov]

Hi @m2-assistant[bot]. Thank you for your report.
The issue has been fixed in #32814 by @MJTheOne in 2.4-develop branch
Related commit(s):

• 42ae72ee01f25880d1356e553d9605c3fdebfe65
• f6aacc1fee99f588b67e69e3787f7b309dd79a3e
• 44836ebe5d804963b4e2b7475873304acf4adef6
• ba01f6150f0ee021f8232e0ffdc79d5a15addb18

The fix will be available with the upcoming 2.4.3 release.