ScientiaMobile
Forum Replies Created
-
Apologies for late reply here… Depending on how you load the fonts, it may be a cross domain issue (CORS). If your not able to address that on your end, you can fix this in the ImageEngine control panel by tuning your CORS settings: https://support.imageengine.io/hc/en-us/articles/4409652734733-Customizing-Engine-Image-delivery-
Forum: Reviews
In reply to: [WP ImageEngine Responsive Image Resizer] Complicated and IntrusiveThank you for your feedback. I agree it is not obvious that images will get watermarked when the plugin is activated with no valid token provided. I understand that this may cause issues when testing the plugin directly in a production environment. We’ll make that clearer.
Forum: Plugins
In reply to: [WP ImageEngine Responsive Image Resizer] Plugin Leaves Traces After DeletionIn that case there has been an additional WP plugin or CDN caching the images and/or the markup.
Forum: Reviews
In reply to: [WP ImageEngine Responsive Image Resizer] Complicated and IntrusiveSorry to hear about the long response time. The process of issuing tokens is manual, so it takes some time. With no token however, images will get watermarked so don’t activate the plugin until you receive a valid token.
Forum: Plugins
In reply to: [WP ImageEngine Responsive Image Resizer] Plugin Leaves Traces After DeletionYou’ll have to deactivate the plugin from the Plugins page and click “Deactivate” under the ImageEngine plugin. If you don’t do that, and just delete the files, the database will still contain information that may make trouble for you.
Yes it is compatible, plug and play.
Only thing is if you’ve done something fancy in the CDN section of w3 total cache. If your images are hosted on a different host than the wordpress instance, you’d have to make sure things happen in the correct order. ImageEngine could either get the images directly from the WP instance, or from your CDN/file host. It’s up to you.Forum: Plugins
In reply to: Jetpack’s Photon and wp_get_attachment_image_src()There is something fishy here since
src
andsrcset
are handled differently by photon. I found a workaround that feels a bit hacky.First do this
if ( class_exists( 'Jetpack' ) && Jetpack::is_module_active( 'photon' ) ) { add_filter( 'jetpack_photon_skip_for_url', '__return_true' ); }
Then, set the priority of the filter for the
wp_calculate_image_srcset
hook to 11 so that it will run after other JetPack filters I’ve found which has prio 10.Forum: Plugins
In reply to: Jetpack’s Photon and wp_get_attachment_image_src()Problem identified:
https://github.com/Automattic/jetpack/blob/master/class.photon.php#L620
is basically overwriting the URL already changed by my filter ??Forum: Plugins
In reply to: Jetpack’s Photon and wp_get_attachment_image_src()Update:
Now, it looks like my function works as expected by adding a new url to the$sources
array
$sources[$size]['url'] = $new_url;
When I dump the array, it contains what I expect (more or less). But by magic, this is photonized at a later stage… No idea where/when…Forum: Plugins
In reply to: [WP ImageEngine Responsive Image Resizer] Uninstall?Yes, then your images would be as your WordPress install choose to treat them by default or by other plugins you use.
Yes, feedback makes total sense. If you cross the threshold, you images will still be served. But you’ll get a friendly reminder that you’re above limit and of course a recommendation to upgrade. The next month you’ll start at 0 again.
Norm,
Yes that is the current model. $100 minimum charge. Though, the free option is quite spacious. If you still feel you need the premium option, I suggest you shoot an email to [email protected] to see if they can help you with a more suitable option.