Context Navigation

Changes between Version 1 and Version 2 of Ticket #63294, comment 6

-              v1
+              v2
 Also this works without issues in older versions i.e. 6.7.1 and 6.7.2. The problem was introduced in 6.8 seems.
+**Edit:**
+I nailed it down to new code introduced in function **create_item_permissions_check()** in version 6.8.
+Further down the code it appears that** wp_image_editor_supports()** returns false if image editing lirary is not enabled on server.
+I believe this is not a correct approach since whether file can be edited or not should not determine whether file can be uploaded or not. Not all servers have support for Imagick or GD and these should not be punished if admins are not planning to use image editing feature in a first place.
+**Workaround**
+Together with the new code mentioned above a new filter was introduced in WP 6.8: **wp_prevent_unsupported_mime_type_uploads**
+It can be used to disable this new behaviour.
+Nuclear option would be:
+{{{#!php
+<?php
+add_filter( 'wp_prevent_unsupported_mime_type_uploads', '__return_false' );
+}}}
+More gradual option would be to expand the function to check what mime type is passed and return false only for images or whatever other file type affected in your project.
+The filter function passes mime type string. So, it could be something like this:
+{{{#!php
+<?php
+add_filter( 'wp_prevent_unsupported_mime_type_uploads', function($current, $mime) {
+        return str_starts_with( $mime, 'image/' ) ? false : $current;
+}, 10, 2);
+}}}