webaware

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

It won’t have any impact on the plugin, but you might still get mixed content warnings. Please let me know what happens, I’m unsure what the current browsers do with this now.

cheers,
Ross

G’day painlessseo,

No changes are made to the system, it only makes changes to content on-the-fly. Deactivating the plugin stops it having any effect.

For your videos, did you mean that they do use HTTPS, or don’t use HTTPS? If they can’t be loaded over HTTPS, they will likely not work due to mixed content.

cheers,
Ross

Use the recommended setting. It’s based on the headers sent by your proxy. WordPress apparently can already detect when the page is requested over HTTPS, so no need to change from that.

G’day,

I know nothing about QUIC.cloud, but the detected recommended setting is usually the best. It indicates that your website is already aware of the state of HTTPS in connections.

cheers,
Ross

Disable Emails can only disable all emails. It is not selective, it blocks emails from being sent.