Fixed PHP 8.3 compatibility patch

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.
 
1714166881203.webp


Michael Scott Grimace GIF
 
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.
... 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.

But luckily this has been addressed now :)
 
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?
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.
 
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
 
Thank you for reporting this issue, it has now been resolved. We are aiming to include any changes that have been made in a future XF release (2.3.0 Beta 6).

Change log:
Improve PHP 8.3 compatibility.
There may be a delay before changes are rolled out to the XenForo Community.
 
I am receiving more than 600 errors similar to this:

  • 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
As 2.3 may take time, is there a temporary fix/patch for 2.2.15 to stop this error? @Chris D
 
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.
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.

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.

The short 3-year support cycles since PHP 7.0 is insane.
 
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.

Yes, unfortunately this kind of immature banana software (php >7.x) is becoming more and more widespread and users are left behind.
Companies should have to keep security stable as long as the respective software is used.
 
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?
 
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?

I believe you will see the release of XenForo 2.2.16 this week (maybe next), which has the full PHP 8.3 patch incorporated. If you can wait.

Otherwise, you can make the edit yourself now and deal with slight annoyance of XenForo warning you of the edited file until 2.2.16 is released.
 
Back
Top Bottom