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
Incomplete Payment Status on Attendee Admin Area Only | Event Espresso - Staging Server

Support

Home Forums Event Espresso Premium Incomplete Payment Status on Attendee Admin Area Only

Incomplete Payment Status on Attendee Admin Area Only

Posted: September 18, 2012 at 11:42 am

Viewing 15 reply threads


ann hagan

September 18, 2012 at 11:42 am

I tested out the entire registration/payment process (using PayPal Pro) and everything worked fine; the Thank You page had no errors and Payment Status is Completed, and both of the emails (including the Ticket itself) show my $10.00 purchase.

However, when I checked the Attendees area in the EE admin, it shows my payment as incomplete. The money was drawn from my bank account, but the payment status is written on the wp_events_attendee table as incomplete. Also, there were no errors in the error log. We just purchased and downloaded the premium EE package on last Monday, and set up the virtual server with WP last Sunday, so we must be on the latest versions of both.

Please HELP! The client needs the registration working ASAP. And thank you in advance.

  • This topic was modified 12 years, 3 months ago by Josh. Reason: moving to Event Espresso forum


ann hagan

September 18, 2012 at 12:38 pm

Also, the event registration pages are being displayed as page ids, rather than permalinks. (The rest of the pages in the site are all using permalinks.) So I have the PayPal IPN url set to: https://ourcompany.com/?page_id=276 (which is the page id for the transactions page).

Do I need to add any plugins for the https?


Eric Martin

September 18, 2012 at 4:30 pm

I’m having the same issue… PayPal Pro working great, admin area is just not updating properly. I’ve read all of the IPN threads on this issue I could find, haven’t been able to find a fix yet… help!


ann hagan

September 18, 2012 at 5:52 pm

I REALLY need help with this issue tonight!!! The URL of the transaction page is https://go2bat4life.com/transactions/


Dean

  • Support Staff

September 19, 2012 at 6:39 am

Hello Ann,

Regarding the permalinks, Event Espresso does use none “pretty” permalinks i.e. https://go2bat4life.com/event-registration/?ee=1 as standard, it shouldnt affect the workings of the plugin or site.

Is it possible to get your login details in order to look into this?

If so, please send them via http://staging.eventespresso.com/contact/

Choose the “I am sending login info as requested” option and fill out the form


ann hagan

September 19, 2012 at 8:03 am

Thanks, I just uploaded the login details and more information on the problem. Really need this working this morning. Also, I purchased premium support last night.

Wes (for Ann)


Eric Martin

September 23, 2012 at 12:37 pm

Was there any helpful info to come out of this? I am still experiencing this same issue…


Dean

  • Support Staff

September 24, 2012 at 12:56 am

Hi Eric,

There was no error from Event Espressos, it seemed to be either a File/folder permissions issue on the server or an issue at Paypals end (both were amended at the same time so its difficult to say which resolved it).

I would check permissions first (give it some time after you do this to allow any changes to take effect) and if not have a quick word with Paypal about the IPN. If neither resolve the issue, let us know and we can have a look at your site (will need login details)


Eric Martin

September 24, 2012 at 7:51 am

Thanks Dean – slowly closing in on the problem! Do you happen to know specifics of file/folder permissions (what changes were made)?


Dean

  • Support Staff

September 24, 2012 at 10:46 pm

Hi Eric.

One of the folders had the wrong permissions 757, and was changed to standard WordPress ones – you can see details of these here but basically its either 755 or 750 for folders.


Dean

  • Support Staff

September 28, 2012 at 2:21 am

Hi Eric,

Just following this up. Have you got it sorted now?


Eric Martin

September 28, 2012 at 8:41 am

Hi Dean,

No not yet unfortunately. I wasn’t sure which folder you were referring to specifically, so I did a general sweep of my folders and they all seem to be standard WordPress 755 or 750. I’ve also triple-checked that PayPal Pro IPN is going to https://bailiwickchicago.com/transactions, and I’m using the minimal transactions page (I can access the page just fine when logged-out). Can someone look into this further if I send login details? Do I need to purchase premium support for that?


Dean

  • Support Staff

September 28, 2012 at 10:56 am

Hi Eric,

Can you email me the log file? It should be at uploads/espresso /logs/espresso_log.txt

You can send it to support@eventespresso.com


Sidney Harrell

  • Support Staff

September 28, 2012 at 1:23 pm

I think I can see what is going on. When I send a POST to the transactions page:

https://bailiwickchicago.com/?page_id=4742&id=235&r_id=37-5065f477e178f&event_id=37&attendee_action=post_payment&form_action=payment&type=paypal

POST /?page_id=4742&id=235&r_id=37-5065f477e178f&event_id=37&attendee_action=post_payment&form_action=payment&type=paypal HTTP/1.1
Host: bailiwickchicago.com
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20100101 Firefox/15.0.1
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip, deflate
Connection: keep-alive
Content-Type: text/xml; charset=UTF-8
Content-Length: 13
Cookie: PHPSESSID=8ed7c9b42295fcbdae6a6a266856ce98
Pragma: no-cache
Cache-Control: no-cache
hello=goodbye

It is getting a 301 redirect to

Location: https://bailiwickchicago.com/transactions/?id=235&r_id=37-5065f477e178f&event_id=37&attendee_action=post_payment&form_action=payment&type=paypal

When it requests that page, the POST data that I sent, hello=goodbye, is gone:

https://bailiwickchicago.com/transactions/?id=235&r_id=37-5065f477e178f&event_id=37&attendee_action=post_payment&form_action=payment&type=paypal

GET /transactions/?id=235&r_id=37-5065f477e178f&event_id=37&attendee_action=post_payment&form_action=payment&type=paypal HTTP/1.1 Host: bailiwickchicago.com User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:15.0) Gecko/20100101 Firefox/15.0.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,/;q=0.8 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip, deflate Connection: keep-alive Content-Type: text/xml Cookie: PHPSESSID=8ed7c9b42295fcbdae6a6a266856ce98 Pragma: no-cache Cache-Control: no-cache

What we can do is just hard-code in the /transactions/ into the notify url if you can send in ftp credentials


Eric Martin

September 28, 2012 at 1:35 pm

AWESOME. Just emailed temp ftp creds to support@. Thank you guys so much for the support!


Sidney Harrell

  • Support Staff

October 3, 2012 at 9:09 am

Hey Eric,
Just ran a test on the modified paypal gateway, and it looks like it worked. The payment was marked as “Completed”. Were you having and problems with the paypal pro gateway, or was that the only problem?

Viewing 15 reply threads

The support post ‘Incomplete Payment Status on Attendee Admin Area Only’ 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.

Event Espresso - Staging Server