webaware
Forum Replies Created
-
Forum: Plugins
In reply to: [Disable Emails] When I deactivate this plugin….G’day R,
Yes, deactivating this plugin returns normal email operation. It only stops emails while it’s activated.
cheers,
RossForum: Plugins
In reply to: [DPS PxPay for WP eCommerce] Plugin not workingNo worries!
Forum: Reviews
In reply to: [DPS PxPay for WP eCommerce] .G’day danny2305,
Please open a support ticket if you have a problem. I’ve just checked the plugin again in my development environment, it’s still working.
https://wordpress.org/support/plugin/dps-pxpay-for-wp-ecommerce/
cheers,
RossForum: Plugins
In reply to: [Eway Payment Gateway] eWay Recurring PaymentG’day Deepak,
No, this plugin only supports single payments. For subscriptions, you should look at the WooCommerce integration:
https://woocommerce.com/products/eway/
cheers,
RossG’day Chris,
It’s the HTML5 Validation plugin — it modifies the HTML for the card number and cvv inputs, so my regular expressions were failing. Please try this updated version:
https://www.dropbox.com/s/ylczxt7x3rt8gd9/gravityforms-eway-2.2.6-dev.zip?dl=1
It’ll be released sometime this week, with these changes:
* fixed: Gravity Forms 2.3 compatibility; don’t directly access database tables
* fixed: amounts in Japanese Yen (JPY) are already in the lowest denomination; no need to shift to / from cents
* fixed: Client Side Encryption fails when Gravity Forms HTML5 Validation plugin is activecheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Can the plug-in be deleted after use?G’day Phil,
Check out this page. It should have your answers.
https://ssl.webaware.net.au/home/deactivate/
cheers,
RossAlso, do you get a warning about your PCRE version? It’s a regular expression module used in PHP, and it must not be too old. The plugin will add a notice to your WordPress admin if you’re system has a very old version of PCRE. It can cause this exact problem.
cheers,
RossG’day Chris,
Normally, the Card Number and CVV fields are modified to have a custom attribute added to them, which my script uses when it calls the Client Side Encryption. That custom attribute (
data-gfeway-encrypt-name) isn’t there, so something on your website is interfering with the process.Do you have anything that might be messing with the Gravity Forms filter
gform_field_content? I use that to inject the custom attribute. e.g. a Gravity Forms related plugin, or something in your theme.cheers,
RossForum: Plugins
In reply to: [Gravity Forms Eway] Transaction failed: V6111: Unauthorised…G’day Sean,
Something on your website is turning all script and css URLs into relative links. Unfortunately, it’s not just doing it for links to things on your website, but also to links for external scripts — including the eWAY Client Side Encryption script:
/scripts/eCrypt.min.jsThis script should be loaded from the eWAY website, but it’s failing because the browser is trying to load it from your website instead, and of course, it’s not there.
Thus, no Client Side Encryption, and you get that error.
cheers,
RossForum: Plugins
In reply to: [GF Windcave Free] Payment Express security changesG’day Leigh / Meg,
My plugins all use the standard WordPress remote access methods, so they will maintain compatibility as long as your web server system software is up to date. You can easily test your web server to see if it supports TLS 1.2 by installing this plugin and running its test page:
https://wordpress.org/plugins/tls-1-2-compatibility-test/
[second posting attempt; forum ate my first reply!]
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] URGENT! Locked out of siteYou could also have temporarily fixed with this in your wp-config.php:
define( 'WP_SITEURL', 'http://example.com/' ); define( 'WP_HOME', 'http://example.com/' );Glad you got it sorted though.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Still some warningsG’day karltucker65,
No, not that I know of. Have a read of how to identify what’s causing the warnings:
https://ssl.webaware.net.au/testing/
Then look at how to clean up the insecure content. There are different levels of the fixer, but often it’s best to fix content at the source if you can. This page discusses both ways:
https://ssl.webaware.net.au/testing/cleaning-up-content/
cheers,
RossG’day Elizabeth,
The problem I’m seeing is the background image on the front page. You can probably fix that easily by:
* logging in to your admin on https
* removing and re-adding the background imageAn alternative is to set your fixer level to Content, but I’d recommend you try fixing it first because it will make for a faster website.
You can find out more about cleaning up insecure content here:
https://ssl.webaware.net.au/testing/cleaning-up-content/
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] “Plugin: SSL Insecure Content Fixer”G’day softbleumedia,
I just checked a bunch of pages in Google Chrome, and could not see any insecure content problems. Can you post a link to a page that has a problem?
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] How does the plugin work?G’day mirgcire,
This plugin does not make any permanent changes to your website. It changes things on-the-fly, when a page is loaded from your website.
You can find out more about what this plugin does by reading about its Settings page:
https://ssl.webaware.net.au/settings/
cheers,
Ross