Forum issue with ordered lists (phpBB bug?)

[Hated Moron]

Seemingly, if you attempt to include an ordered list ([list=1]) in a forum post, it will catastrophically crash the server and result in an HTTP ERROR 500.

As far as I can tell this is a bug in phpBB 3.3.11 (the latest version) to which this forum was recently updated by DDRM. phpBB 3.3.11 officially requires PHP 7.2 or later (this server is running 7.4) but the code for handling an ordered list calls a function which is only in PHP 8!

I've reported this at the phpBB forum, but for the time being avoid the use of ordered lists.

[Hated Moron]

I've reported this at the phpBB forum, but for the time being avoid the use of ordered lists.

Unsurprisingly this doesn't just affect new posts, if you attempt to view any post containing an ordered list (for example one of my release announcements) it will also crash the server! Hopefully a fix will be released soon.

[Hated Moron]

I've reported this at the phpBB forum, but for the time being avoid the use of ordered lists.

I was advised at the phpBB forum that this should be resolved by deleting the cache directory, and that does indeed seem to be the case.

[DDRM]

Hmm. I think that was in the installation instructions. I thought I'd done it, but maybe not - or maybe I did it and then overwrote it during the install...

Anyway, glad it is resolved...

D

[Hated Moron]

Hmm. I think that was in the installation instructions. I thought I'd done it, but maybe not - or maybe I did it and then overwrote it during the install...

You did the installation when the forum was still at bbcbasic.co.uk, surely. Indeed wasn't that the whole point, to update it to the latest version in the hope that it would solve the problems that Svein and Darren had encountered when they tried to move it?

In which case I expect the issue arose when I moved it to the new bbcbasic.net host; probably the cache should have been cleared again but wasn't. Moving it without any admin access, whilst it works, is riskier; it may well be that clearing the cache (which is usually an admin operation) got missed as a result.