actually, I get errors whenever I try to save anything after updating. even if I haven’t changed anything
Warning: Invalid argument supplied for foreach() in /home/smartg2/public_html/wp-content/plugins/testimonials-widget/lib/class-settings-testimonials-widget.php on line 874
Warning: Cannot modify header information – headers already sent by (output started at /home/smartg2/public_html/wp-content/plugins/testimonials-widget/lib/class-settings-testimonials-widget.php:874) in /home/smartg2/public_html/wp-includes/pluggable.php on line 876
Ick…
Could you please check the Reset tab > reset box and then save?
Then try to set new options?
Hey, That did not work, I still get the Warning messages and now the widget is showing as a white box.
We have purchased the Premium version under peter @smarterwebsites.com.au. Should I set you up as a user?
Can you please send me an admin login via http://aihr.us/contact-aihrus/?
Hi, How this going? This site is going live today.
If its not able to be fixed soon we will need to swap widgets around so that the site looks great when its live.
If we swap widgets, will this effect what you are doing?
Please, next time you have a deadline, let the person you’re requesting help from know it.
I’ve looked into this and it seems there’s a server configuration or plugin conflict issue regarding the grabbing and serialization of the importexport option. It’ll take more debugging on your particular site to figure out why.
In the meantime, the Testimonials Widget widget instance does work regarding setting of options and displaying on the front end.
I’ve added the following to your child theme’s functions.php which disables the troublesome setting for now. This way, you can continue to set global settings and then create widget instances which inherit them.
add_filter( 'testimonials_widget_settings', 'my_testimonials_widget_settings' );
function my_testimonials_widget_settings( $settings ) {
unset( $settings['importexport'] );
return $settings;
}
Do let me know if you need something further.
Thank you so much for your help.
I was unaware of the urgency until just before I wrote it on here.
I thought go live was next week.
I will remember this for next time
Not a problem. I’ve also put into the next release a check to ensure this problem won’t happen in the future. It shouldn’t have in the first place. But alas code does as it was coded to do.
Hi Michael,
The plugin now has a white background?? Any suggestions?
Sorry… I’ve got the memory leak fixed. 2.12.1 will be coming out shortly have added a new test to try and prevent similar issues.
