This is probably related to a recent PHP update, the error occurs after updating from PHP 7.0.25 to 7.0.26 or PHP 7.1.11 to 7.1.12. PHP crashes with a segmentation fault, the PHP error log shows the following error messsage:
[25-Nov-2017 10:35:15 UTC] PHP Fatal error: Couldn't execute method C_Display_Type::__get in Unknown on line 0
This could be a bug in PHP or NextGen, a temporary solution would be to switch to an older PHP version like 5.6 until the issue is resolved.
My webhoster switch back PHP to 7.0.25 and now its working again. To the NGG developer Team: Hope you can fix this soon, because this bug is relevant to all PHP 7.0 and 7.1 users with an actual PHP Version. My hoster inform the PHP developer too.
-
This reply was modified 8 years, 6 months ago by
ODAK71.
-
This reply was modified 8 years, 6 months ago by ODAK71.
Downgrading PHP version to 7.0.25 temporarily handles this problem indeed, but I agree that the NGG developer Team (and maybe the PHP developers) has to solve this as downgrading vital packages isn’t a solid solution.
Plugin Contributor
Imagely
(@imagely)
@christianebuddy – We are investigating these reports.
… et al., please continue to submit/create separate topics for each of your sites, we would appreciate the differentiations.
Thanks!
– Cais.
Hi,
We are running into the same problem.
Our provider will not downgrade to PHP 7.0.25
So please provide a quick solution.
Cheers,
KeesD
Same problem here. My site was on PHP 5.4… I just upgraded to 5.6, we’ll see if this helps temporarily.
-
This reply was modified 8 years, 6 months ago by
silico26.
Plugin Contributor
Imagely
(@imagely)
@christianebuddy, @odak71, @keesd, and @silico26 – NextGEN Gallery makes extensive use of PHP Magic Methods to encapsulate our various data models.
The latest releases of PHP, versions 7.1.12 and 7.0.26, include some changes how reference counting of strings is conducted in the __get() magic method that is breaking NextGEN and various WordPress sites. The problem is reproducible using standard PHP code, where both a subclass and it’s parent are using the __get() magic method, and are defined to return-by-reference.
A patch and commit has been accepted into the PHP source code repository but hasn’t yet been released or distributed.
More information may be found here, specifically in the comments: https://bugs.php.net/bug.php?id=75573
We are recommending, during this period where PHP has not been patched and released, to roll back if possible to an older version of PHP. We do apologize if you are not able to roll back to a non-broken version of PHP and we may not be able to address this in a timely fashion before a newer PHP version is released that addresses this issue.
If the concern you are having is not directly related to this PHP version problem, please start your own topic so we can try to help you with your specific issue on your specific site.
See https://make.ww.wp.xz.cn/support/handbook/forum-welcome/#post-in-the-best-place
Thanks!
– Cais.
@imagely Tnx for all the info and explanation. Looks like the PHP team hasn’t solved this problem yet. Keeping php downgraded for now still is the solution
Plugin Contributor
Imagely
(@imagely)
@christianebuddy – We expect the PHP 7.2.0 release version to be correctly handling things now, are you not seeing that as the case; or, do you not have access to that latest release of PHP?
– Cais.
The php 7.2 release has been released just now on 30th of November 2017 and is not included in the major OS-es (Ubuntu, Debian, CentOS…) stable releases yet.
Maybe it’s an option of fixing this error on nextgen-gallery plugin itself as long as php 7.2 is not mainstream in the major distributions?
Plugin Contributor
Imagely
(@imagely)
@christianebuddy – Currently, if a problematic version of PHP is being used (that we are aware of) NextGEN Gallery’s functionality is essentially not available aside from what is needed to display a warning message to that effect.
Thanks!
– Cais.
Well I certainly would not call a stable PHP version in mainstream distributions “problematic” Millions of people are using this version … What about some workaround to give Nextgen’s functionality to all those people….
Plugin Contributor
Imagely
(@imagely)
@christianebuddy – We are focusing all of our developers on this currently.
– Cais.
Plugin Contributor
Imagely
(@imagely)
@christianebuddy – Thanks! It’s proving to be quite challenging to account for all possibilities.
– Cais.
