Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-sales domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the better-click-to-tweet domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-amazon domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the pue-stats domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/staging-poc/public_html/wp-includes/functions.php on line 6114
Timestamp too long? | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Timestamp too long?

Timestamp too long?

Posted: November 20, 2012 at 9:54 am

Viewing 4 reply threads


bcrinion

November 20, 2012 at 9:54 am

I’m getting the following error when EE tries to link to the external payment gateway.

Error 508
Invalid timestamp: { Too many characters }

Can anybody point in the direction of how to find or modify the timestamp?

Brian.


bcrinion

November 20, 2012 at 10:12 am

I should have noted that it worked fine on http://www.irishtriathlon.com with EE 3.1.25.P

Now on http://www.irishtriathlon.com/entry with EE 3.1.28.4.P there seems to be issues.


Josh

November 20, 2012 at 6:09 pm

Hi Brian,

Is this for the Realex gateway? Which version are you currently on? We haven’t seen this on other installs that use this gateway, but I can take a look.


Sidney Harrell

  • Support Staff

    •

November 21, 2012 at 11:35 am

Hey Brian,

I found the problem. It’s line 24 of Realauth.php in gateways/realauth. It should be:

$this->timestamp = date("YmdHis");

It’s fixed in the next version, and if you want to send ftp info, we can fix it in the current version on your server.


bcrinion

November 21, 2012 at 12:20 pm

Sidney,

That works now.

Brian.
Viewing 4 reply threads

The support post ‘Timestamp too long?’ is closed to new replies.

Have a question about this support post? Create a new support post in our support forums and include a link to this existing support post so we can help you.

The original Forum description...

Status: closed

Updated by bcrinion 12 years, 3 months ago ago

Topic Tags

Notifications

This topic is: resolved
Event Espresso - Staging Server