SamVW
Forum Replies Created
-
Forum: Plugins
In reply to: [Contact Form 7] Recaptcha 3 + logo of Recaptcha all over my blogYou can drop that code into your functions.php to selectively load it only on pages with a contact form.
Or you can switch to a different form plugin that allows the use of V2 recaptcha.
@plugin-author, this update was a deal breaker and was poorly executed.
– Pushing a V2 -> V3 switch without an opt-in means you are voluntarily breaking clients’ contact forms until they go out of their way to fix it. I have several clients that updated without realizing this was breaking their contact forms.
– Despite the name, V3 is not a straight upgrade from V2. Even if it were loading only on form pages, V2 is still preferable for people that don’t want to have your web design decisions forced on their websites.
– The fact that it loads on every page is egregious. You realize people are getting popups to pick cars on page load on every page of a website?Thanks for your effort making a great plugin for all these years. Unfortunately we’ve had to remove it from all our sites it was in use on.
Forum: Plugins
In reply to: [MC4WP: Mailchimp User Sync] Auto sync by role doesn’t remove users by roleDamn it, an hour later and the user is now set to unsubscribed. All clear.
Forum: Plugins
In reply to: [ACF-VC Integrator] fopen error after moving site or changing web root pathAwesome, thanks!
Forum: Plugins
In reply to: [W3 Total Cache] Fatal Error – get_feed_permastructSame error when creating variable products with attributes.
I was able to stop the error from occurring by unchecking everything under W3TC > Page Cache > Purge Policy: Page Cache.
Forum: Plugins
In reply to: [WPBakery Page Builder Addons by Livemesh] Plugin crashes JSSorry but this issue is definitely caused by your plugin.
I’ve used it on two sites, and in both cases it broke js for several scripts on the page, giving the error cited in the OP. Disabling LVCA fixes it.
The scripts getting broken begin with:
$ = jQuery.noConflict();
When I remove
jQuery.noConflict(),
from lvca-frontend.min.js everything works again.I’m not saying the fault doesn’t also lie with other theme/plugin authors, but your plugin is the only one I’ve found so far that causes this conflict.
I fixed it by replacing the function above with:
public static function get_module_path( $file ) {
global $itsec_globals;
$path = str_replace( dirname(dirname( $file )), ”, dirname( $file ) );
return trailingslashit( $itsec_globals[‘plugin_url’] . ‘modules/free/’ . $path );
}It doesn’t address the root of the problem, but it’s an ok workaround I guess. The bad part is I’ll have to apply this every time I update the plugin until it gets fixed.