Hi @wimkroegman,
I’ve checked out the plugin, and I think I found a way to make it work. I’ll post a beta version for you to try today or tomorrow.
Best regards,
Anton
@wimkroegman , could you please grab the beta release from https://github.com/av3nger/cf-images/releases/tag/1.1.5-beta.1, replace the plugin files and see if it fixes the problem?
Best regards,
Anton
Wow, works like a charm.
Thank you so much for your quick response and solution Anton!
Awesome. Glad that it worked. I’ll mark this thread as resolved. If you do have any other questions, please feel free to open a new one 😉
Best regards,
Anton
Hi Anton, apparently it works for images in posts but creates an error for featured/WooCommerce images. See below:
Trying to access array offset on value of type bool in wp-content/plugins/cf-images/app/class-core.php on line 787
Trying to access array offset on value of type bool in wp-content/plugins/cf-images/app/class-core.php on line 797
@wimkroegman , sorry for that, fixed. I’ve updated the files in the link above.
Best regards,
Anton
Thx! Almost there Anton.
I’m now (also previous beta) running into an issue that the plugin doesn’t work on Flywheel hosting. 1.1.4 does work. I think it has todo with the fact that wp-config is not writable at Flywheel (need to ask support to add needed rules). It’s also imposable to delete the plugin via wp-admin. Only via ftp. See below for error log (limited to what Flywheel gives).
PHP Warning: fopen(/wordpress/wp-config.php): Failed to open stream: Permission denied in /www/wp-content/plugins/cf-images/App/Settings.php on line 168″
[05-Feb-2023 08:30:31] WARNING: child 219 said into stderr: “NOTICE: PHP message: PHP Fatal error: Uncaught TypeError: fwrite(): Argument #1 ($stream) must be of type resource, bool given in /www/wp-content/plugins/cf-images/App/Settings.php:169”
[05-Feb-2023 08:30:31] WARNING: child 219 said into stderr: “Stack trace:”
[05-Feb-2023 08:30:31] WARNING: child 219 said into stderr: “#0 /www/wp-content/plugins/cf-images/App/Settings.php(169): fwrite(false, ‘write(‘/wordpress/wp-c…’, Array)”
[05-Feb-2023 08:30:31] WARNING: child 219 said into stderr: “#2 /www/wp-content/plugins/cf-images/uninstall.php(45): CF_Images\App\Settings->write_config(‘CF_IMAGES_ACCOU…’)”
[05-Feb-2023 08:30:31] WARNING: child 219 said into stderr: “#3 /wordpress/wp-admin/includes/plugin.php(1241): include_once(‘/www/wp-content…’)”
[05-Feb-2023 08:30:31] WARNING: child 219 said into stderr: “#4 /wordpress/wp-admin/includes/plugin.php(958): uninstall_plugin(‘cf-images/cf-im…’)”
[05-Feb-2023 08:30:31] WARNING: child 219 said into stderr: “#5 /wordpress/wp-admin/includes/ajax-actions.php(4698): delete_plugins(Array)”
[05-Feb-2023 08:30:31] WARNING: child 219 said into stderr: “#6 /wordpress/wp-includes/class-wp-hook.php(308): wp_ajax_delete_plugin(”)”
[05-Feb-2023 08:30:31] WARNING: child 219 said into stderr: “#7 /wordpress/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(”, Array)”
[05-Feb-2023 08:30:31] WARNING: child 219 said into stderr: “#8 /wordpress/wp-includes/plugin.php(517): WP_Hook->do_action(Array)”
[05-Feb-2023 08:30:31] WARNING: child 219 said into stderr: “#9 /wordpr…”
You can add those defines via Flywheel support. They do it within minutes.
Best regards,
Anton
Yes I understand, but that’s not what I meant. These defines are already added. So it works with version 1.1.4, but it goes wrong with 1.1.5 beta
@wimkroegman , those might just be leftover logs from when you replaced the 1.1.4 with 1.1.5. Because the new version has a bit different file structure, and I can see in the logs that the files are from the old version. I tried running this on my Flywheel test site, and it was fine, there were some other issues, which I’ve fixed and updated the beta file.
Best regards,
Anton
Sorry Anton, but I still have this issue. See below for errors in inspector.
Refused to apply style from ‘wp-content/plugins/cf-images-1.1.5-beta.1/assets/css/cf-images.min.css?ver=1.1.5-beta.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
GET /wp-content/plugins/cf-images-1.1.5-beta.1/assets/js/cf-images.min.js?ver=1.1.5-beta.1 net::ERR_ABORTED 404
Refused to execute script from ‘/wp-content/plugins/cf-images-1.1.5-beta.1/assets/js/cf-images.min.js?ver=1.1.5-beta.1’ because its MIME type (‘text/html’) is not executable, and strict MIME type checking is enabled.
Ok, my initial reply is been held for moderation. Will try to post now without actual URL’s
Refused to apply style from ‘/wp-content/plugins/cf-images-1.1.5-beta.1/assets/css/cf-images.min.css?ver=1.1.5-beta.1’ because its MIME type (‘text/html’) is not a supported stylesheet MIME type, and strict MIME checking is enabled.
GET /wp-content/plugins/cf-images-1.1.5-beta.1/assets/js/cf-images.min.js?ver=1.1.5-beta.1 net::ERR_ABORTED 404
Refused to execute script from ‘/wp-content/plugins/cf-images-1.1.5-beta.1/assets/js/cf-images.min.js?ver=1.1.5-beta.1’ because its MIME type (‘text/html’) is not executable, and strict MIME type checking is enabled.
Somehow, I did not receive a notification for you reply, and I just saw that this hasn’t been answered. Not sure if it’s still relevant. But, in any case, the errors above are usually host-based. And you’d need to contact your hosting support to get them fixed. Mime types are set up within the Apache/Nginx config files.
Best regards,
Anton
