nadavss
Forum Replies Created
-
Thanks Paul, I’m no longer seeing the error after updating just now.
Hi, just a follow-up to let you know that it’s not your plugin causing the issue. It was caused by an update to another plugin that was overriding WooCommerce email files.
Sorry for any inconvenience.You should probably know that the error “Warning: date() expects parameter 2 to be long, object given in” is still showing, although it doesn’t seem to be affecting anything.
Forum: Plugins
In reply to: [Disable Blogging in WordPress] Conflict with Visual ComposerNo problem.
Thanks again for your support on this.Forum: Plugins
In reply to: [Disable Blogging in WordPress] Conflict with Visual ComposerI tested yesterday by disabling all plugins and activating one by one, and this revealed Disable Blogging to be causing the conflict. I tried enabling and disabling a few of the settings on Disable Blogging to see if it would fix this, but that didn’t help.
I 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?
As I said, we want Disable Blogging as it does exactly what we need it to, so I’m happy to continue using as is, and will certainly let you know right away if this bizarre conflict somehow re-appears.
Forum: Plugins
In reply to: [Disable Blogging in WordPress] Conflict with Visual ComposerCorrection: I meant that we reactivated Disable Blogging, not Disable Plugin, of course…
Forum: Plugins
In reply to: [Disable Blogging in WordPress] Conflict with Visual ComposerThanks for your quick response.
We’re running Version 5.0.1 of Visual Composer.
This is how it should look:
What was happening was that the circled bits in the screenshot were disappearing. We could still click on them, but we were doing so blind, i.e. we could mistakenly hit trash instead of edit.
I just reactivated Disable Plugin to take a photo of the problem, and would you believe it – everything was working as it should. It’s really strange, as yesterday when I was testing this, it was a clear-cut case of: activate your plugin, the conflict occurs; deactivate it, problem solved.
So I guess we can consider this temporarily solved and I’ll touch base again if the problem re-occurs. Unless you have an inkling as to what the issue could be and we could give it a permanent fix?
Cheers.