webaware
Forum Replies Created
-
Forum: Plugins
In reply to: [SSL Insecure Content Fixer] Not able to disable/uninstall pluginG’day adequatelyadept,
The setting “unable to detect HTTPS” is the most problematic setting when removing the plugin. It forces detection of HTTPS whenever the site URL is set to HTTPS. Deactivating the plugin will stop that happening, and your website will enter a redirection endless loop.
When you visit the settings page for this plugin, what is the recommended setting for HTTPS detection? If it’s the setting you’re on, then your website can’t easily tell when pages are loaded by HTTPS, which is why this plugin has been used. If it’s another setting, then there’s a way to remove this plugin by adding some code to your wp-config.php file.
Another thing you can look at is the array of environment variables that you get when you run the admin page:
Tools > SSL Tests
With luck, it will give some way to detect when your pages are loaded from HTTPS.
cheers,
RossForum: Plugins
In reply to: [Disable Emails] Email still working after installing pluginThat can happen if your platform handles email in a special way, and Disable Emails is not able to replace the standard
wp_mail()function. I recommend that you check with Kinsta support who should be able to help you.cheers,
RossForum: Plugins
In reply to: [Gravity Forms Zero Spam] GitHub repo for submitting pull requestsNo worries, and I’ve removed this plugin now since Gravity Forms 2.7 does the same job natively.
I did look at that repo, but it was a version behind release when I looked at it.
cheers,
RossForum: Plugins
In reply to: [Eway Payment Gateway] Duplicate orders.G’day seboaus,
If the Eway transaction is successful, then this plugin has done its job and passed transaction information back to WooCommerce. Errors after that will be somewhere between WooCommerce and your theme. Have you checked your browser console for JavaScript errors? Make sure there are none after loading the checkout page at least, and then test a transaction to see if there are any errors in the console.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Beaver Builder + UABB Editor AccessYour best bet then is to permanently fix any mixed content using Better Search Replace. GreenGeeks has a tutorial on how to do that:
Fix a Mixed Content Error with Better Search & Replace
After you’ve run that, set the Fixer settings to Off and check your site. If you have HTTPS Detection set to “standard WordPress function”, you can remove SSL Insecure Content Fixer; otherwise, just leave it installed with Fixer set to Off.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Beaver Builder + UABB Editor AccessG’day murfemersed,
Do you have the Fixer settings on Capture All? If not, please try that. It seems to be required for some page builders.
cheers,
RossForum: Plugins
In reply to: [Disable Emails] Email Template Field Not Using HTMLG’day NoN Universe,
BuddyBoss is a premium plugin, so I have no visibility of what it is doing. As their paid customer, you should ask them to diagnose the problem for you. If they need a change made to Disable Emails, they can open a support ticket here with details of the problem.
cheers,
RossForum: Plugins
In reply to: [Eway Payment Gateway] Site error when in backendG’day mercurydan,
Thanks for the bug report. It’s happening because some other plugin is breaking the filter hook
woocommerce_email_order_meta_fieldsby passing null (probably the same mistake I made in Minimum Age for WooCommerce once, returning without a value).I’ve made a change that permits the first parameter to be an array now, so it should no longer break. Please update to v5.0.1 and let me know if you still see any problems.
cheers,
RossForum: Plugins
In reply to: [Log Emails] Cannot delete pluginG’day melligeorgiou,
I have no idea why W3TC would cause that, but then it does not actually surprise me. That plugin causes much grief (but have not heard of it causing grief with this plugin before!)
cheers,
RossForum: Plugins
In reply to: [Eway Payment Gateway] Logo is broken on WooCommerce Checkout page.G’day seboaus,
You need to update your Eway Site Seal in the settings. Get the new code from the Eway website:
https://www.eway.com.au/developers/secure-site-seal-wizard/
Then go your your WordPress admin and replace the Site Seal code that’s already there:
WooCommerce > Settings > Payments > Eway payment gateway > Show Eway Site Seal
cheers,
RossForum: Plugins
In reply to: [Eway Payment Gateway] Suggested way to handle customisation of errors?Ah, yes. I remember now. Codes only, for what you can see in a browser, again to stop giving information to card testers.
I’ve just added a filter hook so that you can change that if you prefer. Download the 5.0.0-dev again (or grab from GH).
https://www.dropbox.com/s/ghdjeyaouf8ibn1/eway-payment-gateway-5.0.0-dev.zip?dl=1
The new filter hook is
woocommerce_eway_error_msgand it passes$error_msgand$response. If you call the following, you’ll get the detailed message as written to the log:$response->getErrorsForLog()However, be mindful of giving card testers too much help!
cheers,
Ross- This reply was modified 3 years, 6 months ago by webaware. Reason: spelnig
Forum: Plugins
In reply to: [Eway Payment Gateway] Suggested way to handle customisation of errors?G’day jaydisc,
It’s hooked up alright, but that code in particular is not handled — Eway doesn’t map it to a friendly description. That’s because it usually is the result of a bad card number attempt, and giving a friendly description to someone testing out card numbers isn’t seen as useful.
But you can hook
eway_code_descriptionto change (supply!) a friendly message if you wish. It takes two parameters,$msgand$code.cheers,
RossThe branch is called refactor:
https://github.com/webaware/eway-payment-gateway/tree/refactor
I haven’t merged into master yet, likely to do that in the next few days sometime and then release.
G’day jaydisc,
Well, I’ve never done that before: manually create a WooCommerce order and pay from a link in an email. Did not know about it! Thanks for the bug report 🙂
I’ve fixed it in the dev version, which you can download and try here:
https://www.dropbox.com/s/ghdjeyaouf8ibn1/eway-payment-gateway-5.0.0-dev.zip?dl=1
NB: this includes a big code refactor, so best if you can try it on a staging server first. Otherwise, be ready to revert to 4.5.1 if you have problems. I hope to release 5.0.0 by early next week, if not sooner.
Here’s what I changed for the fix for this bug:
https://github.com/webaware/eway-payment-gateway/commit/dbea519644c904c40cbcc7255e73fcf08d178317
cheers,
RossForum: Plugins
In reply to: [Minimum Age for WooCommerce] Change location in checkoutThanks for your help finding this bug, it is now fixed in v1.0.18.
cheers,
Ross