webaware
Forum Replies Created
-
Forum: Plugins
In reply to: [SSL Insecure Content Fixer] InsecureG’day tahoemnts,
The background image is being loaded from http in your minified stylesheet:
https://msmlg.org/wp-content/cache/et/6/et-core-unified-15387787508368.min.css
Make sure that you’re on https when in the admin, and edit / save your theme settings to see if that fixes it. If it doesn’t, try removing / adding back your background image.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] About to activate your plugin…G’day Joseph,
People getting locked out almost certainly didn’t login to their admin on https to start with, and then forced their site to https (not something this plugin does). As long as you first check that you can access your admin on https safely, you will not be locked out.
W3 Total Cache can indeed be part of https problems (or any problems). Be sure to follow its guidelines for handling https correctly, and clear your cache after moving to https.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] How to use?G’day,
With a quick look, most pages seemed to be fine, but I saw that the About page has a problem with the banner image:
https://www.lapovertydept.org/lapd-history/
Try changing the fixer setting to Capture so that it can fix things in the page heading.
https://ssl.webaware.net.au/settings/
Ultimately, the best solution is to fix the content on your site:
https://ssl.webaware.net.au/testing/cleaning-up-content/
cheers,
RossG’day Kuba,
Yes, it appears that the post type is not being tested when triggers are processed, so any posts created on a trigger get caught by the hooks you have set up on the initial post. Perhaps storing the post ID of the post you’re processing could help — i.e. you see a post being created / updated, check its post type, save its post ID, then your triggers only process for posts of that ID.
cheers,
RossForum: Reviews
In reply to: [SSL Insecure Content Fixer] It worksG’day nausharipov,
No worries, it can be harrowing to find that your websites have been compromised by malware. If you do track down the method of attack and it was a plugin, please report it to the plugin team.
I hope this plugin has been working well for you, and look forward to you fixing the review 🙂
cheers,
RossG’day @kubitomakita,
Log Emails plugin author here. My plugin currently uses a CPT for email logs. Current release saves them with post_status ‘publish’, here’s a version that uses a custom post_status instead:
https://www.dropbox.com/s/kzfh0tpv4syqtna/log-emails-1.3.0-dev.zip?dl=1
That works for a notification I tried where the trigger was on published post. Haven’t tried with other triggers, but it sounds like it didn’t help antipole.
My ultimate solution is to move to a custom table, which is on my TODO list but probably won’t happen until later this year. Is there a filter hook we can utilise to exclude my CPT from triggering notifications?
cheers,
RossForum: Plugins
In reply to: [Log Emails] Log emails loops with email from NotificationPlease try this dev version. It changes the post status used for logs to that it won’t trigger any actions looking for new published posts.
https://www.dropbox.com/s/kzfh0tpv4syqtna/log-emails-1.3.0-dev.zip?dl=1
cheers,
RossForum: Reviews
In reply to: [SSL Insecure Content Fixer] It worksG’day @nausharipov,
I just checked the .zip file served by ww.wp.xz.cn and I can’t find any malware.
What indication do you have that your sites have malware? I’m happy to help you, but I need more information. I have not seen a support topic to help you with this problem, so this is the first I’ve heard of it.
cheers,
RossForum: Plugins
In reply to: [Log Emails] Log emails loops with email from NotificationG’day antipole,
I’ll check that out and see if I can fix it. Will get back to you.
cheers,
RossForum: Plugins
In reply to: [Eway Payment Gateway] Undefined property: WC_Gateway_EWAYNo worries!
cheers,
RossForum: Plugins
In reply to: [Eway Payment Gateway] Undefined property: WC_Gateway_EWAYG’day,
Wrong plugin, please try this one:
https://ww.wp.xz.cn/support/plugin/woocommerce-gateway-eway
cheers,
RossForum: Plugins
In reply to: [GF Windcave Free] Make Credit Card fields appearResolved – keys being used were for PxPost, not PxPay.
Forum: Plugins
In reply to: [GF Windcave Free] More than one DPS accountG’day clk87,
This plugin doesn’t allow for that. My pro eWAY add-on does let you do that, but of course that’s with eWAY accounts not DPS. Could that meet your requirements?
https://gfeway.webaware.net.au/faq/can-a-form-pay-to-different-accounts/
cheers,
RossForum: Plugins
In reply to: [Flexible Map] Map Cannot Be DisplayedG’day EnFi,
Geocoding is used to look up addresses. If you use an address to show your map, and don’t provide centre coordinates, it needs to use geocoding to find the coordinates.
If you’re using the Server API key in the plugin, that’s best for address lookups because it caches the results and reuses them. You need to use IP address restriction for that, so you’re doing the right thing there. You can specify more than one IP address if you need to.
For HTTP Referrer restriction, which you use for the JavaScript key, you don’t need to say http or https; just the domain name(s) and paths like this:
*.example.com/*cheers,
RossForum: Plugins
In reply to: [Flexible Map] Map Cannot Be DisplayedFor the Maps JavaScript API (which is what is used on web pages to show the maps), you are best off restricting your API keys by HTTP referrer. You can have one key for multiple website that way too, if your total API hits are low enough.
You can also add multiple IP addresses to IP address restriction, so if you’re using that for the server API key for address lookups, you can share the one key if the total API hits are low enough.
If your total hits are significant you will probably be best served by creating a second Google APIs project for it and giving it its own API keys.
cheers,
Ross