Support

April 27, 2016 at 9:42 am

Hi Rob,

I didn’t see the Stripe payment gateway for Event Espresso 4 on your account. Are the payments being processed through another ecommerce plugin (e.g. Woocommerce)?

If so that won’t work as Event Espresso has its own payment gateways.

The other idea that I had is you may have had support for Stripe in the past but no longer do. If that is the case, then you would have a combination of current and old software which could cause the issue that you are experiencing.

—
Lorenzo

April 27, 2016 at 12:33 pm

Alright, thanks for clarifying.

Could you go to the transaction in WP-admin (WP dashboard) –> Event Espresso –> Transactions? Then click on the specific transaction and then scroll down and look at the payment details area.

Could you capture a screenshot of what you see in the payment details area?

Here is what I’m referring to: http://cl.ly/1V3w2s341E46

And here is how to share a screenshot with us:

https://eventespresso.com/wiki/troubleshooting-checklist/#screenshots

—
Lorenzo

April 28, 2016 at 5:45 am

Thanks. Could you please setup no-cache rules for your Event Espresso pages?

The page source shows that W3 total cache is running but the Event Espresso pages are not excluded. Here is how to do that:

https://eventespresso.com/wiki/setup-nocache-exclusion-rules-event-espresso/

And I had a follow up question on your earlier feedback here:

I just ran a successful event last week. I’m using Mijireh with Stripe. The test payment I ran this morning. The payment showed up in Stripe. This is a brand new account.

Was the event from last week also via Stripe through Mijireh?

—
Lorenzo

April 28, 2016 at 11:28 am

Hi Rob,

Are you seeing it under the performance option in your WP dashboard? Here is a screenshot of the area from your original screenshot:

http://cl.ly/1p2X3k221y0b

Could you create a test event with a low value and re-test to ensure that the caching isn’t affect the page?

Here are the steps:

1) Create an event called test with a description of test. Note that the words test isn’t required, rather its just so you know that this is a test event.

2) Set the ticket price to a low value like a dollar or 50 cents and publish

3) Copy the URL (link) for the new event and then open a different web browser other than the one that you are currently logged into your site with.

For example, if you are using Firefox, then try Chrome, Opera, or Safari. This will simulate a registrant/attendee as they will be a public visitor. Then go to the link in the other web browser and try a registration.

Do things then work as expected (e.g. payment processed and registration approved with an email notification)?

—
Lorenzo

April 28, 2016 at 5:56 pm

Thanks for letting us know. It sounds like the no-cache rules are running.

Please be sure to set the test event to draft or delete it so it isn’t available for registration by your registrants/attendees.

—
Lorenzo