davdebcom
Forum Replies Created
-
Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] PHP Fatal error: Uncaught TypeErrorHi
this is a conflict with simple-locator plugin that uses an older version of Guzzle. I’m not going to ask you to ask the simple-locator developers to update their version of Guzzle, because next weke we will have an update that contains a workaround for the Guzzle conflict.
So, stay on 3.0.6 for now, and when 4.0.0 stable comes out, you can update to that.
Thanks for reaching out, by the way!
Kind regards
DavidForum: Plugins
In reply to: [Paytium: Mollie payment forms & donations] Blank ResponseHi
You can either use Paytium Plus:
https://www.paytium.nl/handleiding/eigen-tekst-na-betaling/Or use a custom code snippet if you have experience with PHP:
https://www.paytium.nl/handleiding/veelgestelde-vragen/#kan-ik-gebruikers-na-een-betaling-redirectenIf the last option is not working, please share the code you used and explain how you added it to WordPress. If you used a plugin like Code Snippets, are you sure the snippet is activated?
Kind egards
DavidForum: Plugins
In reply to: [Mollie Payments for WooCommerce] Beta?Hi Jos,
Is it against the guidelines? I never found a specific rule against it, feel free to point me to the correct article. Wouldn’t want to not follow the guidelines.
I actually only found an indirect sentence that seems to communicate that versions other then stable are allowed.
https://developer.wordpress.org/plugins/wordpress-org/detailed-plugin-guidelines/#14-frequent-commits-to-a-plugin-should-be-avoidedThe two remaining issues are: some servers don’t have valid cacert.pem files, some sites have conflicts with other plugins that use Guzzle/Composer. Both issues will be fixed. I hope to release the stable this week.
I hope you understand that I choose to be extra careful when releasing a new major version to 40.000 eCommerce websites.
Kind regards
DavidYou mentioned earlier that this issue doesn’t occur anymore, so now it does again? If you haven’t already, please email me on mollie@paytium.nl. I’ll search my inbox and make sue you haven’t already, but feel free to email anyway.
Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] Bitcoin and iDeal not visible in checkoutHi Tim
Yes, let’s look into this.
Do you have any other WooCommerce related plugins installed? Which?
Did you try with a regular test product of 10 euro’s? Does that work?
Care to share the direct link to your test product so I can look?Kind regards
DavidThe second issue I can’t reproduce, I would like to investigate and see if it is specific to your site. Could you email me on mollie@paytium.nl?
Multiple people have reported this, but none let me know what the eventual status is. So maybe you will?
Older topics:
https://wordpress.org/support/topic/not-working-with-plugin-payment-gateway-based-fees-and-discounts-for-woocommerce/
https://wordpress.org/support/topic/extra-charges-per-gateway/#post-10510159My reply from earlier:
This plugin, which we recommend, does work correctly:
https://wordpress.org/plugins/woocommerce-pay-for-payment/It seems the plugin uses some logic to only show fees for some Gateways. I’m not sure what the logic is. But according to the website it shouldn’t add fees to other gateways. I think the best next step is to actually ask the developer of that plugin.
Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] Extra charges per gatewayHi Kees
Any news?
Kind regards
DavidHi Marjons
Any news?
Kind regards
DavidHappy you found out what’s happening. I’ll research this and get back to you.
But if it’s a payment for one year, it’s not a subscription, so why did you create it as a subscription product? Just wondering.
- This reply was modified 7 years, 10 months ago by davdebcom.
Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] SSL certificate problem on localhostYour server is using an old cacert.pem, ask your hoster to update it.
In 3.x we used our own cacert.pem for when this happened, we are probably going to re-add it, it seems there are still enough hosters with old versions around.
Nope, not possible, there is definitely a conflict. Klarna is using a 1 year old version of Guzzle (5.x) and we are using the latest version (6.x). I have already asked them to update, no reply yet:
https://github.com/woocommerce/woocommerce-gateway-klarna/issues/127We had the same with Cardinity, they’ve updated within 24 hours.
Alternative solution for you: use the 3.x versions of our plugin until Klarna is updated.
- This reply was modified 7 years, 10 months ago by davdebcom.
Forum: Plugins
In reply to: [Mollie Payments for WooCommerce] Beta?It’s simple: you don’t feel confident about it, don’t update and wait for the stable.
If there was a security update, it would be mentioned in the changelog off course. And if a security issue was known before releasing the beta’s, I would have added the fix in the previous stable version as a point release.
Oke, please let me know what the outcome is.
This plugin, which we recommend, does work correctly:
https://wordpress.org/plugins/woocommerce-pay-for-payment/It seems the plugin uses some logic to only show fees for some Gateways. I’m not sure what the logic is. But according to the website it shouldn’t add fees to other gateways. I think the best next step is to actually ask the developer of that plugin.