Nico Marcuz
Forum Replies Created
-
Forum: Plugins
In reply to: [WooCommerce] Error warning@cfm168 same here
PHP Warning: Attempt to read property “order_awaiting_payment” on null in /xxx/wordpress/wp-content/plugins/woocommerce/includes/wc-cart-functions.php on line 187
Forum: Plugins
In reply to: [Unite Gallery Lite] Is there still support for Unite Gallery Pro?are you using the pro (pay!) version?
thnx Takayuki
Good morning Takayuki!
Thank you very much for your quick response.
We work with the Generate Press theme (current Pro version).The plugins we use are:
- Advanced Custom Fields PRO
- Borlabs Cookie – Cookie Opt-in
- Classic Editor
- Contact Form 7
- Custom Post Type UI
- Elementor Pro
- Elementor
- GP Premium
- Post Types Order
- Product Filter for WooCommerce
- WooCommerce
- Yoast SEO Premium
- Yoast SEO
- WP Grid Builder – Elementor
- WP Grid Builder
- WP Rocket
- wpDiscuz
Hi John,
yes, the error only occurred when updating the plugin to the current version.
We have updated from the last current version to the most current version.
Maybe this will help you a little further in troubleshooting.
Forum: Plugins
In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: noneWith pleasure. i did it some time ago.
Forum: Plugins
In reply to: [Unite Gallery Lite] Unite Gallery Lite Vulnerability@davidritter Are you using the Lite or the Pro version?
Forum: Plugins
In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: noneThank you for the explanation. I understood everything.
I think we can close this ticket.
best regards
NickForum: Plugins
In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: noneHi Saif,
I understand what the task “woocommerce_cleanup_rate_limits” is responsible for. However, since no action is assigned to the task, I thought that the task could not be executed properly if it was required by WooCommerce.
Just for my understanding the additional question:
Do I understand correctly that if WooCommerce requires the task “woocommerce_cleanup_rate_limits” then an action is dynamically assigned to this task?
Forum: Plugins
In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: noneGood morning Igor. Many thanks for your feedback.
Sorry that I’m asking here again: I understand that as you write, the cron event is set to run but that there is no function stored that should be processed when it is run. Understood everything.
This is exactly what worries us about the woocommerce_cleanup_rate_limits cron job.
Does your last sentence “This issue frequently arises when plugins fail to clear their cron events upon deactivation. It is probable that these can be safely removed” mean that an external plugin may have caused this problem and that we should delete the cron job “woocommerce_cleanup_rate_limits” to fix the problem?
Sorry for the trouble!
Forum: Plugins
In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: noneGood morning Igor!
Many thanks for your feedback. If we see it correctly, these two tasks should be performed on a daily basis. If this assumption is correct, is it okay that there is no entry in “Action”? (See the screenshot).
2023-06-13_08h10_13.pngForum: Plugins
In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: noneGodd morning @xue28 ,
What is the function of the two tasks woocommerce_cleanup_rate_limits and woocommerce_tracker_send_event? What should they do in principle?
Forum: Plugins
In reply to: [WooCommerce] WC Cronjob tasks . Here: Action: noneHi @anastas10s,
I am sending you a screenshot of the WooCommerce task in the cron stack. There you can also see the tasks that have not been assigned an action.
2023-06-07_17h09_19.pngDo you need more information?
We can reproduce the error at any time by clicking on the “Tools” tab under WooCommerce.
Result see screenshot here: https://immarketingforum-my.sharepoint.com/:i:/g/personal/marcuz_hello-world_net/ERh1jRgSLrdNnfg6p3EkxcIBw1Ps_0lqhxFJla7Vkzojag?e=nFYPmg
Hi John, we have just updated the current WooCommerce version as well as Query Monitor to the current version on our production site. Unfortunately the error persists.
However, the live site is still running on WordPress version 6.1.3. Could it be because the error continues to appear?