Use Jetpack Image CDN (formerly Photon) to proxy image uploads from another site.
| Author: | Philip Newcomer (profile at wordpress.org) |
| WordPress version required: | 3.0 |
| WordPress version tested: | 4.9.25 |
| Plugin version: | 1.0.0 |
| Added to WordPress repository: | 16-02-2018 |
| Last updated: | 16-02-2018
Warning! This plugin has not been updated in over 2 years. It may no longer be maintained or supported and may have compatibility issues when used with more recent versions of WordPress.
|
| Rating, %: | 0 |
| Rated by: | 0 |
| Plugin URI: | https://github.com/philipnewcomer/CDN-Image-P... |
| Total downloads: | 845 |
 Click to start download |
|
When developing locally, it’s common to use a database dump from a production site. With large sites, it’s also common that the production site’s image uploads cannot be easily copied to the local environment, because there are simply too many of them.
While local environments like Pilothouse allow you to easily proxy image uploads to your local environment from the production site, that doesn’t work so well if you add or change one of the registered thumbnail sizes in your local copy of the theme, since the new thumbnail size can’t be proxied from production as it doesn’t exist there. You’re also not able to regenerate the needed thumbnail sizes locally, because the original image file is not present locally.
CDN Image Proxy solves this problem by using Jetpack Image CDN (formerly Photon) to proxy image uploads from your production site. Jetpack Image CDN will automatically generate and serve any required thumbnail size on-the-fly, but CDN Image Proxy will tell it to look for the original image on your production server, rather than on your local URL.
The result is that you can add or change registered image sizes locally whenever you want, and Jetpack Image CDN will generate and provide a CDN URL for whatever thumbnail size is required, sourced from the original image file located on the production site.
FAQ
ChangeLog