Add New > Blank Screen

That’s really good of them to get onto fixing it so quickly.

I’m just curious: is there any particular reason you’re anxious to raise the minimum PHP version, now that this issue is resolved?

@bungeshea – Simply because you don’t know what you don’t know. Raising the version would eliminate this type of problem for other plugins that are lurking out there. Why go through this every time?

Also, raising the PHP version increases security overall, right? (if not, happy to be corrected)

Finally, I’m a big proponent of raising standards, and raising awareness in the WP community at large. It’s time to leave PHP 5.2, 5.3, and 5.4 completely behind. It really is. PHP 7 is the official *recommended* version of PHP for WordPress, and they have already put a warning in place for using lower PHP versions, like 5.24.

–> https://d.pr/i/rJqt

https://www.ads-software.com/about/requirements/

But it’s entirely up to you my friend. I’m certainly not *clamoring* for it or anything. ??

Ah, that’s what I was wondering. Yes, implementing namespaces would help prevent something like this from happening in future – though I wouldn’t necessarily say the likelihood of that happening is that significant, it still is something to consider.

Raising the minimum version doesn’t necessarily ‘increase security’. All it would really do is allow me to use features that are only present in newer versions of PHP. It’s updating the version of PHP that is run on the server that would increase security, which doesn’t have a lot to do with the plugin.

And I completely agree with you, raising standards is definitely something to go for. It’s why most of my other plugins aren’t supported on PHP 5.2 – I have just held off a little longer with this one given that it has a fair few users and is more of a complicated product. It does feel like this might be a good time to make the change, so I’ll add it to the roadmap for when I’m looking to make major changes to the plugin.

Thanks for your thoughts – I was looking to see if there were reasons that I wasn’t thinking of. It’s good to get a second opinion on things like this ??

Awesome man… We’re on the same page, all around.

And thanks for the clarification about PHP on the server vs. what you’re coding the plugin itself with. It’s an important distinction.

I think it’s a good decision though, and will help to raise awareness even more…

Just make sure you give ample and good warnings, and put some instructions in place for common hosts, like: You can contact GoDaddy, BlueHost, HostGator, etc. etc. etc. here… and link to their support areas.

You *will* run into problems though, but you know this, as a seasoned WP developer.

Thanks for what you do, and for your help in this thread. It’s noticed and greatly appreciated.

Keep rocking man!

~ Chris M.