Hi acri, it should work on PHP 5.2+. There were only minor changes in this update, so it shouldn’t break your content, although it might affect the output if you’re using an object cache.
– Brady
help!! The plug-in revision seems to be causing a major internal server error in the site I just launched today. I upgraded it before launching. The site was working fine on the subdomain … now all is working EXCEPT the homepage that uses this plug-in in the marquis slider.
forgot to include the link:
Thread Starter
acri
(@acri)
Hi Brady,]
Thanks for the super quick reply.
Just upgraded server to php 5.4.
Still using version SIW 4.0.
I have not tested the plugin again after the php upgrade based on your previous compatibility info.
I believe there is contention (version 4.0.10) with a slider plugin on my site. (Using ithemes slideshow version 3.0.0.) There may be a common relationship going with the marquis slider not working for xuzi as well .
Hi acri, it may indeed be a bug in the plugin. Would you be comfortable manually upgrading to a development version to test it out for me? If so, you can grab the version with a bug fix here: https://github.com/blazersix/simple-image-widget/archive/develop.zip
Thanks,
Brady
I also receive a 500 server error after updating 🙁
version 4.0.1, WP 3.9.1
Hi folks,
I just released an update that should resolve these issues. Let me know if y’all are still encountering any problems after updating to 4.0.2.
Thanks,
Brady
Thread Starter
acri
(@acri)
Thanks for your continued support. It is developers like you that continue to make this a great WP community. Your hard work is appreciated.
Have any idea that you would care to share about what happened? I am always seeking to deepen my knowledge base. Again BIG thank you.
Thread Starter
acri
(@acri)
I will test 4.0.2 in my MS Dev site to see what happens. Its is huge over 40g and growing – no I am not a spammer lol.
Thanks acri. It was a silly mistake on my part while trying to maintain backwards compatibility.
WordPress 3.9 added widget support in the Customizer, but it can cause issues with object caching if not implemented properly. While adding support, I referenced the parent class the wrong way. You can see the change in this commit: https://github.com/blazersix/simple-image-widget/commit/06c4ed48b00da6218a493f8a1d0b0739112d40f2
Cheers,
Brady
Thread Starter
acri
(@acri)
Well it makes sense to me it always has to be the parent’s fault. Just like in real life. 🙂
Thanks for explaining. I am always in a quandary as to what makes things break.
