- This topic has 20 replies, 3 voices, and was last updated 6 years ago by
.
-
Posts
-
Since this morning:
After registering for an event, customers are no longer sent to Mollie for the payment. They get the error message “er is een fout opgetreden” in a yellow bar. However, a reservation is made in the system and the notification mail is sent.
So customers think they did not make a reservation and re-submit the form. Some customers do that several times, so much manual labour now to remove double bookings.
Can you please look at this, since the update telss us you did change something to the Mollie-connection. Thanks!
website: ihbv.nl/evenementen
How do you send them to Mollie for paymet? If you do this automatically (via jquery or so), then read the changelog:
* Mollie changes (API update and GET=>POST)Weet ik veel 😉
Ik heb niets veranderd. Sinds vanmorgen doet de plugin niet meer wat hij eerder wel deed.
Moet ik nu zelf iets aanpassen? Waar?Van mijn technische ondersteuner krijg ik dit door:
https://ihbv.nl/evenementen/?eme_eventAction=mollie_notification
Well, then you’ll have to ask your tech-guy for help. Nothing I can do here (no logs, no error messages, no browser console info).
If you want tech-support from me: feel free to mail me in private (but I have to warn you: I don’t work for free either …)Snap ik, we hebben al eerder contact gehad, heb ook gedoneerd aan je. Maar ik stuurde dus eerder al de link naar de melding:
Fatal error: Uncaught Mollie\Api\Exceptions\ApiException: Invalid payment ID: ”. A payment ID should start with ‘tr_’. in /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/payment_gateways/Mollie/2.1.3/src/Endpoints/PaymentEndpoint.php:62 Stack trace: #0 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/eme_payments.php(1295): Mollie\Api\Endpoints\PaymentEndpoint->get(NULL) #1 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/eme_actions.php(126): eme_mollie_notification() #2 /srv/users/ihbv/apps/ihbv/public/wp-includes/class-wp-hook.php(286): eme_actions_init(”) #3 /srv/users/ihbv/apps/ihbv/public/wp-includes/class-wp-hook.php(310): WP_Hook->apply_filters(NULL, Array) #4 /srv/users/ihbv/apps/ihbv/public/wp-includes/plugin.php(453): WP_Hook->do_action(Array) #5 /srv/users/ihbv/apps/ihbv/public/wp-settings.php(450): do_action(‘init’) #6 /srv/users/ihbv/apps/ihbv/public/wp-config.php(37): require_once(‘/srv/users/ihbv…’) #7 /srv/users/ihbv/apps/ihbv/public/wp-load in /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/payment_gateways/Mollie/2.1.3/src/Endpoints/PaymentEndpoint.php on line 62
That was not in the info of your posts above. Let me check this, this might be related to the new api.
I just tried (signup to Mollie and requested a new API test key) and everything seems to work just fine.
Check your mollie API keys to make sure your keys are correct.
Btw: your error seems to be when mollie calls back to report the payment status, and that only works with a live API key. People shouldn’t see this error though.
Nothing in your error report points to an error with redirection to Mollie though.mollie key just fine; working with the live key, not the test key
nothing changed on my side, something did in your plugin….Your topic title is “customer not directed to Mollie after recent plugin-update” and now you’re saying it works ok with the live API key? Then I don’t see any issue.
So please redirect your questions concerning test api key and payment notification to Mollie, I’m not in control of their code (I just use it in the way they describe it). If they decide to not give out correct notifications for a test key, that’s not something I can change. Feel free to post any answer they may provide here.there is no problem with the test-api. I am working with the live api.
I have checked the keys as you suggested and the correct one is mentioned in de “Instellingen”This is our situation:
when a customer has filled in the booking form, and submits it, he is not directed to mollie, but an error code is displayed.In the backend however, a reservation has been made en the e-mail to conform this, is sent to the customer.
But the customer doesn’t know this untill he checks his e-mail.
In our confirmation-mail we also give the customer the link for direct payment (= link to Mollie) and that works just fine. It is just that the “pay now” button on the bookingform gives an error message.
This is the case since yesterday morning. Before that everything was working fine.
I hope I have explained this correctly now
the sentence”there is no problem with the test-api” might be confusing. What I mean is that our problem happens while working with the live-api, which is correctly mentioned in Instellingen.
Ok, I made a test booking (please do delete it so it doesn’t take up valid places).
The problem you’re seeing doesn’t seem to have anything to do with Mollie itself, nor the redirection to it. There seems to be an error in the backend when returning the ‘booking success” message.
This might be related to another bug that was just reported today and for which I released a new version, see: https://wordpress.org/support/topic/database-error-271/
If your success-message somehow contained the number of approved seats, that might have been the reason. What is the format of the success message?
Also, to make it easy: you can first update to 2.0.61 and see if that fixes the problem, then we know we were talking about the same issue.we have updated de plugin, tested and unfortunately it did not fix the problem. This is the errorlog:
[30-Oct-2018 17:07:07 UTC] PHP Fatal error: Uncaught Error: Call to undefined function _PhpScoper5bc8350a1bb6a\GuzzleHttp\choose_handler() in /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/payment_gateways/Mollie/2.1.3/vendor/guzzlehttp/guzzle/src/HandlerStack.php:37
Stack trace:
#0 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/payment_gateways/Mollie/2.1.3/vendor/guzzlehttp/guzzle/src/Client.php(64): _PhpScoper5bc8350a1bb6a\GuzzleHttp\HandlerStack::create()
#1 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/payment_gateways/Mollie/2.1.3/src/MollieApiClient.php(204): _PhpScoper5bc8350a1bb6a\GuzzleHttp\Client->__construct(Array)
#2 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/eme_payments.php(786): Mollie\Api\MollieApiClient->__construct()
#3 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/eme_payments.php(63): eme_mollie_form(Array, Array, 17.5, ‘EUR’, ”, 0)
#4 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/eme_rsvp.php( in /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/payment_gateways/Mollie/2.1.3/vendor/guzzlehttp/guzzle/src/HandlerStack.php on line 37This is something else … this is internal Mollie code failing. Since it works for me locally and my provider: can it be you’re using an old php version? What is your php version?
The server is on PHP 7.1. I ran the site on 7.0 (just now) which gives the same error.
(7.0 error:
PHP Fatal error: Uncaught Error: Call to undefined function _PhpScoper5bc8350a1bb6a\GuzzleHttp\choose_handler() in /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/payment_gateways/Mollie/2.1.3/vendor/guzzlehttp/guzzle/src/HandlerStack.php:37
Stack trace:
#0 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/payment_gateways/Mollie/2.1.3/vendor/guzzlehttp/guzzle/src/Client.php(64): _PhpScoper5bc8350a1bb6a\GuzzleHttp\HandlerStack::create()
#1 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/payment_gateways/Mollie/2.1.3/src/MollieApiClient.php(204): _PhpScoper5bc8350a1bb6a\GuzzleHttp\Client->__construct(Array)
#2 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/eme_payments.php(786): Mollie\Api\MollieApiClient->__construct()
#3 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/eme_payments.php(63): eme_mollie_form(Array, Array, 17.5, ‘EUR’, ”, 0)
#4 /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/eme_rsvp.php( in /srv/users/ihbv/apps/ihbv/public/wp-content/plugins/events-made-easy/payment_gateways/Mollie/2.1.3/vendor/guzzlehttp/guzzle/src/HandlerStack.php on line 37Apparently the error is because of other plugins also using guzzler (part of mollie api), but probably older version. See https://github.com/mollie/WooCommerce/wiki/Composer-Guzzle-conflicts
My best guess for now: check all your plugins, disable all and reactivate one by one until you find the conflicting one. But again: it is a mollie api issue, not EME specific.
If you find the plugin causing conflict: you can report it to mollie on https://github.com/mollie (or your mollie tech contact).
Also make sure all your plugins are up-to-date and still maintained … if one uses also the guzzler library (like mollie does), then this will cause the problem.I want to jump in on this issue. I get the same problem but none of the plugins which I have are the issue. I turned on debugging in wordpress and the log showed me this:
[12-Nov-2018 17:15:08 UTC] PHP Parse error: syntax error, unexpected ‘.’ in /home/cforcdx156/domains/aanmeldenvelodrome.nl/public_html/wp-content/plugins/events-made-easy/payment_gateways/Mollie/2.1.3/vendor/autoload.php on line 11
Can you verify your code???
The Mollie code is not mine, but provided by Mollie. If you have a syntax error, your php version is too old.
Correct. Hosting was on php version 5.5 and required was 5.6.
- The forum ‘Generic’ is closed to new topics and replies.