webaware
Forum Replies Created
-
Forum: Plugins
In reply to: [Eway Payment Gateway] Not a valid eWAY Customer IdG’day @stevemyecom,
I think you need to register a Sandbox account before you can use the Sandbox with a customer ID other than 87654321.
cheers,
RossG’day Yuli,
The entry payment status should change from Processing to Approved when you return to the website from the Payment Express page. If it isn’t, then there is something wrong.
I test with WordFence just now, and could not make it cause this problem. Perhaps it isn’t at fault here (although I still have my suspicions).
Are you using pretty permalinks, or do you have your website set for “Plain”?
Settings > Permalinks
Are you able to share a link to the form? If you prefer to keep that private, please send to me via my support form.
cheers,
RossG’day Yuliana,
Did the Payment Status change from Pending to Approved? Please check the entries. Look at the Payment Details box on the right-hand side of the page when you view an entry.
Are you running any “security” plugins? Can you temporarily deactivate and retest please? Some “security” plugins block legitimate requests from payment gateways.
Can you test with minimal other plugins activated, e.g. just Gravity Forms and this add-on?
cheers,
RossG’day Yuliana,
Did the Payment Status of the entries change to Approved? If not, it means that Gravity Forms isn’t getting the payment notification from Payment Express. Let me know, we can then examine why if that’s happening.
cheers,
RossG’day Yuliana,
Those options tell the add-on to not send notifications until a successful payment is received. If your customer submits a form but either doesn’t complete the Payment Express page, cancels it, or the payment fails, then no notifications are sent.
If you need to receive notifications anyway, you can tick the option for “Always execute delayed actions, regardless of payment status”. You can then conditionally send some notifications only if the entry has an AuthCode (condition AuthCode “is not” {empty string})
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Insecure logoG’day,
Looks like some of your pages have images loaded from http, not https. You can edit your page content to fix that, or if you prefer, just change the fixer settings to Content.
In general, I would advise you to edit your website from https so that any images are linked from https, not http. This will prevent mixed content warnings in content.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Insecure content still exist on pageG’day rajsshah86,
Looks like you’ve resolved this. If you still need assistance, please ask and I’ll try to respond more promptly 🙂
cheers,
RossG’day tanckom,
Happening on a couple of pages, e.g. this one.
That’s the plugin SiteOrigin Widgets Bundle doing that. It has written some customised CSS stylesheets with the incorrect protocols for Google web fonts.
You can probably fix this by logging in to your WordPress admin and select your fonts again in that plugin’s settings. It should then rewrite the stylesheets with the correct protocol.
Ultimately, I recommend that you contact the authors of that plugin and tell them that they should only be using https for Google web fonts, never http.
cheers,
RossG’day guys,
This plugin doesn’t make any changes to your website, it fixes some things “live” as it were. You can manually apply any fixes it makes, and then deactivate the plugin, activating / deactivating won’t fix your website.
If the problem you’re fixing is HTTPS detection, then you can add a code snippet to your wp-config.php to do what this plugin is doing. Tell me which setting you are using, and I can help you pick the correct code snippet — or you can look at the source code and see for yourself.
cheers,
RossG’day wordlala24,
Your website is loading two images using http, not https. One is Menu.jpg and is being loaded in the menu. The other is Newsletter.jpg and is being loaded by your Mailchimp form.
See if you can change both of them to https in your WordPress admin. You might need to login to the admin using https, and remove / add back the images so that they get the correct protocol.
If you can’t get that to work, try changing to the Capture fix level.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Logo is still served over http on some pagesG’day bmaas93,
Looks like you’ve resolved this. If you still need assistance, please ask and I’ll try to respond more promptly 🙂
cheers,
RossForum: Plugins
In reply to: [Gravity Forms Eway] Can't get any transaction on eway sandboxG’day sos3524576,
Did you use a Product field to build those price choices?
There must be an amount to charge, otherwise nothing gets sent to eWAY. If you used a basic Radio Buttons field instead of a Product field configured for radio buttons, then Gravity Forms will see that as just a list of options with no price attached, and there will be no total amount for eWAY to charge.
You’ll find the Product field under the Pricing fields palette.
https://www.gravityhelp.com/documentation/article/product/
cheers,
RossForum: Plugins
In reply to: [GF Windcave Free] DPS Payment Cloud Improvements QueryG’day volom,
That’s something specific to your website host.
The plugin references the payment gateway server by name, so it depends on DNS (domain name service) to give back the correct IP address. DPS have already taken steps to ensure that domain name lookups will get the correct address after the switchover. The way they do that is to set TTL (time to live) for the DNS lookup to something very small, so that the systems asking for the address don’t cache it for very long. When they ask for the DNS lookup again, they’ll get the new address.
The note that DPS has sent to you is basically telling you that, and telling you to make sure that your website host won’t cache the DNS lookup past what they tell them. If your host has set things up correctly, this won’t be an issue.
If you’re unsure, please ask your website host to confirm.
cheers,
RossForum: Plugins
In reply to: [Gravity Forms Eway] Wrong amountPlease ignore the dev version; v2.2.2 has now been released.
cheers,
RossForum: Plugins
In reply to: [Gravity Forms Eway] Transaction failed – UnauthorizedG’day Bruno,
You get that error when your API key/password pair is incorrect. Please check those in the settings
Forms > Settings > eWAY Payments
cheers,
Ross