Known issues in 3.2.4

[Marc]

After the release of phpBB 3.2.4 we've noticed an issue that can affect users with extensions that employ the generate_text_for_display() function.
A fix for this can be found on Github and will be included in the 3.2.5 release:
https://github.com/phpbb/phpbb/pull/5448/files

[3Di]

Thumbs up.

[</Solidjeuh>]

Thank you for the fix

[P_I]

After the release of phpBB 3.2.4 we've noticed an issue that can affect users with extensions that employ the generate_text_for_display() function.
A fix for this can be found on Github and will be included in the 3.2.5 release:
https://github.com/phpbb/phpbb/pull/5448

Thanks for the quick update and fix.

Has anyone started to compile a list of extensions that employ this call or is it up the end users to scan their ext directory for calls to the function before deciding to update their boards to 3.2.4.

Added: So far I've found that the Board Rules extension makes this call.

[3Di]

Almost all of my recent and large extensions make use of it.

[david63]

My Privacy Policy and User Details extensions use this function.

[kasimi]

It only affects extensions that render rich text in the old style format used in phpBB 3.1.x and earlier. In phpBB 3.2.x the content is saved in the database as XML. When calling generate_text_for_display() with XML content, the bugged code is not called. So this only affects extensions written before 3.2.x that haven't migrated to the new XML format yet. For example, mChat 2.1.x uses the new XML format exclusively and therefore is not affected, while mChat 2.0.x is.

[bubbathegimp]

I downloaded the fix, but being a complete noob, I have no Idea of how to apply it...

[P_I]

It only affects extensions that render rich text in the old style format used in phpBB 3.1.x and earlier. In phpBB 3.2.x the content is saved in the database as XML. When calling generate_text_for_display() with XML content, the bugged code is not called. So this only affects extensions written before 3.2.x that haven't migrated to the new XML format yet. For example, mChat 2.1.x uses the new XML format exclusively and therefore is not affected, while mChat 2.0.x is.

Thanks for this additional information.

On the boards I'm involved with I've scanned for calls to generate_text_for_display() and so far only the Board Rules extension makes this call. Rather than dig further into the code and database, I've asked the extension developers if the extension is affected or not. Since there is a 3.2.x and 3.1.x version of the extension I'm guessing not but I'd rather have the developers confirm to be sure.

[invenio]

A fix for this can be found on Github and will be included in the 3.2.5 release:

Any estimate when we should see 3.2.5? If it's coming soon I would rather hold off on the update.

[rxu]

The issue also affects boards freshly converted from 2.0/3.0/3.1 to 3.2 (where text is not reparsed to XML yet).

[Swanny]

Can you update the 3.2.4 code package right now so people from now on doing the upgrade aren't affected? I haven't upgraded to 3.2.4 yet, I usually wait a few days after release in case there are known "bugs".

[Forex Station]

Can you update the 3.2.4 code package right now so people from now on doing the upgrade aren't affected? I haven't upgraded to 3.2.4 yet, I usually wait a few days after release in case there are known "bugs".

Same here haha. I get a bit nervous now with the updates. Even though we don't run many extensions we've had a couple of issues in the past like that one update that made it unable to upload attachments. Everyone on our forum had a fit

[Crizzo]

Can you update the 3.2.4 code package right now so people from now on doing the upgrade aren't affected? I haven't upgraded to 3.2.4 yet, I usually wait a few days after release in case there are known "bugs".

This would lead to two different versions with the same name/number and would lead to a mess.

[janus_zonstraal]

And offer a download with know errors will lead not to a mess?
Why not give it a other name as phpbb did in the past? phpbb3.2.4_fix