Staff member
Apr 11, 2011

It looks like PHP will include a fix for that bug in PHP versions 7.1.13 and 7.0.27. I can open an internal request to see if we can get this bug patched ahead of time, but I currently see no other reports of this causing widespread errors (it looks to mostly affect WordPress Gallery plugin users). Could you elaborate more on the effect this is having on your websites? Note in the meantime, one potential workaround is to assign the affected accounts a different version of PHP (e.g. PHP 5.6).

Thank you.

Note: Edited to remove reference to PHP 7.2 as a workaround. PHP is including the fix for the 7.2 branch in version 7.2.1.
Last edited:


Dec 1, 2017
cPanel Access Level
Root Administrator
I see that PHP 7.2.0 has been distributed now. Thank you for that. It looks like, however, that the issue still persists on 7.2.0. I'm surprised that there hasn't been more of an uproar, to be honest. It's true that the problem seems to be with primarily with NextGen Gallery users. That plugin has 1+ million active installs. I use it a lot on many of my client's websites. Sure, we can roll back to 5.6 but the performance hit doesn't seem worth it.

The NextGen folks, to their credit, have it made so that if affected PHP versions are detected a warning message is displayed and the plugin is disabled. You only see the shortcode instead of getting a server error. Apparently, their code for the plugin makes heavy use of some PHP "magic method" that is not easily fixed with a patch on their end. So we are at the mercy of getting a patch quickly rolled out by the PHP devs.

I know you guys at cPanel don't have anything to do with this but if you do have any pull or sway with the PHP team, whatever can be done to expedite a patch would be much appreciated.