Hi @rmolina79
Thanks for using PublishPress Future.
Can you please inform me few informations?
- What PHP version are you using?
- What PublishPress Future version are you using?
- What WordPress version are you using?
- Inform me all plugins installed on your site.
Thanks,
Hi! Thanks for your quick answer.
I didn’t tell you that the post to auto erase is a custom postype.
- What PHP version are you using?: 7.4
- What PublishPress Future version are you using?. Last version download from here.
- What WordPress version are you using? 6.2.2
- Inform me all plugins installed on your site:
Adminimize
Disable Comments
Classic Editor
Elementor
Elementor Pro
Hide Admin Bar Based on user roles
iThemes Security
Jet Elements for Elementor
Jet Engine
JetEngine Post Expiration Period Module
JetSmart Filters
Login Logout Register Menu
LoginPress
Smush
SVG Support
User Menus
Visibility Logic for Elementor
WPCode Lite
WPFront Scroll Top
Yoast Duplicate Post
Yoast SEO
Hi @rmolina79
Thanks for the information. Please, could you doule check if the file
/home2/budatrav/public_html/wp-content/plugins/post-expirator/vendor/woocommerce/action-scheduler/classes/schema/ActionScheduler_StoreSchema.php
exists on the site?
I had deleted the plugin so I don’t know if that file was there.
Now I reinstalled it and it’s there.
My site doesn’t have woocoomerce. It doesn’t matter?
No problem, thanks @rmolina79
Thanks for double checking.
No, it WooCommerce is not required. It is part of that path because WooCommerce is the author of the referenced library.
This is the only report we have for now for the issue and we can’t replicate it here. Please, could you let us know if that happens on every page load, or only on post expiration tasks that run in the background?
Please, could you also try disabling all the other plugins on a staging site to see if you still have the issue?
Hi! Thanks for the answer.
It only happens on post expiration tasks that run in the background.
I can’t disable the others plugin because is a web of a client and they’re using it daily.
Regards!
Thanks for the information. We still can’t replicate, or find the path it is following to break.
Is there any chance to temporarily activate XDebug on the site in order to retrieve a trace of the files and methods executed when that exception occurs?
We have a new beta package addressing other bugs, feel free to test it and check if it fixes the bug you found.
https://1drv.ms/u/s!AsIYGyKS9Y3YozD5oAoprfXTJmXf?e=RW9IKF
Please, let us know the results.
Thanks
We haven’t heard back from you in a while, so I’m going to mark this as resolved. If you have any further questions, please reply again here, or you can start a new thread.
Thanks,
