Fact Maven
Forum Replies Created
-
Forum: Plugins
In reply to: [Disable Blogging in WordPress] Conflict with Visual ComposerI know it sounds strange, but it truly was causing a conflict yesterday, and since re-activating today – it’s working fine. Are there any possible explanations for this?
Not sure since we haven’t been able to reproduce it on our end. To take a guess, it could be cache related.
Since you are no longer experiencing any issues. I’ll mark this ticket as resolved until you experience this issue again.
Forum: Plugins
In reply to: [Disable Blogging in WordPress] Conflict with Visual ComposerInteresting. Did you recently change your settings in Disable Blogging?
We also use VC with the latest version (
5.0.1
) on websites that we develop and haven’t noticed a conflict with it so far. There may be another plugin that is causing the conflict. Please check by disabling all of your plugins and activate each plugin one-by-one until you see the VC options missing again.Forum: Plugins
In reply to: [Disable Blogging in WordPress] Conflict with Visual ComposerIn order for us to help narrow down and fix this issue, please verify the following for us.
…since upgrading to the latest version of Visual Composer…
What version are you currently running?
…the row and column tags disappear from front-end editing on VC, which makes it extremely difficult to use VC properly (I wish I could show you a screenshot of what I’m talking about, but WordPress doesn’t appear to offer this)…
WordPress doesn’t offer screenshots, but you can take one from your computer. Please look online on how to take a screenshot (PC or Mac). Show us what VC looks like before enabling Disable Blogging, then another one with the plugin activated. Then you can upload the screenshots on an image sharing site such as Imgur and share the links here.
Do you have any idea what could be causing the issue in your plugin’s code?
Based off of VC’s comment, we have an idea on where to start investigating. Addressing the points above will help us narrow it down.
- This reply was modified 7 years, 7 months ago by Fact Maven.
Forum: Plugins
In reply to: [Remove HTTP: Fix Mixed Content Warning] Use With Avada ThemeYes, this is what we’re looking for. Thank you. We’re looking into this now.
Forum: Plugins
In reply to: [Remove HTTP: Fix Mixed Content Warning] Use With Avada ThemeThanks for the 5 star review.
Please provide us a sample of your container background so we can test this on our end. This way, we can look into this.
Forum: Plugins
In reply to: [Specify Image Dimensions] Blank height and width attributesThis issue is now resolved since v1.1.0
Forum: Plugins
In reply to: [Specify Image Dimensions] Blank height and width attributesFound out the issue. Working on applying a fix.
- This reply was modified 7 years, 9 months ago by Fact Maven.
- This reply was modified 7 years, 9 months ago by Fact Maven.
Forum: Plugins
In reply to: [Remove HTTP: Fix Mixed Content Warning] Didn’t help with my imagesJust revisited your website and I see you are no longer experiencing mixed content issues. Was this fixed manually though your theme?
Forum: Plugins
In reply to: [Specify Image Dimensions] Blank height and width attributesWhen you disable our plugin, do you still see blank dimensions?
Forum: Plugins
In reply to: [Specify Image Dimensions] Blank height and width attributesThanks for bringing this to our attention.
We started investigating your issue and will get back to you with a response.
Forum: Plugins
In reply to: [Remove HTTP: Fix Mixed Content Warning] Didn’t help with my imagesIn your case, it would be quicker to make the fix on your end since it’s only one image that’s causing the issue. If this is all content-related, you can ensure that all of your links are pointing to HTTPS by following these steps.
Until then, if we can figure out a way on our end to update our algorithm to also fix it, we will definitely push it in the next update.
- This reply was modified 7 years, 9 months ago by Fact Maven.
Forum: Plugins
In reply to: [Remove HTTP: Fix Mixed Content Warning] Didn’t help with my imagesAfter investigating, this is the image that’s causing the mixed content warning:
Looking at the source code, here’s a snippet of what you currently have:
<section class="section-contact" id="section-contact" style="background-image: url( https://fourfincreative.com/online/wp-content/uploads/2014/03/iStock_000045557738_Small.jpg);">
This issue can be easily fixed on your end by changing manually to the following:
<section class="section-contact" id="section-contact" style="background-image: url(//fourfincreative.com/online/wp-content/uploads/2014/03/iStock_000045557738_Small.jpg);">
Q: Why doesn’t Remove HTTP remove the protocol in this case?
We only have protocols removed from the following sources:
script
,link
,base
,img
,form
,a
,meta
,iframe
,svg
In previous versions, we did have a more aggressive algorithm to remove any reference of
https://
orhttps://
. However, we discovered that it was too aggressive and caused issues with some plugins.I also see that your other
<section>
tags use protocol-relative URLs:<div class="services-bg" style="background-image: url(//fourfincreative.com/online/wp-content/uploads/2014/03/smallboat.jpg);"></div> <div class="blog-bg" style="background-image: url( '//fourfincreative.com/online/wp-content/uploads/2014/03/blog.jpg' );"></div>
Forum: Plugins
In reply to: [Disable Blogging in WordPress] Fatal error with the setup woocommerceApologies, didn’t realized you were actually the first person to review our plugin! Thanks for being with us since the beginning!
Forum: Plugins
In reply to: [Disable Blogging in WordPress] Fatal error with the setup woocommerceWe appreciate your contribution to help making sure Disable Blogging runs smoothly. As a token of our thanks, we’ve added you to our list of bug spotters which you can find on our plugin page here.
If you enjoy using this plugin, please consider giving this plugin a five star review.
- This reply was modified 7 years, 9 months ago by Fact Maven.
Forum: Plugins
In reply to: [Disable Blogging in WordPress] Fatal error with the setup woocommerceThis issue is now fixed in the latest update v2.0.4