@carlos-revilla – the PHP warning you note is something we saw as well, and is newly introduced with PHP 7.2.0. It’s something we’ll fix in an upcoming release. But that warning would never produce the broader symptoms you are seeing (500 error across site). I’ll be honest and say it’s not immediate obvious what would be causing that 500 error – it’s not the same bug, which was fixed; and it’s not something we’re duplicating. We’ll need to do more assessment to figure out what’s going on. We’ll have a dev looking at it today.
@karpin – “i tested and have the same problem” – can you clarify, are you seeing the PHP warning, the 500 errors, or both?
@aeternal – We’ll look into it.
@kent-brockman – First, I want to be clear, the issue here is not with our plugin. It is a bug in specific PHP versions. There are only two versions we know have the bug: 7.0.26, and 7.1.12. If you use any other 7.0.x or 7.1.x version of PHP, you should be fine. Our tests of of 7.2.0 are also fine, though obviously some users in this thread seem to be seeing something different.
]]>@karpin – can you confirm if you are using 7.2.0RC6 as well?
]]>phpinfo()
function to see what version you are using?
Here is a link to a file you can upload to your root directory then visit with your browser to see what information is being rendered by the phpinfo()
function: https://cloudup.com/c5PTkCRwjQw
Thanks!
– Cais.
]]>Also, the warning should be fixed ASAP, the error log size goes up the roof by the hour.
Regards
Carlos
]]>RC6
version as well; it is not being published as our recommendation is to roll back to an older version of the PHP 7.0.x or 7.1.x branches or (as a temporary measure) the last release of the PHP 5.6.x branch.
We are continuing to monitor this issue and do not want to flood the repository with numerous releases of our plugin as each RC and related versions are accounted for.
Thanks!
– Cais.
]]>