webaware
Forum Replies Created
-
Forum: Plugins
In reply to: [SSL Insecure Content Fixer] Capture Setting problem on 2 of 5 websitesIn your wp-config.php, please replace this line:
define('WP_DEBUG', false);with these lines:
define('WP_DEBUG', true); define('WP_DEBUG_LOG', true); define('WP_DEBUG_DISPLAY', false);Then try again. This will ask WordPress to write errors to a file /wp-content/debug.log so that we can see what error is killing the page.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Upgrade killed page edit abilityThanks. Unfortunately, it wasn’t enough to help me reproduce the problem. I’ll have a poke around with Visual Composer and see if I can stimulate a failure.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Upgrade killed page edit abilityCan you please use Classic Mode and copy the page content from the Text view in the editor? That will give me the content that the plugin is breaking on.
cheers,
RossG’day @sachin_c,
Your advertising widget is loading images over http: instead of https:
Have you changed your website to run from https: by editing your Website URL and Site URL?
Settings > General
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Site still has a “!” sign@thetravelgal good news, glad to hear things are working OK now.
@gadabout please start a new support topic for your problem. Also note, I can’t diagnose a website problem when it is hidden behind a “coming soon” screen.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Upgrade killed page edit abilityCan you please copy the content of the page from the Text view in the editor, save it in a text file, and email to me? It could be a problem with my code that does the search/replace on content. Likely because of the size of the content.
support (at) webaware.com.au
I can then test in my development environment and track down the problem.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Site still has a “!” signG’day @thetravelgal,
Please start a new support topic for your problem, and provide a link to the actual page that gets the warnings. I took a quick look and could not find a problem.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Connection is not secureG’day @sailors,
Try the tips on the Cleaning Up page:
https://ssl.webaware.net.au/testing/cleaning-up-content/
Your site seems to have some images being loaded from http: still, so I recommend backup of the site and running the Better Search Replace plugin to change image references in your content.
cheers,
RossForum: Reviews
In reply to: [SSL Insecure Content Fixer] how to remove the plugin without crashing site?Support is here, and doesn’t require a star rating (one or otherwise):
https://wordpress.org/support/plugin/ssl-insecure-content-fixer/
Forum: Plugins
In reply to: [SSL Insecure Content Fixer] Upgrade killed page edit abilityG’day sr4k,
What version were you running previously? (i.e. were you up-to-date or had you missed a few versions?)
Are you running any page builder tools, e.g. Visual Composer, Avada’s Fusion Builder, etc.?
Can you check your site logs for error messages please?
cheers,
RossG’day @tarawhitie,
Please open a new support ticket. Your problem is not the same problem (it just resembled it).
While you’re at it, please tick the option “use WooCommerce standard credit card fields” in the eWAY settings
WooCommerce > Settings > Checkout > eWAY
I have not yet released the fix I gave Dave, so you’ll need to run with the standard credit card fields for now (and I recommend you stick with them, they are better supported by themes).
BTW, I suspect that you are trying to use the test card number 4444333322221111 with the live gateway. This won’t work; only the sandbox gateway accepts that test card number.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Hi, how to activate back website?Your wp-config.php looks good to me, for most HTTPS detection problems. See how that goes.
If you still can’t get in, then you will need to stop forcing WordPress to https until you can get in to your admin. Remove any http to https redirects you might have in .htaccess, for example.
You can stop WordPress forcing your site to https by adding lines like this to your wp-config.php (replace example.com with your domain name):
define( 'WP_SITEURL', 'http://example.com/' ); define( 'WP_HOME', 'http://example.com/' );cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] No https unless refresh browserG’day @thebateser,
It sounds like a problem with a script or stylesheet generated by a plugin or your theme before the https fixes were done. Please run through your all settings in plugins and your themes and save again, to regenerate any scripts / stylesheets.
cheers,
RossCan you tell me please what you changed the HTTPS detection settings to?
@grtgrfx your site is set to force all requests to https, so disabling the plugin’s HTTPS detection won’t fix your problem.
Please add this snippet to your wp-config.php file, above the lines defining ABSPATH:
if (isset($_SERVER['HTTP_X_FORWARDED_PROTO']) && $_SERVER['HTTP_X_FORWARDED_PROTO'] === 'https') { $_SERVER['HTTPS'] = 'on'; }That will do what the plugin does for X-Forward-Proto header detection. If you had selected a different fix for HTTPS detection, the code will need to be different.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Fix Share Counts?? Canonical link??G’day aaronrobb,
Please post a URL to your site so that I can look at it with the browser console open. I can’t diagnose the problem with what you’ve told me.
cheers,
Ross