webaware

G’day baursnes,

First things first, your websites doesn’t have a valid TLS certificate. That’s might be why the unknown error, as well. Mozilla says it’s a self-signed certificate.

Beyond that, I recommend checking the website error log. You can find your website error log through your hosting control panel, usually under a button called Logs. If you’re not sure where to find it, you can tell WordPress to write errors to the file wp-content/debug.log by editing your wp-config.php file. Find the line that says:

define('WP_DEBUG', false);

And replace it with this:

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);

NB: you should change it back when you’re finished, because debug mode slows your website down a bit!

cheers,
Ross

Duplicate, answered in other ticket.

cheers,
Ross

G’day ytian03,

Simply because it wasn’t available in WooCommerce when I initially wrote the integration in 2013. I’ve added the WooCommerce transaction ID now in version 5.3.0, so please update.

cheers,
Ross

The problem is that this plugin doesn’t currently support the new WooCommerce checkout block, only the old shortcode. I was hoping to add that support this week but every day brings more tasks that are urgent, so the earliest I’ll be able to do that is sometime next week. I’ll update this ticket once that has been done.

cheers,
Ross

G’day @jasonm530,

Have you enabled the payment method? You can do that either in the list of payment methods, or on the settings page for Eway payments.

If you have, have you enabled Sandbox mode? It won’t be available for payments if you haven’t set the live API details and Sandbox mode is not enabled.

cheers,
Ross

When you add or edit a Notification, you can choose what event to send the notification on. The default event is “Form is submitted”, but for transactions you should choose “Payment Completed” for successful transactions, “Payment Failed” for unsuccessful transactions.

https://gf-windcave.webaware.net.au/faq/notifications-success-fail/

G’day sccwjd,

I’ve run a couple of tests and the merge tags seem to be working OK.

Are you sure that there was a successful transaction? You will get that when the transaction failed or was cancelled. To only receive a notification on successful transactions, change the Event to Payment Completed on the notification. You can have a separate notification for failed transactions.

cheers,
Ross

Resolved, please update to version 5.2.1. Thanks again for your bug report.

cheers,
Ross

G’day @tatsaman,

I’ve obtained an updated copy of EE Pro, and can reproduce the problem. Will get a fix out soon. Thanks for your bug report.

cheers,
Ross

G’day bcrosgrove,

It’s on my list to do, but there’s a few important things in ahead of it. Can’t commit to when it might happen.

cheers,
Ross

Now released as v2.5.0; no change required for Pro version.

G’day sccwjd,

Thanks for letting me know. I’ll get new releases out today.

FWIW, it looks like they’ve reinstated sec.paymentexpress.com for now at least so production systems will continue working. Likely only temporary, so the new releases will be rushed ??

cheers,
Ross

G’day mpedersen,

It’s likely an out of memory problem, and it’s happening now because of increased memory use in Divi. You’re seeing it because you’ve chosen settings in my plugin that capture the whole content, possibly even the setting to Capture All. If you can get away with stepping down those settings, please do that.

Ultimately, the best solution for you is to permanently fix your mixed content problems as described in the “Images, iframes, embeds” section on this page:

https://ssl.webaware.net.au/testing/cleaning-up-content/

Use the Better Search Replace plugin, and clean things up properly. You will be able to set the fixer settings to Simple, or even remove the plugin.

NB: make sure that you are logged in to the website on https and can use the website admin, before running Better Search Replace!

cheers,
Ross

Yes, you need to add your main domain to Cloudflare and let it manage your domain if you want to make use of its free TLS for subdomains. My point was that you could add your main domain with no proxy (i.e. traffic goes direct to your domain), but proxy your media domain.

Ultimately, the simplest solution for you with free TLS for your media subdomain might just be a separate domain, bought cheaply from Namecheap or similar. Subdomains a nicely free, but cost you in the end. Don’t ask me about sub-sub-domains and Cloudflare, nor how I know!

cheers,
Ross

Those are your best options, I believe. You probably don’t have to have Cloudflare proxy your main domain, but you will need to add it to their DNS so that you can manage the subdomain. If that’s a problem, then look at how you can purchase and load a TLS certificate for GCS. I imagine they have some doco on that.

cheers,
Ross