New Media Gallery Could not create directories

[nemke82]

Preconditions (*)

Magento 2.4-dev or 2.4.3-p1

1. Switch Enable Old Media Gallery option in Advanced->System section in system configuration from Yes to No
2. Execute php bin/magento media-gallery:sync and php bin/magento media-content:sync and clear cache

Steps to reproduce (*)

1. Switch Enable Old Media Gallery option in Advanced->System section in system configuration from Yes to No
2. Execute php bin/magento media-gallery:sync and php bin/magento media-content:sync and clear cache
3. Navigate to Content --> New Media Gallery
4. Click on Create folder

Expected result (*)

1. To create a folder

Actual result (*)

Attention: Could not create directories: test

Screenshot:
https://i.imgur.com/OiXVuC0.png

POST to /media_gallery/directories/create/?isAjax=true result with 400 status

Works when you click on the folder, for example:
Active filters: Directory: catalog/category
Then click on create folder or upload image.

Additional Info (*)

• If at all we don't select any of the existing folder and try to create new folder, then only we get to see the issue.
• If at all we select any of the available folder and try to create new folder as a child to it, then we can successfully create the new folder.

Suggested fix is that the module picks the Active filter by default.

Please provide Severity assessment for the Issue as Reporter. This information will help during Confirmation and Issue triage processes.

• 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 @nemke82. 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.

⚠️ 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.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

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

[m2-assistant]

Hi @engcom-Delta. 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.

[engcom-Delta]

Hi @nemke82 ,
We tried to reproduce the issue with provided steps , observed that we are not able to create directory without filters created but it allows to create with active filters. Please find the attached screenshots for reference.
Hence added the label 'Issue confirmed'.

[github-jira-sync-bot]

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

[m2-assistant]

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

[nazarklovanych]

@magento I am working on this

[m2-assistant]

Hi @nazarklovanych! 👋
Thank you for collaboration. Only members of Community Contributors Team are allowed to be assigned to the issue. Please use @magento add to contributors team command to join Contributors team.

[nazarklovanych]

@magento add to contributors team

[m2-assistant]

Hi @nazarklovanych! 👋
Thank you for joining. Please accept team invitation 👉 here 👈 and add your comment one more time.

[nazarklovanych]

@magento add to contributors team

[nazarklovanych]

@magento I am working on this

[nazarklovanych]

@joanhe Could you please provide an explanation why you have been removed the posibility to cerate new folders in pub/media and allowing only that folders that specified in the config ? for now users of new media gallery can create only wysywig folder and catalog/category/ and before your commit there was a posibility to do that, here is a commit -> 33aaa42

[joanhe]

@joanhe Could you please provide an explanation why you have been removed the posibility to cerate new folders in pub/media and allowing only that folders that specified in the config ? for now users of new media gallery can create only wysywig folder and catalog/category/ and before your commit there was a posibility to do that, here is a commit -> 33aaa42

@nazarklovanych This is done intentionally. It is only allowed to create new folders under wysywig and catalog/category folders per product request. Please see Modify Media Library folder permissions for more information.

[nazarklovanych]

@joanhe ok, so then this issue can be closed @engcom-Alfa @nemke82

[tuyennn]

Same issue on 2.4.3-p3, please keep this open. The issue is no longer exist on > 2.4.3 only