|
spaselca
|
August 13, 2018 at 3:37 pm
I have setup VANCO payment gateway plugin. I have checked that the credentials are entered correctly with no extra spaces. I can get through all the forms fine with no errors, but once I hit submit it will spin for a brief period then I get a
POST http://www.********.org/wp-admin/admin-ajax.php 500 (Internal Server Error)
If you could provide any help that would be great.
FYI – Paypal express works just fine.
Here is the full error stack
send @ jquery.js?ver=1.12.4:4
ajax @ jquery.js?ver=1.12.4:4
process_and_submit_payment @ eea_vanco_payment_me….js?ver=1.0.6.p:305
(anonymous) @ eea_vanco_payment_me….js?ver=1.0.6.p:231
dispatch @ jquery.js?ver=1.12.4:3
r.handle @ jquery.js?ver=1.12.4:3
trigger @ jquery.js?ver=1.12.4:3
a.event.trigger @ jquery-migrate.min.js?ver=1.4.1:2
(anonymous) @ jquery.js?ver=1.12.4:3
each @ jquery.js?ver=1.12.4:2
each @ jquery.js?ver=1.12.4:2
trigger @ jquery.js?ver=1.12.4:3
(anonymous) @ single_page_checkout.js?ver=4.9.65.p:422
dispatch @ jquery.js?ver=1.12.4:3
r.handle @ jquery.js?ver=1.12.4:3
Thanks!
|
|
Tony
|
August 13, 2018 at 4:09 pm
Hi there,
The most likely cause for the error you are getting is the mcrypt module is not enabled on your server, so when the Vanco payment method attempts to use the functions from that module it throws an error.
The fix is to enable that module on your server, however, we wil be releasing an update to the Vanco payment method that uses a different module to both avoid this error and update add-on to use a newer module.
I can send you a copy of that version of the Vanco payment method to test if you prefer?
|
|
Tony
|
August 13, 2018 at 4:14 pm
To actually confirm the error you are getting you’ll need to check the servers error logs, error 500 means it’s a server side error so there should be a log entry with whatever the problem is.
Generally your host will provide a section in your control panel to viw any errors on the page, or you can add the code here:
https://eventespresso.com/wiki/troubleshooting-checklist/#wpdebug
To your wp-config.php file and retest the Vanco payment, the error should then be logged to /wp-content/debug.log
|
|
spaselca
|
August 14, 2018 at 10:15 am
Thanks for the quick reply!
sorry for my slow reply!
Here is the entry from the debug.log, for providing how to do this as well,
[14-Aug-2018 16:18:17 UTC] PHP Fatal error: Uncaught exception ‘EE_Error’ with message ‘'' is not a model name. A model name must be provide$
Stack trace:
#0 /home1/spaselca/public_html/wp-content/plugins/event-espresso-core-reg/core/libraries/payment_methods/EE_Gateway.lib.php(345): EEM_Change_Log->gatew$
#1 /home1/spaselca/public_html/wp-content/plugins/eea-vanco-payment-method/payment_methods/Vanco_Onsite/EE_PMT_Vanco_Onsite.pm.php(277): EE_Gateway->lo$
#2 /home1/spaselca/public_html/wp-content/plugins/eea-vanco-payment-method/payment_methods/Vanco_Onsite/EE_PMT_Vanco_Onsite.pm.php(231): EE_PMT_Vanco_O$
#3 [internal function]: EE_PMT_Vanco_Onsite::ajax_encrypt_nvpvar(”)
#4 /home1/spaselca/public_html/wp-includes/class-wp-hook.php(286): call_user_func_array(Array, Array)
#5 /ho in /home1/spaselca/public_html/wp-content/plugins/event-espresso-core-reg/core/db_models/EEM_Change_Log.model.php on line 172
|
|
spaselca
|
August 15, 2018 at 8:43 am
The first line is actually
PHP Fatal error: Uncaught exception ‘EE_Error’ with message ''' is not a model name.
And I do have mcrpyt installed on the server
Thanks for the assistance
|
|
Tony
|
August 15, 2018 at 9:55 am
Hmm, yeah that looks like a different error than I was expecting.
However, I’ve pushed the update to the Vanco PM live so I recommend you update anyway.
It looks like you are not getting a session_id back from Vanco during the login request, can I take a look in the admin? I’d like to take a look over the payment logs, if so you can send login credentials using this form:
https://eventespresso.com/send-login-details/
|
|
spaselca
|
August 15, 2018 at 12:55 pm
I update the plugin and tried again and still getting the same error.
I am submitting login information now
|
|
Tony
|
August 15, 2018 at 1:26 pm
Hi there,
Did you submit the form?
I’m just checking as we’ve not had anything through as of yet.
|
|
spaselca
|
August 15, 2018 at 1:58 pm
Yep sent it in
Thanks for sending your information! We will get in touch with you shortly. Be sure to watch your support topic url for updates: https://eventespresso.com/topic/post-500-internal-server-error/#post-275786
|
|
Tony
|
August 16, 2018 at 3:39 am
Took a little for them to come through but I found them, thank you.
Unfortunately, the logs don’t provide any useful information in this case so I’ll need to add some code to the site to view what is happening, to do that I’ll need FTP credentials.
Can you resubmit the form providing all requested details?
I’ve seen something similar to this before with Vanco and it turned out the server didn’t support SNI with its setup, I can’t say if that’s the case here just yet but it might be worth opening a ticket with your host and have them confirm that your server is set up to support SNI (your site uses Nginx which does not have SNI enabled by default).
|
|
spaselca
|
August 16, 2018 at 8:07 am
Hi Tony!
Thanks for all your help
I re submitted the credentials with an FTP account
I will reach out to our provider and ask about SNI
|
|
spaselca
|
August 16, 2018 at 8:11 am
I just realized I may have added a 4 at the end of the login in name. Please disregard that. Sorry
|
|
spaselca
|
August 16, 2018 at 8:24 am
Just talked to our server host. They have SNI enabled on our server
|
|
Tony
|
August 16, 2018 at 10:29 am
Can you recheck those credentials please, I’m getting access denied both with and without the extra ‘4’ on the username.
Just talked to our server host. They have SNI enabled on our server
Ok, thank you for checking.
|
|
spaselca
|
August 16, 2018 at 2:01 pm
Just sent over new credentials
|
|
Tony
|
August 16, 2018 at 4:44 pm
Thanks, those worked.
This isn’t a problem with your setup, its something we’ll need to fix within core for certain situations.
I’ve applied a simple patch to the version of EE you are using on your site and created a ticket for our developers to investigate this further, a fix to prevent this will likely be included in the next version of EE so whilst we don’t recommend editing core files, it wont matter in this case.
|
|
spaselca
|
August 17, 2018 at 8:57 am
Sounds good. Thank you so much for figuring this out!
|
|
Tony
|
August 24, 2018 at 4:53 am
Hi there,
I just wanted to let you know the latest version of Event Espresso (currently 4.9.67.p) has a fix applied for this so you can update when ready, if you do run into any problems just let me know.
|
