Title: Error after plugin update Last modified: December 1, 2023 --- # Error after plugin update * Resolved [Erick](https://wordpress.org/support/users/relozo/) * (@relozo) * [2 years, 6 months ago](https://wordpress.org/support/topic/error-after-plugin-update-13/) * Hi, I recently updated Kadence to Version 3.1.26 and I am getting thrown this error when I try to edit a block. * `ErrorException: Attempt to read property "base" on null in file /wp-content/ plugins/kadence-blocks/includes/class-kadence-blocks-image-picker.php on line 73` * Is there a known issue with this one? Viewing 9 replies - 1 through 9 (of 9 total) * Plugin Contributor [Gilbert Hernandez](https://wordpress.org/support/users/ghernkadence/) * (@ghernkadence) * [2 years, 5 months ago](https://wordpress.org/support/topic/error-after-plugin-update-13/#post-17247657) * Hello [@relozo](https://wordpress.org/support/users/relozo/), * I haven’t found any other similar reports. The error you posted appears to be related to the Pexels image picker that Kadence provides. The error says that the [get_current_screen()](https://developer.wordpress.org/reference/functions/get_current_screen/) function on line 73 returns null. * Can you provide more details on how the error is generated so we can try to recreate it? Can you list the steps you took to trigger the error? * Thread Starter [Erick](https://wordpress.org/support/users/relozo/) * (@relozo) * [2 years, 5 months ago](https://wordpress.org/support/topic/error-after-plugin-update-13/#post-17247827) * Hi, thanks for replying. * I did more testing and it seems like it happened after updating another plugin– Advanced custom fields pro to the latest 6.2.4. * Does the plugin support that compatibility? * Thread Starter [Erick](https://wordpress.org/support/users/relozo/) * (@relozo) * [2 years, 5 months ago](https://wordpress.org/support/topic/error-after-plugin-update-13/#post-17249360) * I modified the code on line 73 and it seems to have fixed the issue in my case temporarily. I found that the problem is not related to ACF, but it started on Kadence version 3.1.16 with the introduction of Pexels. I’ve already disabled the option in wp-config, but the issue persisted. * `// $current_screen = is_admin() && function_exists( 'get_current_screen' ) ? get_current_screen()->base : '';` * `$current_screen = is_admin() && function_exists( 'get_current_screen' ) ? get_current_screen(): null;` * `$current_screen_base = is_object( $current_screen ) ? $current_screen->base :'';` * `if ( $this->image_picker_has_access() && $is_option_enabled && 'upload' !== $current_screen_base ) {` * Plugin Contributor [Gilbert Hernandez](https://wordpress.org/support/users/ghernkadence/) * (@ghernkadence) * [2 years, 5 months ago](https://wordpress.org/support/topic/error-after-plugin-update-13/#post-17254612) * Hello [@relozo](https://wordpress.org/support/users/relozo/), * Do the errors only appear when you use the ACF Pro plugin v6.2.4? You mentioned the problem occurred after you updated ACF pro. Can you confirm the problem doesn’t occur on 6.2.3? * Unfortunately, ACF Pro isn’t a plugin I have access to for testing. I’ll mention this thread to the developers for them to review. * Thread Starter [Erick](https://wordpress.org/support/users/relozo/) * (@relozo) * [2 years, 5 months ago](https://wordpress.org/support/topic/error-after-plugin-update-13/#post-17254985) * Hi, I did more testing and the issue occurred even at 6.2.3 * No worries at all. I am just hoping that the solution I did is a workaround for the error I am encountering. * Plugin Contributor [Gilbert Hernandez](https://wordpress.org/support/users/ghernkadence/) * (@ghernkadence) * [2 years, 5 months ago](https://wordpress.org/support/topic/error-after-plugin-update-13/#post-17255161) * Hello [@relozo](https://wordpress.org/support/users/relozo/), * I received word from the developer. A fix will be released in the next update. Thank you for reporting the problem and providing your feedback. * [phillt](https://wordpress.org/support/users/phillt/) * (@phillt) * [2 years, 5 months ago](https://wordpress.org/support/topic/error-after-plugin-update-13/#post-17301704) * Same for me : the following error : **Warning**: Attempt to read property “base” on null in **/home/xxxxxxx/www/wp-content/plugins/kadence-blocks/includes/class- kadence-blocks-image-picker.php** on line **73**is there for many month already, it’s just an annoying warning i get on the backoffice. I use Astra theme, Custom Post Type UI among others if it can help…Thanks * Plugin Contributor [Gilbert Hernandez](https://wordpress.org/support/users/ghernkadence/) * (@ghernkadence) * [2 years, 5 months ago](https://wordpress.org/support/topic/error-after-plugin-update-13/#post-17304281) * Hello [@phillt](https://wordpress.org/support/users/phillt/), * The fix hasn’t been released to the WP repository. Currently, Kadence Blocks 3.2 is in beta status and available for pre-release testing at Kadencewp.com. * [Brian – TGL](https://wordpress.org/support/users/w411/) * (@w411) * [2 years, 4 months ago](https://wordpress.org/support/topic/error-after-plugin-update-13/#post-17382525) * I just updated from 3.1.22 to 3.2.19 and the warnings have stopped in my PHP Error Log. Viewing 9 replies - 1 through 9 (of 9 total) The topic ‘Error after plugin update’ is closed to new replies. * ![](https://ps.w.org/kadence-blocks/assets/icon-256x256.png?rev=3178382) * [Kadence Blocks — Page Builder Toolkit for Gutenberg Editor](https://wordpress.org/plugins/kadence-blocks/) * [Frequently Asked Questions](https://wordpress.org/plugins/kadence-blocks/#faq) * [Support Threads](https://wordpress.org/support/plugin/kadence-blocks/) * [Active Topics](https://wordpress.org/support/plugin/kadence-blocks/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/kadence-blocks/unresolved/) * [Reviews](https://wordpress.org/support/plugin/kadence-blocks/reviews/) * 9 replies * 4 participants * Last reply from: [Brian – TGL](https://wordpress.org/support/users/w411/) * Last activity: [2 years, 4 months ago](https://wordpress.org/support/topic/error-after-plugin-update-13/#post-17382525) * Status: resolved