shoaibahmd
Forum Replies Created
-
@vanyukov
Is there a way I can find what image is exactly blocking the bulk deletion?Another concern
Total number of images on media library is around 70k and the total offloaded are images are around 40K, and when we hit Bulk Offload then it says “No new images to process”Hi Anton,
Thanks for the clarification.
Although I am getting error while Bulk deleting images (experimental feature). Can’t proceed with Bulk deletion due to this error.
ERROR: Cannot remove image, Scaled image offloadedOhh that’s why It was breaking in the first place on checkout. and I was thinking it was a bug in the plugin.
BTW Thanks Anton.I just fixed the issue by applying below filter
add_filter( ‘cf_images_attachment_meta’, function( $cloudflare_image_id, $attachment_id ) {
$cloudflare_image_id = str_replace( ‘staging.myhomecloset.com’, ‘myhomecloset.com’, $cloudflare_image_id );
return $cloudflare_image_id;
}, 10, 2 );
Before the upgrade I was getting below error on place order woocommerce checkout, that’s why I had to upgrade to 1.9.8 version.
CF_Images\App\Modules\Cloudflare_Images::replace_staging_domains_in_attributes() must be of the type string, array given, called in /home/1431997.cloudwaysapps.com/fammafmjgx/public_html/wp-includes/class-wp-hook.php on line 341 and defined in /home/1431997.cloudwaysapps.com/fammafmjgx/public_html/wp-content/plugins/cf-images/app/modules/class-cloudflare-images.php:595 Additional context{ “error”: { “type”: 1, “file”: “/home/1431997.cloudwaysapps.com/fammafmjgx/public_html/wp-content/plugins/cf-images/app/modules/class-cloudflare-images.php”, “line”: 595 }, “remote-logging”: true, “backtrace”: [ “”, “#0 /home/1431997.cloudwaysapps.com/fammafmjgx/public_html/wp-includes/class-wp-hook.php(341):I actually upgraded the plugin to 1.9.8, before the upgrade I was using the production offloaded images on staging environment. they were loading perfectly. but suddenly after the upgraded, all the images were unable to load hence I found out that now the url contain staging prefix before the domain, which leads to 404. If I remove the staging prefix manually by browser inpect element then the images loads successfully, since the image was offloaded from production.
Now I can’t offload the images again from staging environment, since its space and time taking. I need a workaround to get the exact same url as production environment on staging environment (without the staging prefix inside it).
I can’t understand your below point:
“But in the context of Cloudflare Images, you shouldn’t really worry about this. Let staging use production images”
How exactly? the url is auto-generated and contains staging prefix 🙁