anonymized-13171256
(@anonymized-13171256)
What theme are you using? Where can I find it?
What plugins are active?
Are you using a page builder? If so, which one?
https://jimscomputerservices.com.au/testimonials/
No page builder.
Theme:
WFX Girder
This is a child theme of Wonderflux.
I deactivated all my plugins but still is down if there are two shortcodes:
[testimonial_view id=1]
[testimonial_view id=2]
anonymized-13171256
(@anonymized-13171256)
Thank you.
I would like to see that page when it’s working. Please remove the shortcode that breaks it.
https://jimscomputerservices.com.au/testimonials/
I removed:
Display Testimonials
display Modern
[testimonial_view id=2]
anonymized-13171256
(@anonymized-13171256)
Thanks. I found the source of the conflict with Wonderflux framework. I will attempt to handle it in my plugin and with the Wonderflux developer.
Meanwhile, if you want, I can show you a simple workaround that involves adding one line of code.
Sure. I would like to know the solution.
anonymized-13171256
(@anonymized-13171256)
Edit the main plugin file strong-testimonials.php and find ‘private function preprocess’ at line 1161. Add this line right after it:
return; // quick fix for Wonderflux compat
So the whole function should look like this:
private function preprocess( $atts ) {
return; // quick fix for Wonderflux compat
$atts = shortcode_atts(
$this->get_view_defaults(),
$atts
);
$this->view_atts = $atts;
if ( $atts['form'] ) {
$new_view = new Strong_View_Form( $atts );
}
elseif ( $atts['slideshow'] ) {
$new_view = new Strong_View_Slideshow( $atts );
}
else {
$new_view = new Strong_View_Display( $atts );
}
$new_view->process();
/**
* The whole purpose of preprocessing is to load our styles
* in <head> to avoid FOUC.
*/
add_action( 'wp_enqueue_scripts', 'wpmtst_view_scripts' );
}
This is a temporary fix.
Thanks for the temporary fix. Will wait also for the official update on the plugin.
Great help! thanks so much
anonymized-13171256
(@anonymized-13171256)
No problem. Thanks for reporting it. FYI, I will be publishing a minor update later today so if you run the update you will have to add that line again.
anonymized-13171256
(@anonymized-13171256)
Version 2.19.2 has a permanent fix so that extra line is no longer necessary.
