Compatibility issues (a lot of extensions got deprecated and no longer are supported on 8.0), or shared hosting that still defaults to 7.4.I find it crazy only about 50% of customers run PHP8. That was released 3.5 years ago![]()
Compatibility issues (a lot of extensions got deprecated and no longer are supported on 8.0), or shared hosting that still defaults to 7.4.I find it crazy only about 50% of customers run PHP8. That was released 3.5 years ago![]()
... and the fact that XenForo < 2.2.15 told admins that the PHP version is "recommended" if it's > 7.2, so many XenForo admins might not have been aware that they are running (severely) outdated PHP versions and thus do not upgrade even though it might be as easy as changing some options in their hosting account settings / server control panel.Compatibility issues (a lot of extensions got deprecated and no longer are supported on 8.0), or shared hosting that still defaults to 7.4.
I donāt think youāve said exactly what error you received so difficult to say but recently a lot of logs generated by newer PHP versions have been deprecation notices which are only logged in debug mode.No, i mean the member that triggered the warning... does JohnQMember see it as a page fault while browsing the site, or is it just logged in ACP?
There may be a delay before changes are rolled out to the XenForo Community.Improve PHP 8.3 compatibility.
This was one of the fixed issues in the patch os all sorted.ErrorException: Template error: [E_WARNING] Increment on type bool has no effect, this will change in the next major version of PHP src/XF/BbCode/Renderer/Html.php:296
Companies tend to prefer stability over bleeding edge, especially since you don't know which bleeding edge technology is going to win out for the long run.Yeah I get that. But the funny part is, the internet is (perceived to be) on the forefront of bleeding edge tech...while, in the same time, the underlying engine is really really old.
Never understood that.
The life cycle up to PHP 5.6 was much better, with a longer span before EOL of security updates. There's a reason so many companies opt for the stability of Redhat and it's derivatives (Oracle Linux). Redhat's 10 year lifespan is very compelling, and if you get paid support it's extended to 15 years.
I just went up to PHP 8.3 and am now seeing this error. I seem to recall that Xenforo complains if I just edit a PHP file, is there an "official" way of implementing @PaulB 's change?
Not needed in 2.2.16+ or 2.3 RC2+.Do we need to use this fix or is the current version working on 8.2, 8.3?
We use essential cookies to make this site work, and optional cookies to enhance your experience.