Make WordPress Core

Changes between Initial Version and Version 1 of Ticket #64105, comment 1


Ignore:
Timestamp:
10/16/2025 03:47:19 PM (3 months ago)
Author:
nabilaminhridoy
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #64105, comment 1

    initial v1  
    11Hi there 👋
    22
    3 I’ve tested this issue on the latest **WordPress 6.8.3** with the **Classic Editor plugin (v1.6.3)** and can confirm that the problem still exists.
     3Hi everyone 👋
    44
    5 When trying to insert `.webp` or `.avi` files via the “Add Media” modal in TinyMCE, the files are not recognized or previewed correctly. 
    6 Meanwhile, the Block Editor supports `.webp` uploads and displays them as expected.
     5I’ve reproduced this issue on WordPress 6.8.3 with the Classic Editor plugin (v1.6.3).
    76
    8 This seems to be related to the allowed MIME types or TinyMCE’s media plugin configuration in the Classic Editor integration.
     7When inserting `.webm` or `.avi` video files through the Classic Editor (TinyMCE), they are not recognized or previewed properly. In contrast, the Block Editor supports these formats without any issue.
    98
    10 Steps to reproduce:
    11 1. Activate the Classic Editor plugin.
    12 2. Go to “Posts → Add New”.
    13 3. Click “Add Media” and try uploading a `.webp` or `.avi` file.
    14 4. The file is rejected or not displayed in the editor.
     9This indicates that the core media handler supports modern formats, but TinyMCE’s configuration or the allowed MIME types for the Classic Editor are limited to older formats (mp4, m4v, ogv, mov, wmv).
    1510
    16 Expected:
    17 The Classic Editor should handle `.webp` and modern video formats similar to the Block Editor.
     11**Possible fix direction:**
     12Add support for additional MIME types in TinyMCE initialization or extend `wp_get_mime_types()` for Classic Editor to include:
     13- `video/webm` → `.webm`
     14- `video/x-msvideo` → `.avi`
    1815
    19 If needed, I can help test or submit a patch for this.
     16I tested this on WP 6.8.3 and can confirm the issue still exists.
     17Happy to help test a patch if someone is working on this.
    2018
    2119@nabilaminhridoy