Title: Error when opening CPT Last modified: January 3, 2024 --- # Error when opening CPT * Resolved [christiaanroberts](https://wordpress.org/support/users/christiaanroberts/) * (@christiaanroberts) * [2 years, 3 months ago](https://wordpress.org/support/topic/error-when-opening-cpt/) * Hello, * I am having a problem with the plugin since one of the last updates. When I open the CPT to which Future Posts is linked I get an error message. Sorry, the error message is in Dutch. * ```wp-block-code Een fout van het type E_ERROR werd veroorzaakt op regelnummer 120 van het bestand /home/brc/domains/babyandchild.nl/public_html/wp-content/plugins/post-expirator/src/Modules/Expirator/Models/PostTypeDefaultDataModel.php. Foutmelding: Uncaught Exception: Invalid date/time offset "01 jun 2024" for post type "evenementen" in /home/brc/domains/babyandchild.nl/public_html/wp-content/plugins/post-expirator/src/Modules/Expirator/Models/PostTypeDefaultDataModel.php:120 Stack trace: #0 /home/brc/domains/babyandchild.nl/public_html/wp-content/plugins/post-expirator/src/Modules/Expirator/Controllers/QuickEditController.php(189): PublishPress\Future\Modules\Expirator\Models\PostTypeDefaultDataModel->getActionDateParts() #1 /home/brc/domains/babyandchild.nl/public_html/wp-includes/class-wp-hook.php(324): PublishPress\Future\Modules\Expirator\Controllers\QuickEditController->enqueueScripts() #2 /home/brc/domains/babyandchild.nl/public_html/wp-includes/class-wp-hook.php(348): WP_Hook->apply_filters() #3 /home/brc/domains/babyandchild.nl/public_html/wp-includes/plugin.php(517): WP_Hook->do_action() #4 /home/brc/domains/babyandchild.nl/public_html/wp-admin/admin-header.php(139): do_action() #5 /home/brc/domains/babyandchild.nl/public_html/wp-admin/edit.php(411): require_once('...') #6 {main} thrown ``` * Installed the 3.1.7-beta2 just to be sure, but this does not solve the problem. * Thanks, * Christiaan Viewing 6 replies - 1 through 6 (of 6 total) * Plugin Support [Riza Maulana Ardiyanto](https://wordpress.org/support/users/rizaardiyanto/) * (@rizaardiyanto) * [2 years, 3 months ago](https://wordpress.org/support/topic/error-when-opening-cpt/#post-17315448) * Hi [@christiaanroberts](https://wordpress.org/support/users/christiaanroberts/) * I did not face this issue in our testing. Can you give us more details? * Does this issue happens in Classic Editor? Or happen both on Block Editor as well? * Thread Starter [christiaanroberts](https://wordpress.org/support/users/christiaanroberts/) * (@christiaanroberts) * [2 years, 3 months ago](https://wordpress.org/support/topic/error-when-opening-cpt/#post-17317397) * Hello Riza, * Thank you for your response. * I have a CPT called “Events”. When I try to open the list of posts within this CPT, the error message comes up. It is not possible to open the list or posts within this CPT when Future Posts is active. * What I have tried: - Disabled all plugins except Future posts - Removed the message mentioned in the error with date 01 Jun 2024 * Both do not resolve the error. Only after deactivating Future Posts I can access the CPT again. * We have been using Future Posts for over 2 years now with no problems. Also no changes have been made within the configuration. This seems to be a problem that has occurred since one of the latest updates. * Thanks, * Christiaan - This reply was modified 2 years, 3 months ago by [christiaanroberts](https://wordpress.org/support/users/christiaanroberts/). * Plugin Support [Riza Maulana Ardiyanto](https://wordpress.org/support/users/rizaardiyanto/) * (@rizaardiyanto) * [2 years, 3 months ago](https://wordpress.org/support/topic/error-when-opening-cpt/#post-17317798) * [@christiaanroberts](https://wordpress.org/support/users/christiaanroberts/) Could you please check if your issue resolved in this latest beta? * [https://github.com/publishpress/PublishPress-Future/releases/download/3.1.7-beta.3/publishpress-future-3.1.7-beta.3.zip](https://github.com/publishpress/PublishPress-Future/releases/download/3.1.7-beta.3/publishpress-future-3.1.7-beta.3.zip) * Thread Starter [christiaanroberts](https://wordpress.org/support/users/christiaanroberts/) * (@christiaanroberts) * [2 years, 3 months ago](https://wordpress.org/support/topic/error-when-opening-cpt/#post-17317860) * [@rizaardiyanto](https://wordpress.org/support/users/rizaardiyanto/) I’ve installed the beta version 3, still an error. * Plugin Support [Riza Maulana Ardiyanto](https://wordpress.org/support/users/rizaardiyanto/) * (@rizaardiyanto) * [2 years, 3 months ago](https://wordpress.org/support/topic/error-when-opening-cpt/#post-17320015) * [@christiaanroberts](https://wordpress.org/support/users/christiaanroberts/) I’m still unable to see this error. Do you might know the steps to replicate this issue on a new fresh WordPress installation? * Plugin Author [Steve Burge](https://wordpress.org/support/users/stevejburge/) * (@stevejburge) * [2 years, 2 months ago](https://wordpress.org/support/topic/error-when-opening-cpt/#post-17355254) * Thanks for using PublishPress Future. We’ve not seen an update on this post in 2 weeks so are closing it for now. Please post back again if this remains an issue. Viewing 6 replies - 1 through 6 (of 6 total) The topic ‘Error when opening CPT’ is closed to new replies. * ![](https://ps.w.org/post-expirator/assets/icon-256x256.png?rev=3118683) * [Schedule Post Changes With PublishPress Future: Unpublish, Delete, Change Status, Trash, Change Categories](https://wordpress.org/plugins/post-expirator/) * [Frequently Asked Questions](https://wordpress.org/plugins/post-expirator/#faq) * [Support Threads](https://wordpress.org/support/plugin/post-expirator/) * [Active Topics](https://wordpress.org/support/plugin/post-expirator/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/post-expirator/unresolved/) * [Reviews](https://wordpress.org/support/plugin/post-expirator/reviews/) * 6 replies * 3 participants * Last reply from: [Steve Burge](https://wordpress.org/support/users/stevejburge/) * Last activity: [2 years, 2 months ago](https://wordpress.org/support/topic/error-when-opening-cpt/#post-17355254) * Status: resolved