Media title falsely has kebab case when inserted via REST API (e.g. in Block Editor)

[abitofmind]

Reproduction I: "Upload New Media" creates media title "My Great Photo"

1) Media > Add New
2) Drag-n-drop "My Great Photo.jpg"
3) Inspecting this in "Edit Media" shows a media title "My Great Photo".

Reproduction II: Insertion via Block Editor (Gutenberg) creates media title "My-Super-Photo"

1) Edit an existing page or create a new page.
2) Set the cursor into an empty block.
3) Drag-n-drop "My Super Photo.jpg" into this block. This automatically creates a media page behind the scenes.
4) Save the page.
5) Inspecting the media title via "Edit Media"

• Actual: The media title is "My-Super-Photo".
• Expected: The media title should be "My Super Photo".
  • The media title should be the filename portion (without the suffix) in its purest possible form (UTF-8) and only the slug and filename should then be transformed according settings regarding ascii/whitespace/transliteration/escaping/punycode/etc.
  • Achieving the same goal via different means (Upload New Media vs. drag-n-drop in editor) should result in the same outcome. Otherwise this is an inconsistency.

Analysis & Fix

@adamsilverstein already analyzed and fixed this bug in the Gutenberg issue tracker and asked to re-file here in WordPress Core for review & adding to the codebase.

Adam's Analysis

This is actually something that happens on the core side where the logic to set the title is currently different in the REST API vs. the regular media uploader.

Adam's Fix which should be reviewed

I proposed a fix in ​WordPress/wordpress-develop #3981 that works in my testing. Would be good to have some additional feedback, maybe from the REST API team.

Environment

• First ​reported on 2021-08-19 in WordPress v5.8 , ​confirmed/patched in 2023-02 on a WordPress v6.1.1 instance.

Priority

• If the fix is deemed solid and the review process goes quickly without bumps: Is there a chance that the fix can make it into the 6.2 release? If not, no worry, am happy whenever this will get eventually fixed.

References

• Gutenberg: ​Discussion and investigation details where it was determined to be a Core issue.

[audrasjb]

Hello and thanks for the detailed ticket!

This is an annoying bug, but since it wasn't introduced in WP 6.2 development cycle and as we're about to release RC3, it's far too late to fix it during this cycle :)

We can of course fix it in 6.3, but we can also consider this for 6.2.1. For the moment, I'm moving it to 6.2.1 for visibility.

[abitofmind]

Thanks for the first reaction. 6.2.1 then, certainly good!

Match the naming behavior for uploaded media in the REST API to the way media is named when uploading in the media library.

Fixes ​https://github.com/WordPress/gutenberg/issues/34149

Trac ticket: https://core.trac.wordpress.org/ticket/57957

[hellofromTonya]

Adding a link to the original bug report from Gutenberg.

Description updated. This PR is now linked to the Trac ticket ✅

@adamsilverstein are there existing unit tests to validate this fix? If no, would you mind adding tests?

[adamsilverstein]

@adamsilverstein are there existing unit tests to validate this fix? If no, would you mind adding tests?

Good suggestion @hellofromTonya, will do.

I'd also like to get some more REST API component maintainer feedback, maybe @TimothyBlynJacobs or @spacedmonkey can review?

@adamsilverstein are there existing unit tests to validate this fix? If no, would you mind adding tests?

I'll take a look, thanks for the suggestion.

Any idea when this will be ready?
And if it is ready, in which WP version will it be included?

Asking to estimate for myself whether my upcoming mass picture placement session can count on this feature already or whether I must use a workaround. Thanks.

[audrasjb]

Since WordPress 6.2.1 Release candidate 1 is planned today, let's move this ticket to 6.2.2 to give it more time to add unit test cases and proper testing.

[abitofmind]

And regarding unit tests: What's the holdup? Any progress?

[audrasjb]

@abitofmind for the moment, this patch still needs unit tests.

Anyone is welcome to refresh the patch to add unit test cases, so this ticket could be considered for the next minor or major release.

[abitofmind]

My question is: What's the challenge with the unit tests? And what timeline to expect roughly.

[audrasjb]

No specific challenge, we are just waiting for someone wanting to handle them. No timeline for now as we're still waiting for these tests :)

[desrosj]

Moving this to 6.2.3.

[abitofmind]

#44789 was marked as a duplicate.

[abitofmind]

I now found #33789 which is already known for 5 years, and still unfixed.