webaware
Forum Replies Created
-
Forum: Plugins
In reply to: [SSL Insecure Content Fixer] Version 2.2.2 breaks Visual Composer BackendOK, I reckon I have a fix. I’ll release this once I get confirmation from a couple of testers, but in the meantime, here it is pre-release if anyone wants to try it.
https://www.dropbox.com/s/ugitrqdal9gqy7c/ssl-insecure-content-fixer-2.2.3-dev3.zip
Many thanks to @jsherk for stepping up and providing an environment where I could test this. It would have taken me a long time to find the problem without that.
cheers,
RossG’day joalmama78,
All of your warnings are from images, many from the slider. You need to clean up your sliders to only load from https — perhaps edit them when logged in to the admin from https.
A simple fix could be to set the fixer mode to Content.
https://ssl.webaware.net.au/settings/
The best fix is to replace all http links to your site, and the Avada demo site, with https links. You can do that easily with the Better Search Replace plugin.
https://wordpress.org/plugins/better-search-replace/
e.g. replace http://avada.theme-fusion.com with https://avada.theme-fusion.com
cheers,
RossG’day Jeff,
Thanks for the offer. I can’t reproduce the problem, so I’m grateful that you can accommodate my testing. Email address:
support (at) webaware.com.au
cheers,
RossG’day Jeff,
Yes, I’ve had a few reports of this problem. I can’t reproduce it myself — everything works fine for me in my test environments. You can see that others have reported the same though, so it’s definitely a problem:
https://wordpress.org/support/topic/version-2-2-2-breaks-visual-composer-backend/
I’ve asked for access to a test environment that exhibits this problem, so that I can diagnose it. Nobody has stepped forward yet. Are you able to help? If I can test it, I can fix it.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Deactivate after useMy plugin makes no changes to the website. It cleans things up on-the-fly. It’s a way to get a site working on https quickly, or to fix up some crap plugins / themes that misbehave.
If you have content that needs fixing, my plugin will cover you while you get ready to clean up the content. I use WP Migrate DB Pro (because it’s pretty much always on sites I work on) or Better Search Replace otherwise.
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] Still loading from unauthenticated sourcesMaybe. But I need to see the website to know. Can you post a link please?
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] no httpsG’day papaworx,
It sounds like your website certificate doesn’t match your website’s domain name. Can you share the URL to your site so that we can inspect it?
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] 500 Internal Server ErrorG’day Banyo,
The plugin makes no changes to the website, so deactivating it stops its effect.
Try removing the new defines you added to your wp-config.php file.
Also check your website logs to see what is breaking. If you have trouble finding your website logs in your hosting control panel, you can turn on
WP_DEBUGandWP_DEBUG_LOG(and turn offWP_DEBUG_DISPLAY) in your wp-config.php file so that logs go to the filewp-content/debug.log:https://codex.wordpress.org/Debugging_in_WordPress
cheers,
RossForum: Themes and Templates
In reply to: User Registration, Permission and AccessMembers lets you create a new role. You can then edit pages / posts to restrict access to only selected roles. There are lots of other good plugins in that space too, e.g. Restrict Content and its Pro version.
I tend to start simple with Members plugin until I know more about what restrictions are required. You lose nothing if you need to drop Members in favour of something more complex, and often you’ll find that Members is all you need.
For front-end logins, I tend to go with this plugin. It’s pretty flexible, and can be customised through templates.
https://wordpress.org/plugins/login-with-ajax/
cheers,
RossForum: Plugins
In reply to: [SSL Insecure Content Fixer] After update v.2.2.2 Page Edit isn’t workingG’day militarium,
Please read this thread:
https://wordpress.org/support/topic/version-2-2-2-breaks-visual-composer-backend/
If you can offer more information or especially an environment in which I can test this, please do. Right now, I can’t reproduce the problem, so I can’t fix it.
If you delete this plugin, https fixes stop. There are alternative plugins, which you can search for in the plugin directory.
cheers,
RossG’day folks,
Please read this thread:
https://wordpress.org/support/topic/version-2-2-2-breaks-visual-composer-backend/
If you can offer more information or especially an environment in which I can test this, please do. Right now, I can’t reproduce the problem, so I can’t fix it.
cheers,
RossForum: Plugins
In reply to: [WP eCommerce] What is the correct directory for payment gateways?You can write a payment gateway integration using a plugin. While I won’t hold it up as a shining example, here’s one that integrates with WP eCommerce without being lost each time you upgrade that plugin.
https://en-au.wordpress.org/plugins/eway-payment-gateway/
You can browse the source code in GitHub. Selected bits of interest:
Hooking WP eCommerce to register a new gateway integration
The gateway integration classNB: WP eCommerce did have some very sparse doco about writing payment gateway integrations once, but it’s been lost since the doco site was rearranged.
cheers,
RossAha!
Forum: Plugins
In reply to: [Gravity Forms Eway] Error submitting paymentG’day diskmandotnet,
With eWAY Client Side Encryption, the credit card number and cvn are encrypted and then the input fields are wiped so that they cannot be intercepted. The encrypted values are passed to eWAY with the transaction.
Those error numbers indicate two things. First, your transaction made it to eWAY, and they returned an error with some codes for why it failed.
Second, the codes mean, in order:
- Do Not Honour
- International Transaction Fraud
It means that something about the transaction details triggered Beagle to reject the transaction as possibly fraudulent. Generally it’s a combination of the address and the computer’s IP address passed to eWAY.
If you think that this is wrong, I suggest that you discuss with eWAY. Be sure to provide them with details about the transaction you were testing.
cheers,
Ross