fatal error

I’m running 5.2, updated the plug in and it’s working. Thanks for all your work!

Awesome! Glad to hear it. This is the 3rd report the 3.7.7 did the trick. Sounds like the new release is “good to go”.

I am glad to hear that the new release is “good to go”, but I am disappointed that the developer released an upgrade without testing on PHP 5.2. Your plugin requirements state:
PHP 5.2.4+ (same as WordPress 3.3.2)
WordPress: 3.3.2+

As such, all releases should be tested for PHP 5.2.4, especially since there are major changes between PHP 5.2 and 5.3.

@sjwattok – I test on the development system and test system I have setup. I even run a set of automated test with Selenium which is FAR MORE than 90% of the plugins out there. I already spend 8 hours testing every release and for a free plugin I feel that is more than enough.

I’ve asked time & time again for beta testers. ONE person is on the list and is NOT on PHP 5.2 and did not even test the latest release.

The ONLY way the plugin will ever be what I consider “well tested” is if the community gets involved, gets the beta release, and tests it fully. As a single person doing ALL of the development, documentation, and support there are simply not enough hours in the day. Especially considering how few people donate ($35 in over 2 years) or purchase premium add-ons.

Releases go out about once/week and take a full day to test thoroughly. If you wish to donate your time and help test Store Locator Plus release, I’m glad to have you.

@sjwattok – Also, if you wonder why my development system is on 5.3 and NOT 5.2.4 it is because I have to do other projects to feed my family. 5.2.X has numerous memory leaks and even a SEGFAULT that produces unstable and far inferior results on those other projects.

Some of those memory leaks creep up in WordPress plugins more often than you realize. Ever wonder why some WordPress sites run out of memory when certain plugins are installed? Read the PHP 5.3.X release notes and you will find DOZENS of memory leaks and security issues being addressed.

Yes, WordPress requires 5.2.4 and they don’t like to change the requirement if they can help it. Makes sense. PHP does some AWFUL things when they release new versions (talk about testing releases & backwards compatibility issues!), but anyone that CAN run PHP 5.3.X should do so. Just make sure you test first so you know none of your plugins break.

BTW, that is another good point. You cannot simply test 5.2.4. For a full test you must test 5.2.X and 5.3.X. Since I only have enough time to do ONE I choose 5.3 for the reasons stated previously.

No, not a perfect solution but software is NEVER perfect. Just look at the 300,000+ bugs already reported in Windows 8, and they have a MUCH bigger test team and much longer release cycle. Or closer to home… WordPress 3.5 and their known bug/issues list.

I hope this sheds some light on what I do and why.

– L

FYI, my company has purchased pro-pack and you can be sure I will be testing all plugin upgrades (not just store locator) prior to promoting them to my production website. For the time being my test and prodution environments are 5.2.5 and 5.2.13 respectively. I would be glad to get beta releases for testing on these platforms.

Here is the beta release sign-up link:
https://eepurl.com/pqZrz

I was sending emails with the beta releases attached until I realized “that one guy” (literally) was not even opening 90% of these and I never received any test issues even after a notable bug in one release got by me.

If you are wondering why my production system is 5.2.13… This is my first WordPress site, I have other sites on this server utilizing other php software that have not all been tested and verified on PHP 5.3

@sjwattok – I get it. Not everyone can upgrade to 5.3.

I also understand why some people would think “requirement is 5.2.4, why doesn’t he test on that” so I felt an explanation is in order. Things are never as simple or cut & dried as people first imagine.