webaware
Forum Replies Created
-
Forum: Plugins
In reply to: [SSL Insecure Content Fixer] Destroyed my websiteG’day webtexweb,
This plugin does not change any settings on your website.
Did you change your WordPress Address (URL) and Site Address (URL) to https? If you did, and your site can’t detect https, then you’ll be locked out.
You can force your site back to http while you sort out your problems by temporarily adding the following lines to your wp-config.php file, changing the domain name to your domain name of course:
define( 'WP_SITEURL', 'http://example.com/wordpress' ); define( 'WP_HOME', 'http://example.com/wordpress' );You might also want to temporarily add this to your wp-config.php file, to stop this plugin detecting https and overriding some other mechanism on your website:
define('SSLFIX_PLUGIN_NO_HTTPS_DETECT', true);Then reinstall this plugin and check what it says for HTTPS detection on either its settings page or the Tools page.
https://ssl.webaware.net.au/https-detection/
cheers,
RossG’day miguelitomola,
That’s there to help me diagnose why a WordPress installation can’t detect HTTPS.
Can you tell me please, what are your environment variables called? And are you adding them as environment variables, or server variables?
cheers,
RossG’day Hugo,
Thanks for the bug report! I actually handle JPY correctly for a couple of other gateway integrations, so it’s a bad oversight on my part that I missed it on my eWAY integrations.
Can you please try this version?
https://www.dropbox.com/s/ctjqayzudgac6ga/eway-payment-gateway-4.0.3-dev.zip?dl=1
cheers,
RossG’day Bond,
There’s lots of things on that site. Can you point me to a bookings page please, so that I can see a form that should have the card details on it?
cheers,
RossThe “returned nothing” ones could be someone trying the test card number, 4444333322221111, on the live gateway. That number is only for the sandbox.
V6111+V6010 means that:
- you’ve entered your Rapid API key/password and the Rapid API is being used
- your eWAY account requires Client Side Encryption (most do)
- the transaction is being sent without Client Side Encryption
If you’ve set your Client Side Encryption key, then it could be that your site has a JavaScript error preventing Client Side Encryption from working. Please provide a link to the site so that I can inspect it.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Mixed Content error imagesG’day des,
Your website is loading some images over HTTP still. Read about cleaning up content — the section about Images, iframes, embeds.
https://ssl.webaware.net.au/testing/cleaning-up-content/
A short-cut is to set your fixer level to something higher, like Content or Capture. But I recommend cleaning up your content if you can.
cheers,
RossForum: Plugins
In reply to: [Eway Payment Gateway] Failure descriptionsG’day gonget,
It should already be doing that. What product are you integrating with? e.g. WooCommerce, WP eCommerce, Events Manager, AWPCP?
cheers,
RossG’day mindplant,
I’m not seeing any problem on that site. Can you please tell me what product you’re adding, and what browser you’re seeing this problem in?
cheers,
RossG’day digibond,
I suggest that you turn on logging in the eWAY add-on to see what gets processed. This will track when a transaction is attempted with eWAY and any errors that it gets. If it’s not attempting a transaction, you should be able to see that by omission: i.e., if you get a booking, but not a transaction.
Events > Payment Gateways > eWAY > Settings > Logging
Set it to All Messages, and check the log file (via FTP) after a few bookings.
cheers,
RossForum: Plugins
In reply to: [Gravity Forms Eway] Pay different accountsG’day Jacob,
I’ve just added a new FAQ page for this. You can see a screenshot of those settings now.
https://gfeway.webaware.net.au/faq/can-a-form-pay-to-different-accounts/
cheers,
RossForum: Plugins
In reply to: [Gravity Forms Eway] Pay different accountsG’day Jacob,
The Free add-on can’t do that, but you can do that with the Pro add-on. It works differently to the Free add-on, using a “feeds” model like the PayPal add-on does.
https://gfeway.webaware.net.au/pro/create-a-feed/
You can add two feeds for a form, and use conditional logic to select which one to process from. Leave one on the default add-on settings, and enable Customise Connection on the second one to enter the API credentials for your second account.
cheers,
RossG’day topofthemornin,
Just saw this in RSS (no email came, dammit!)
Try adding this to your wp-config.php file, before any mention of ABSPATH:
if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && strtolower($_SERVER['HTTP_X_FORWARDED_PROTO']) === 'https') { $_SERVER['HTTPS'] = 'on'; }It hard-codes the HTTPS detection used by a bunch of different server models, which is probably what’s keeping you locked out.
If that doesn’t work, try the code specific to Cloudfront instead.
cheers,
RossG’day @draczilla,
I can see a missing image getting a 404 on that page:
https://baredia.no/wp-content/uploads/2017/06/deb2.jpg
Looks like it’s in a Revolution Slider.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] eBay and HTTPS on website imagesG’day questionsrus,
Are your sure your website doesn’t force everything to https? e.g. when I visit the link in your wordpress.org profile, and change the https to http, it instantly redirects to https which means the web server has a redirect. That could also be Cloudflare settings. If you have Cloudflare set to force https, it’ll do that for images too.
I checked the code for wp-lister, and it fixes all image links so that they’ll work on eBay. I don’t think my plugin is doing anything to change that back, so I strongly suspect a http > https redirect.
Try getting a link to an image, pasting it into the browser location, and changing it to http. See if it instantly reloads as https. If it does, you have a redirect. My plugin doesn’t do that.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Not all content secureG’day tadekh,
One of your widgets is loading an image on http:
http://eva.temashdesign.com/fashionimport/wp-content/uploads/sites/4/2017/01/payment.png
Edit the text widget and change that to https.
cheers,
Ross
