Huge error_log due to plugin PHP warnings

I have not had a free moment to go actually check that due to being in midst of PCI-DSS ‘attack scanning’ right now. But I will, as now you have me darn curious about that, since we run multiple sites with AMP.

I’m assuming you have looked at your amp page source to see if there is a broken sitename tag in there ?

Sorry that you ran into these issues.

Two thoughts:
– I’d suggest doing size-based log rotation as well to prevent issues when the log file gets too big.
– The errors are happening when an image included in a post doesn’t have an explicit size available (usually a hotlinked image), in which case we remotely fetch it and attempt to guess it’s size. The errors are being generated from the class we use to do this (although, technically, the lower-level PHP APIs are throwing the errors), most likely because it failed to properly fetch or read the image. It’s possible the resource where the images are hosted is having issues? Or maybe remote connections are blocked on the server? Or maybe there’s a bug in the plugin 🙂

If you want to disable this remote image lookup, you can use the following code:

add_action( 'amp_extract_image_dimensions_callbacks_registered', 'xyz_amp_extract_image_dimensions_disable_remote_lookup' );
function xyz_amp_extract_image_dimensions_disable_remote_lookup() {
	remove_filter( 'amp_extract_image_dimensions', array( 'AMP_Image_Dimension_Extractor', 'extract_by_downloading_image' ), 999, 2 );
}