Title: Expanded Editor compatibility Last modified: September 11, 2026 --- # Expanded Editor compatibility * [Matt Scheidler](https://wordpress.org/support/users/matt6303/) * (@matt6303) * [3 weeks, 6 days ago](https://wordpress.org/support/topic/expanded-editor-compatibility/) * The new version 6.0.6, just released, does not seem to correct the issue noted here: [https://wordpress.org/support/topic/cropping-doesnt-work-in-expanded-editor/](https://wordpress.org/support/topic/cropping-doesnt-work-in-expanded-editor/) * Might a version 6.0.7 incorporate the updated input-script.js file, or otherwise address this issue? * We’re using 6.0.5 with the replacement file, but would prefer to use the latest version of the plugin. * Thank you! Viewing 4 replies - 1 through 4 (of 4 total) * Plugin Author [joppuyo](https://wordpress.org/support/users/joppuyo/) * (@joppuyo) * [3 weeks, 6 days ago](https://wordpress.org/support/topic/expanded-editor-compatibility/#post-19017933) * Hello Matt! * As you can read in the changelog, the new 6.0.6 release is focused on security fixes. It does not add support for the “expanded editor”. * This plugin was released in 2018, shortly after ACF 5 came out. This version of ACF didn’t have an “expanded editor”. While I aim to keep this plugin updated with current ACF versions, I can’t anticipate when a new feature is introduced in ACF. * Because of this, the plugin will not automatically be compatible with every new ACF feature when they are released. * I hope you can understand! * However, I hope I will be able to add support for the “expanded editor” in a future release of this plugin. * Thread Starter [Matt Scheidler](https://wordpress.org/support/users/matt6303/) * (@matt6303) * [3 weeks, 6 days ago](https://wordpress.org/support/topic/expanded-editor-compatibility/#post-19017959) * Thank you for the reply! * I’ve been using your plugin for at least 6 years – maybe even the full 8 years since you first released it. It’s been a long time. I’ve got it running on 65 websites. * Right now, the plugin is completely useless if I update to your latest version. Our only option is to apply the fix that the other user was generous enough to share. * We tried updating to 6.0.6 and the functionality went away, so we reverted to 6.0.5 with the fix. Yet untested is whether we can apply that fix to the 6.0.6 version. I was hoping it could just be incorporated into the actual plugin so that we could safely begin updating again. * I understand that this user’s approach might not be exactly your own and you may wish to add support in a different way. But it works, and without it we cannot use your plugin. * Also, to note, I believe ACF had to update its approach to stay in step with WordPress core. It’s not really a new ACF feature but rather the move they had to make to maintain WP core compatibility. * Thanks again for taking the time to reply! - This reply was modified 3 weeks, 6 days ago by [Matt Scheidler](https://wordpress.org/support/users/matt6303/). * Plugin Author [joppuyo](https://wordpress.org/support/users/joppuyo/) * (@joppuyo) * [3 weeks, 6 days ago](https://wordpress.org/support/topic/expanded-editor-compatibility/#post-19018072) * Hello! * I understand that it is a frustrating situation. I can’t provide support for patches that are made by third parties. * However, I asked Claude to port the v6.0.5 path to v6.0.6, you can find the patched file here: * [https://gist.github.com/joppuyo/7ca3d082148a895f4ca91a54ef03b4d6](https://gist.github.com/joppuyo/7ca3d082148a895f4ca91a54ef03b4d6) * I tested it in my local development environment and it seemed to work with ACF blocks registered with version 3. * Please keep in mind that I don’t have any projects where I use block version 3. * This is the reason such support doesn’t exist in the plugin: I haven’t encountered this issue in any of my projects. * So I don’t give any guarantee that the patched version will work. * But please do test it and report if it works for you. * I’m planning on adding proper support for block version 3 in a future version of this plugin when I have tested that it works throughly. * [matlembo](https://wordpress.org/support/users/matlembo/) * (@matlembo) * [2 weeks, 2 days ago](https://wordpress.org/support/topic/expanded-editor-compatibility/#post-19026586) * In the same boat. I’ve been using and loving this plugin for years. Hoping for a patch soon otherwise will have to jump ship. Viewing 4 replies - 1 through 4 (of 4 total) You must be [logged in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fexpanded-editor-compatibility%2F%3Foutput_format%3Dmd&locale=en_US) to reply to this topic. * ![](https://ps.w.org/acf-image-aspect-ratio-crop/assets/icon-256x256.png?rev= 1908145) * [Image Aspect Ratio Crop Field for Advanced Custom Fields](https://wordpress.org/plugins/acf-image-aspect-ratio-crop/) * [Frequently Asked Questions](https://wordpress.org/plugins/acf-image-aspect-ratio-crop/#faq) * [Support Threads](https://wordpress.org/support/plugin/acf-image-aspect-ratio-crop/) * [Active Topics](https://wordpress.org/support/plugin/acf-image-aspect-ratio-crop/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/acf-image-aspect-ratio-crop/unresolved/) * [Reviews](https://wordpress.org/support/plugin/acf-image-aspect-ratio-crop/reviews/) * 4 replies * 3 participants * Last reply from: [matlembo](https://wordpress.org/support/users/matlembo/) * Last activity: [2 weeks, 2 days ago](https://wordpress.org/support/topic/expanded-editor-compatibility/#post-19026586) * Status: not resolved