webaware

G’day Stefan,

Did you resolve this? Did it happen with a plain login, or when you tried logging in specifically on this plugin’s setting page URL?

cheers,
Ross

G’day @thebateser,

You’ll find the start of the code here:

https://github.com/webaware/ssl-insecure-content-fixer/blob/master/includes/class.SSLInsecureContentFixer.php?ts=4#L73-L76

The Capture modes start page buffering on the init action, and run the content changes at the end of the page when buffering ends, as show here:

https://github.com/webaware/ssl-insecure-content-fixer/blob/master/includes/class.SSLInsecureContentFixer.php?ts=4#L295-L309

Content fixing is a bunch of regular expression search/replacements. They’re the same for Content, Widget, Capture so that should not be your problem — but you can see them here:

https://github.com/webaware/ssl-insecure-content-fixer/blob/master/includes/class.SSLInsecureContentFixer.php?ts=4#L227-L250

I tested Leaflet MapsMarker and did not strike a problem. I suggest that you look at other plugin differences, especially anything that buffers the whole page (like cache plugins, plugins that redirect pages based on content/forms, etc.)

cheers,
Ross

G’day,

It sounds like you have needed to set HTTPS Detection to something other than the default (standard WordPress function). That means you need to have some means of telling WordPress when you’re loading the site from HTTPS.

https://ssl.webaware.net.au/https-detection/

If you’re a little handy with PHP, you can make the fix permanent so that you can deactivate the plugin, as described here:

https://ssl.webaware.net.au/https-detection/permanent/

cheers,
Ross

G’day Dave,

If you prefer to use the custom credit card fields, not the WooCommerce standard fields, please load this version of the plugin:

https://www.dropbox.com/s/t96jeevrb50of2b/eway-payment-gateway-4.0.2-dev.zip?dl=1

Thanks again for helping me find the bug!

cheers,
Ross

G’day @morgo75,

That error exactly means that:

• you’ve entered your Rapid API key/password and the Rapid API is being used
• your eWAY account requires Client Side Encryption
• the transaction is being sent without Client Side Encryption

You said you have entered your client side encryption key, so something else is messing things up. I looked at the WooCommerce checkout page and the usual stuff for client side encryption just isn’t there, so either you’ve removed the API key/password to get things working again, or something is stopping the scripts for client side encryption from being added to the page.

Are you able to try changing the theme to twentysixteen or something similarly vanilla? That will help test whether it’s your theme doing something weird.

Another possibility is that Cloudflare’s Rocketscript is messing things up. That thing can do weird things with JavaScript. I don’t think that’s the problem because my eWAY client side encryption scripts aren’t even showing up in the page source, but it’s still a possibility. If the theme switch doesn’t fix things, try turning off Rocketscript and see if that helps. And let me know!

cheers,
Ross

G’day @rmt3030,

There’s a number of options available for eWAY payments customer-entered amounts.

Using WooCommerce, you can add a plugin for a Donation product type. There’s a bunch, including a couple of free ones:

http://duckduckgo.com/?q=woocommerce+donations+plugin+!g

If you want to accept customer-entered payments without a cart, I’d recommend looking at Gravity Forms. There’s a free and a pro eWAY integration:

https://en-au.wordpress.org/plugins/gravityforms-eway/
https://gfeway.webaware.net.au/

For an even simpler solution, you can use a Pay Now Button. This is very simple, and not for everyone, but it might suit you:

https://pay-now-button.webaware.net.au/faq/can-customers-change-the-amount/
https://play.webaware.net.au/pay-now-button-for-eway/

cheers,
Ross

G’day joemillie,

That page actually links to your Gravity Forms page, which is working OK… almost stopped there, but saw the link to the Online Store 🙂

So, it looks like your theme is breaking something in the checkout so that Client Side Encryption isn’t running. I can see the CSE config in there, it’s just not running when the customer clicks on Place Order.

Are you able to send me a .zip of the theme so that I can test with it? I have an idea about what might be causing the problem, but need to test against a copy of the theme. You can send to this email address: support(at)webaware.com.au

In the meantime, you can get your online shop working again by removing the Rapid API password from your WooCommerce eWAY settings, and it will use the legacy API with your customer ID (so make sure your customer ID is set!)

cheers,
Ross

Version 4.0 released, with Rapid API support and open to all eWAY-supported currencies.