Yes, I found a first solution here: viewtopic.php?p=15381596#p15381426
Paradoxically a post that deserves a core based 'like'. Stereotyping (inaccurately) people because of their views is unhelpful here and in their moderator capacity. I've hosted many phpBB forums for over 15 years and don't do social media but if I was starting a new forum would probably go Discourse. However, swapping large existing forums to Discourse would be too much of a challenge.
But you can use Emoji in 3.2.8 und 3.2.9 as well within the posts and you cannot disable this. Why is this now a problem?
I don't get want you mean. I don't know, if 3.2.9 will be the last 3.2.x release, but it's content and bugfixes are in 3.3.0 as well.
Emoji support came together with phpBB 3.2.0. So how do you solve this "problem" at the moment in your board?
https://bamboo.phpbb.com/browse/PHPBB3-DD32-648/commit
Code: Select all
Code commits
phpBB Rhea
Marc
Marc 3 days ago 790e77de019099b977593fa7f78ac82b3bda7365
[3.2.x] Update version numbers to 3.2.10-dev
build/build.xml (version 790e77de019099b977593fa7f78ac82b3bda7365)
phpBB/includes/constants.php (version 790e77de019099b977593fa7f78ac82b3bda7365)
phpBB/install/schemas/schema_data.sql (version 790e77de019099b977593fa7f78ac82b3bda7365)
Thank you, this is quite reassuring as my biggest worry is whether my extensions will all be compatible with this upgrade when it's released.P_I wrote: ↑Mon Dec 30, 2019 5:09 am Overall it took about 5 minutes to complete successfully and my sanity testing shows everything seems to be functioning as expected.
After sanity testing, I changed to the PHP 7.3 repository, verified that ACP->General showed PHP version 7.3.13 and repeated my sanity testing. All appears OK.
One of the reasons would be the change in coding guidelines (hence the yml check (by david63 IIRC), which test the validity of certain syntax. If it passes it doesn't yet imply that the extension is 3.3 compatible, however if it doesn't pass the test then it's certainly not compatible.BlackPandaBear wrote: ↑Mon Dec 30, 2019 9:50 am Could someone with more knowledge on here explain why an extension could become incompatible after upgrading from 3.2.8 to 3.3?