Support

October 30, 2020 at 10:33 am

Hi ICLE,

There’s no error in that log entry, that looks like a response log from FirstData and shows the payment was Approved unless I’m missing something?

October 30, 2020 at 10:39 am

I’m going to remove the credentials posted on the forums (yes even though its private reply).

If you’ve purchased a support token to investigate this then please use the link to redeem your token on your account page (just below your license keys) to securely send us your login details and any additional details required.

October 30, 2020 at 1:04 pm

Unfortunately, I have no idea what you are going to find without reviewing the logs.

Each successful payment ‘should’ create 3 log entries

Payeezy sale request Parameters (the request from your site to FirstData)
Payeezy sale request Response (the response from them)
Post Payment Transaction Details (a log entry created by EE itself after the payment object has updated the transaction)

Entry isn’t an error, its the body of the response log and appears to be a successful payment. If you can send over the login details I’ll happily review the log entries for a transaction this has happened on.

https://eventespresso.com/send-login-details/

(Note that we generally require a support token to troubleshoot directly on the server, without one I’ll review the logs and see if anything stands out but if you need further troubleshooting you’ll need a support token)

November 16, 2020 at 10:04 am

Ok, so that’s actually a totally different issue.

The issue you are referring to is when the AHEE__EE_Messages_Scheduler__sending and AHEE__EE_Messages_Scheduler__generation WP_Cron jobs would randomly disappear from the cron events.

It looks like a core WP issue as all we do is add the job and then it’s somehow lost. But, in either case, what we did to fix that was add a check into 4.10.8.p which runs on the AHEE__EE_Messages_Scheduler__cleanup and confirms that the other 2 jobs are available every hour.

They stated that they didn’t know the cause of the issue. In WP control, when you edit the hooks, it says:

“Cron events trigger actions in your code. A cron event needs a corresponding action hook somewhere in code, e.g. the functions.php file in your theme.”

In short and with all due respect, whoever is helping you here needs to learn more about how WP_Cron works, that has nothing to do with the issue you are referring to.

That snippet is basically telling you that you WP_Cron takes a schedule and a function to call and you can’t just schedule a task without having a function to call for that task. EE already has those built into it, you don’t need anything in functions.php.

If you are looking in WP Crontrol the only thing you need to confirm is that you can see these jobs:

AHEE__EE_Messages_Scheduler__sending
AHEE__EE_Messages_Scheduler__generation
AHEE__EE_Messages_Scheduler__cleanup

It should look like this: https://monosnap.com/file/kJgTqpdZSU1W1z8r8IJneJnFz9TPW1

If those are there EE has added the WP_Cron events as expected, thats it.

If they aren’t there, use Event Espresso to do it for you by either de-activating and then re-activating Event Espreso 4, or, run the AHEE__EE_Messages_Scheduler__cleanup job if you have 4.10.8.p+ on the site as that’ll add the jobs back for you.

—-

I’m not sure what you are doing with crons on the server, but you want to do something like this:

https://www.siteground.co.uk/tutorials/wordpress/real-cron-job/

Which in effect does nothing more than call wp-cron.php on a ‘real’ cron every X minutes, rather than WP_CRON doing it on every single request to check if a task needs to fire.

November 17, 2020 at 3:47 am

The only Cron Event I see is:
“AHEE__EE_Cron_Tasks__expired_transaction_check”

and the last one was ran 6 months two weeks ago.

That’s the only EE cron you have listed?
How many of those do you have?

The cron jobs will only be created on activation so if they’ve been altered/removed since then you’ll need to de-activate and re-activate EE to have them recreated.

November 19, 2020 at 7:47 am

That’s a very good indication that you have an issue with WP_CRON on your site.

Every registration added on EE creates that cron to check if the registration has been finalized after the user’s session has expired. If you’ve got many of those just sitting waiting to run then crons aren’t running on your site.

At the top of WP Crontrol does it mention anything about WP_CRON being disabled?

If you look in the sites wp-config.php can you see anything at all to do with CRON?

Earlier you said you added a cron in bluehost, can you add some details on what you actually did there? If you’ve added a cron in bluehost to trigger your sites cron jobs the above crons should already have run.

December 4, 2020 at 8:18 am

Please answer my question above, the next steps depend on what you’ve done to cron.

Regarding AHEE__EE_Cron_Tasks_expired_transaction_check, a new wp_cron task will be scheduled each time there is a registration so if WP_CRON isn’t running then its expected that you would see those and they wont be removed until WP_CRON is functioning again.

December 7, 2020 at 4:30 am

Hey, I’ve just been informed that

AHEE__EE_Messages_Scheduler__sending
AHEE__EE_Messages_Scheduler__generation
AHEE__EE_Messages_Scheduler__cleanup

are present, they were ran manually.

Ok, so were they always there or have they been manually added, and then manually run?

Is there a setting to allow them to run upon the need to run?

The only setting needed is setting ‘Generate and send all messages’ to ‘On separate request’ within Event Espresso -> Messages -> Settings

They are added to the WP Cron schedules and then run with WP_CRON.

If we make changes to the frequency do we need to restart wordpress to see the changes?

Sorry, I don’t understand. Changes to which frequency and how would you restart WordPress?

Is it possible to get someone at EE to login and advise on the settings?

Sure, however, last time we logged in there was an issue with an NDA here. I assume that is still valid here?

We don’t keep login credentials for any longer than necessary so we no longer have the credentials you sent over previously, if you can resend temp credentials using this form:

https://eventespresso.com/send-login-details/

I’ll take a look.

We have been suffering for over a month with this.

I’m sorry your running into this issue, but if you take a look at the timestamps within this thread you’ll see I’ve replied to each of your posts within 24hours, mostly within an hour of your previous reply. So the month long delay in fixing this has not been on our end.

December 8, 2020 at 4:18 am

Hi,

Unfortunately, it looks like the password supplied is invalid, can you recheck and resend, please?

December 8, 2020 at 8:12 am

Hi there,

That’s the credentials I’m using but still getting invalid login.

December 8, 2020 at 8:35 am

No, I’m using Win10 with Chrome.

I sent you a screenshot via email showing you the login page I’m using.

December 17, 2020 at 5:56 pm

Hi there,

My apologies for the delay, I can access the site with the latest credentials.

I had a look at site can see loopback requests are failing on the site, if you look in Tools -> Site Health you’ll see a critical error showing ‘Your site could not complete a loopback request’, which is required for WP_CRON to work.

It could be due to your SSO running and preventing the request from completing or it could be from any number of issues (sessions being opened on each request for example).

First, try adding this to your sites wp-config.php file:

define('ALTERNATE_WP_CRON', true);

That switches WP to use an alternative method for WP_CRON which doesn’t require loopback requests. You need to add the above line somewhere before the line that has:

/* That's all, stop editing! Happy blogging. */

Do messages automatically step through the message queue with the above in place?

You may want to clear out the current AHEE__EE_Cron_Tasks__expired_transaction_check cron tasks before you add the above as you have tasks from over 7months ago that will start running and possibly trigger messages for the registrations they run for (it depends on what status each registration is at).