weaselnerd
Forum Replies Created
-
The solution I found to this issue was to create a Data Layer variable for
eventModel
, and on my trigger(s) filter that its value equals “undefined”.This works because
gtag()
events (like those fired by Google for WooCommerce) store their values undereventModel
in the data layer. ThedataLayer.push()
used by GTM4WP does not generate aneventModel
variable.Not sure if they’re going to bring back the old responsive behavior back or not at this point.
If you want to default all calendars to the “large” view by default you can do it with a filter instead of editing the plugin directly:
add_filter( 'em_calendar_get_default_search', function( $atts, $array, $defaults ) { $atts['calendar_size'] = 'large'; return $atts; }, 10, 3 );
Forum: Plugins
In reply to: [API KEY for Google Maps] Version 1.2.2 header update issueYup, that did the trick. Version 1.2.3 appears in the WordPress Updates admin and updated just fine.
Thanks for the fix.
Forum: Plugins
In reply to: [Themify - WooCommerce Product Filter] Add new filter doesn’t workI’ll chip in it appears to be a PHP 8 incompatibility.
Testing PHP 8 threw up the ajax 500 error in the console. Reverted back to PHP 7.4 and the edit screens load up again, which is fine for this site for now at least.
Sample error:
PHP Fatal error: Uncaught TypeError: floor(): Argument #1 ($num) must be of type int|float, string given in /nas/content/live/mysite/wp-content/plugins/themify-wc-product-filter/includes/class-wpf-form.php:407\nStack trace:\n#0 /nas/content/live/mysite/wp-content/plugins/themify-wc-product-filter/includes/class-wpf-form.php(407): floor('')\n#1 /nas/content/live/mysite/wp-content/plugins/themify-wc-product-filter/includes/class-wpf-form.php(331): WPF_Form->get_main_fields('price', 'Price', Array)\n#2 /nas/content/live/mysite/wp-content/plugins/themify-wc-product-filter/includes/class-wpf-form.php(278): WPF_Form->module('price', 'Price', Array, Array)\n#3 /nas/content/live/mysite/wp-content/plugins/themify-wc-product-filter/admin/partials/form.php(7): WPF_Form->form()\n#4 /nas/content/live/mysite/wp-content/plugins/themify-wc-product-filter/admin/class-wpf-admin.php(343): include_once('/nas/content/li...')\n#5 /nas/content/live/mysite/wp-includes/class-wp-hook.php(303): WPF_Admin->add_template('')\n#6 /nas/content/live/mysite/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters('', Array)\n#7 /nas/content/live/mysite/wp-includes/plugin.php(470): WP_Hook->do_action(Array)\n#8 /nas/content/live/mysite/wp-admin/admin-ajax.php(187): do_action('wp_ajax_wpf_edi...')\n#9 {main}\n thrown in /nas/content/live/mysite/wp-content/plugins/themify-wc-product-filter/includes/class-wpf-form.php on line 407, referer: https://mysite.wpengine.com/wp-admin/admin.php?page=wpf_search
Forum: Plugins
In reply to: [Happy Addons for Elementor] Parse error after todays update@ramyos Did you try removing the plugin and reinstalling as @sabbirshouvo mentioned? Strangely that was enough to remove the error on my site.
Forum: Plugins
In reply to: [Happy Addons for Elementor] Parse error after todays updateRemoving the plugin and reinstalling it from scratch from the plugin directory did seem to do the trick on my site. Thanks.
Forum: Plugins
In reply to: [Happy Addons for Elementor] Parse error after todays updateSame error.
Was able to re-activate the plugin by making a hotfix to
classes/widgets-manager.php
to disable the PDF viewer module. Comment out lines 984-995.// 'pdf-view' => [ // 'cat' => 'creative', // 'is_active' => true, // 'title' => __('PDF View', 'happy-elementor-addons'), // 'icon' => 'hm hm-lens', // 'css' => ['pdf'], // 'js' => [], // 'vendor' => [ // 'css' => [], // 'js' => ['pdf-js'], // ], // ],
Hopefully the next plugin update fixes this.
cheers
Appreciate it, thanks!
I updated my site with the new patch and it seems to be working just fine now.
Thanks for the update @sagarseth9.
cheers,
seanJust fixed the same error on a website.
Deleted the trailing commas at the end of lines 438 and 719 (inside the
printf()
statements) in includes/admin/tools.php to get it running again.Obvious not great I had to edit the plugin directly, so I hope this gets fixed by next update.
cheers