Plugin update breaks all sites, regrettably a step backwards.

  • The latest update to this plugin is quite disappointing. It’s proven so problematic that we’ve had to resort to disabling updates altogether and securing the plugin against updates via an WP CLI command.

    function disable_bunnycdn_update( $update ) {
unset( $update->response['bunnycdn/bunnycdn.php'] );
return $update;
}
add_filter( 'site_transient_update_plugins', 'disable_bunnycdn_update' );

    added a zero byte file in bunnycdn > called bunnycdn-update-lock < located in the public_html/wp-content/plugins/bunnycdn directory

    It appears we’ll need to seek an alternative solution, as the new plugin’s is overly bloated now, I hope that can be corrected, and it’s still missing key features we’ve been requesting for quite some time.

    Apart from this issue, the service remains exceptional. It seems like we’re faced with a trade-off: either develop a custom solution using an API or settle for a basic plugin to manage the CDN, sacrificing many essential features the service can offer.

    It’s puzzling how this flawed update slipped through R&D — We are genuinely surprised and disappointed.

  • The topic ‘Plugin update breaks all sites, regrettably a step backwards.’ is closed to new replies.