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
Paypal IPN error. "An error occurred. No ID or an invalid ID was supplied." | Event Espresso - Staging Server

Support

Home › Forums › Event Espresso Premium › Paypal IPN error. "An error occurred. No ID or an invalid ID was supplied."

Paypal IPN error. "An error occurred. No ID or an invalid ID was supplied."

Posted: July 16, 2013 at 2:20 pm

Viewing 1 reply thread


Meg Benedicte

July 16, 2013 at 2:20 pm

The transaction URL is setup on this page http://newearthcentral.com/transactions/ and it has the following shortcode [ESPRESSO_TXN_PAGE]

When I go to the above page I get this message.
“An error occurred. No ID or an invalid ID was supplied.”

Would the IPN work properly?


Josh

July 16, 2013 at 2:50 pm

Hi Meg,

That’s actually expected if you visit the /transactions/ page in the web browser and indicates that the page and shortcode are correctly set up.

There are other things that can affect whether the PayPal IPN works properly and we’ve put together a list on how to make sure it works here:

http://staging.eventespresso.com/wiki/how-to-set-up-paypal-ipn/
Viewing 1 reply thread

The support post ‘Paypal IPN error. "An error occurred. No ID or an invalid ID was supplied."’ 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 Josh 11 years, 6 months ago ago

Topic Tags

Tagged: 

Notifications

This topic is: not resolved
Event Espresso - Staging Server