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
Beanstream | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Beanstream

Beanstream

Posted: December 7, 2012 at 10:50 am

Viewing 3 reply threads


Noah Purves-Smith

December 7, 2012 at 10:50 am

Just launched our main site. We were testing on another domain, and everything was working perfectly. When we did a simple transfer to our actual domain, the Beanstream gateway in Event Espresso stopped working. It gives the following error:

%3CLI%3EInvalid+expiration+month%3Cbr%3E

We’ve been testing quite a bit, and didn’t get this problem on our test domain. Any thoughts where this could be going wrong?


Josh

December 7, 2012 at 4:56 pm

Hi Noah,

How was the site transferred?


Noah Purves-Smith

December 10, 2012 at 10:02 am

Hi Noah:

We copied the files over to the FTP.

We also did a search and replace for the domain name on the SQL and imported that too.


Noah Purves-Smith

December 10, 2012 at 12:17 pm

I was contacted by someone at Beanstream with the solution:

The expiry date needs to have a leading zero. I have updated the beanstream\payment.php file on line 145:

<?php
for ($i = 1; $i < 13; $i++)
echo "".sprintf("%02d", $i)."";
?>

It seems to be working now. Not sure why it was working on our test domain.
Viewing 3 reply threads

The support post ‘Beanstream’ 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 Noah Purves-Smith 12 years, 1 month ago ago

Topic Tags

Tagged: 

Notifications

This topic is: resolved
Event Espresso - Staging Server