|
ICLE
|
July 19, 2021 at 9:55 am
We are getting this error on our export of data:
{“code”:”invalid_format_for_timestamp”,”message”:”Timestamps received on a request as the value for Date and Time fields must be in RFC3339\/ISO8601 format. The timestamp provided (]=2021-07-16T12:21:38) is not that format.”,”data”:{“status”:400}}
Was there a change to the date format in a recent EE update? Is there a patch?
|
|
Tony
|
July 19, 2021 at 10:44 am
Hi there,
Was there a change to the date format in a recent EE update?
Not that I’m aware of, where do you see this error message?
|
|
ICLE
|
July 19, 2021 at 11:08 am
This reply has been marked as private.
|
|
ICLE
|
July 19, 2021 at 11:11 am
This reply has been marked as private.
|
|
ICLE
|
July 19, 2021 at 1:54 pm
This reply has been marked as private.
|
|
Tony
|
July 19, 2021 at 2:48 pm
When did you switch to using the alternative WP_CRON version on the site?
The above link you included works fine unless you are redirected to check for WP_CRON requests.
I’ll post a private reply with the specific URLS.
|
|
Tony
|
July 19, 2021 at 2:50 pm
This reply has been marked as private.
|
|
ICLE
|
July 19, 2021 at 3:41 pm
Hi Tony,
This is Dave under Michaels account. It sounds like what you are saying is that if we stop that WP_Cron redirect then the problem may resolve itself?
Regarding the switch to the WP_Cron redirect, I will see if I can get in the dashboard and see how that is set up. Michael might know something about it.
Thank you for your help.
|
|
Tony
|
July 19, 2021 at 3:47 pm
This is Dave under Michaels account. It sounds like what you are saying is that if we stop that WP_Cron redirect then the problem may resolve itself?
Correct, the redirect for the alt WP_CRON system is causing this as far as I can tell.
Regarding the switch to the WP_Cron redirect, I will see if I can get in the dashboard and see how that is set up. Michael might know something about it.
That will be set up within the sites wp-config.php file using something like:
define('ALTERNATE_WP_CRON', true);
Which switches the site from the ‘standard’ wp_cron setting to the redirect you are seeing above.
|
|
ICLE
|
July 21, 2021 at 12:53 pm
This is Michael again.
The messages do not send when the alt cron is disabled.
Do you have any suggestions?
|
|
Tony
|
July 22, 2021 at 12:11 pm
I remember this from a little while ago now.
Personally, I’d troubleshoot why loopback requests aren’t working on your site/server. The messages aren’t sending because they rely on WP_CRON to function, the ‘standard’ method for WP_CRON (loopback requests, essentially the site making a request to itself) don’t work on your site so you switch to ALTERNATE_WP_CRON).
With the report you are generating above using the REST API, is that generated on the site same as EE is installed or another?
|
|
ICLE
|
July 22, 2021 at 12:38 pm
The request is coming in from another. It is the request we have in this thread which was private due to I don’t want my site to get hacked.
So in order to suss this out, I should open a ticket with the host?
|
|
Tony
|
July 22, 2021 at 4:04 pm
The request is coming in from another. It is the request we have in this thread which was private due to I don’t want my site to get hacked.
I’m not sure I follow. I’ll explain why I’m asking and if it doesn’t apply then no worries.
We often have users using the REST API to generate various ‘reports’ or features on the same site that is running Event Espresso. If you’re running it on the same site then you are better using our model system to get all the data you need, but you can’t use that if you are using the data on another site from where EE is installed.
So if you are on the same site, use the model system.
If you are pulling the data from Site A into Site B, use the REST API.
So in order to suss this out, I should open a ticket with the host?
Loopback requests failing can happen for many reasons, the first thing I would do is contact my host and confirm they allow for WP loopback requests so that WP_CRON can function. If they do not, ask what not and if they can add an exception to whatever is blocking it for your site.
If they say all is working on their end you’ll need to start troubleshooting the site itself, it could be another plugin causing a conflict on those requests, or the theme. Theres multiple possible casues.
|
