|
imran nathani
|
October 3, 2019 at 11:44 am
So this has been an ongoing issue and for events where we have limited spots I have had to manually go in and trash the registrations to clear up active spots.
So troubleshooting steps I have taken so far are
-I tried scheduling a post to ensure cron is enabled, (wp did post it at the requested time)
-I installed wp cron events and this is what the last couple of lines are in the log
AHEE__EE_Cron_Tasks__expired_transaction_check
[
2809
]
EE_Cron_Tasks::expired_transaction_check()
2019-10-02 21:15:51 (now) Non-repeating Edit | Run Now | Delete
AHEE__EE_Cron_Tasks__expired_transaction_check
[
2810
]
EE_Cron_Tasks::expired_transaction_check()
2019-10-02 23:55:29 (now) Non-repeating Edit | Run Now | Delete
AHEE__EE_Cron_Tasks__expired_transaction_check
[
2811
]
EE_Cron_Tasks::expired_transaction_check()
2019-10-03 13:32:28 (now) Non-repeating
I can post the website and ticket links here to assist with the solving of this problem.
|
|
Josh
|
October 3, 2019 at 12:20 pm
Hi,
Something related to the cron scheduling & timing doesn’t seem right. Usually you would only see cron events for the future listed there. Instead, the cron events you’ve posted here are in the past (two from yesterday).
If you go to the Site Health > Tools page, Hi,
If you go to your site’s Tools > Site Health page, then wait about 30 seconds, does it show a message that says anything about a scheduled task failing?
|
|
imran nathani
|
October 3, 2019 at 12:40 pm
This is what the site health page shows.
|
|
imran nathani
|
October 3, 2019 at 12:41 pm
https://imgur.com/a/Wd7oqOj
not sure if the link in the img tag worked.
|
|
Josh
|
October 3, 2019 at 1:03 pm
It does say that a scheduled event has failed, and the
One thing you could try that may help is switch the site to use an alternative cron. This involves a one-line edit to the wp-config.php file, outlined here:
https://wordpress.org/support/article/editing-wp-config-php/#alternative-cron
Aside from that, you could try ruling out a plugin conflict or check with your host to see if they’ve added a different way of triggering scheduled tasks instead of using wp_cron.
|
|
imran nathani
|
October 4, 2019 at 5:32 am
Is there a way to change the time for the reset so i can elimiate plugins one at a time by trying it?
the switching the site to the alternative cron didnt work for the reset of tickets.
|
|
Josh
|
October 4, 2019 at 9:20 am
There is but you may not need to change the time for the session expiration, and probably shouldn’t if this is a live site taking registrations. Two reasons why: 1) Anyone trying to register will not be able to complete their registration and 2) If you still have cron tasks from the past that haven’t fired yet, then you’ve got what you need to troubleshoot plugins. Basically what you’re looking to happen is those older cron tasks that should have fired yesterday or earlier, they need to fire. In other words, if you deactivate a plugin, then check the cron tasks page and suddenly the older cron tasks get dropped from the list, then you may have found the plugin conflict.
|
|
imran nathani
|
October 8, 2019 at 9:18 am
Okay so idealy when an event triggers it runs the event and then goes away?
This is what the whole page looks like right now.
https://imgur.com/8x8d3Ux
So my next step would be to disable addons and then see if the list clears up or how would I know if its working.
Thanks!
|
|
Josh
|
October 8, 2019 at 9:28 am
Yes, you shouldn’t have months worth of old cron tasks listed there like that, normally there should only be future scheduled tasks.
One important thing at the top of that screenshot that maybe you didn’t catch:
WP_DISABLE_CRON is set to true. WP-Cron spawning is disabled.
You actually do not want that to be disabled, so it’s advised to remove that constant from the wp-config.php file.
|
|
imran nathani
|
October 11, 2019 at 1:42 pm
Okay, so I deleted the WP_DISABLE_CRON. It triggered and send 286 emails to people from last 6 months.. 🙁
I just went in and picked a ticket for an event and closed the tab.
I see `AHEE__EE_Cron_Tasks__expired_transaction_check
[
2826
]
EE_Cron_Tasks::expired_transaction_check()
2019-10-11 16:43:17 (58 minutes 14 seconds) Non-repeating`
I did this earlier today but it didn’t cancel the ticket and change the available number itself.
Any other suggestions?
|
|
Josh
|
October 11, 2019 at 2:19 pm
Hi,
When the EE_Cron_Tasks::expired_transaction_check() runs, it shouldn’t cancel the ticket, but the reserved count should decrement by 1. If you go in to view the scheduled tasks in Tools > Cron events, is there a scheduled task listed for the transaction you started? It will have the same transaction ID.
|
