This site is intended to continue support for the legacy 2.x line of the phpBB2 bulletin board package. If you are a fan of phpBB2, please, by all means register, post, and help us out by offering your suggestions. We are primarily a community and support network. Our secondary goal is to provide a phpBB2 MOD Author and Styles area.

I started a repository on GitHub dedicated to the maintenance of phpBB 2. The repository is based on the version 2.0.23. It doesn't contain new features, but only bug fixes addressing the compatibility with recent versions of PHP (tested with PHP 7.0).

Nice project! Especially as OVH is starting to remove old php versions from their servers.

There's a way to unbust your mysqli layer without removing the query arrays (commit).
It doesn't matter in the slightest for basic phpbb cases, the object will just be casted to a boolean, but if you have advanced usages, it will start to break down.

Thank you for the feedback. I didn't want to use the cast to boolean because it didn't look safe. As I understand as soon as a page opens two resultsets simultaneously it's likely to break. But maybe this issue is moot anyway because the only method reading the saved row/rowset is sql_fetchfield(), and if I'm not mistaken it's never used. That's why I simply removed the fields. I'll keep in mind the SplObjectStorage trick if ever the optimization must be preserved for some mods.

Are there other fixes in Icy Phoenix that would be worth backporting to a vanilla phpBB 2?

Thank you for the feedback. I didn't want to use the cast to boolean because it didn't look safe. As I understand as soon as a page opens two resultsets simultaneously it's likely to break. But maybe this issue is moot anyway because the only method reading the saved row/rowset is sql_fetchfield(), and if I'm not mistaken it's never used. That's why I simply removed the fields. I'll keep in mind the SplObjectStorage trick if ever the optimization must be preserved for some mods.

You are right. However most phpBB2 boards are modded with cache and/or a "phpbbmyadmin"-style mod, and those tend to require that.

Quote:

Are there other fixes in Icy Phoenix that would be worth backporting to a vanilla phpBB 2?

Icy Phoenix is a hybrid phpBB2/phpBB3 codebase, taking things apart is Too Hardô.
I'm having troubles remembering what would effect phpBB2 itself, considering I have applied different fixes to my premod(ezarena), to IntegraMOD, and to Icy Phoenix over the years.

Also, since your repo is a fork, Github's codesearch is disabled...
In no specific order, I have those: (sorry if they don't actually matter in vanilla phpBB2)

Oh, MWE_001! Happy to see you here! It's funny, I started porting AD&R to integramod just this weekend, a few days ago ._________________Developer on EzArena, the ADR premod.
Developer on Icy Phoenix, the phpBB hybrid cms.
Developer on IntegraMOD, the full-featured premod.
Help me archive premods on github! (fixed for recent PHPs).

On a side note, I do have this version installed and have added a few odds and end mods to it like a Reg Code Mod to stop bots from registering (very simple awesome mod) and a couple index related mods and ACP related. So far no issues.

*EDIT*

Is this version the one that we were calling the unofficial 2.0.24 release years back?

I created a pull request on Git. One small change to the install.php file. I got to install on php 5 and php 7 up to 7.1.16 it fizzled out at 7.2.4 And I am positive I know how to fix that error on that version. Not sure how bad the errors get after the fact. I will try it and see.

As a recap, all I did was take the install.php file and where it was showing mysql4/5 2 times on the install instead of mysqli being an option, I fixed that. If the pull is accepted, it is good to go. If not, it can be gotten from my Git. I have to stress, my coding is sloppy at best. If you swing by my Git, use at your own Risk. I would rather the pull request be looked into and accepted or scrapped.