Development Discussion Board

This is a bad idea.
I understand not all is easy but to just close them and forget is a bad idea. As AmigoJack said there are a lot more, no reported because of nothing happened with the already reported.
Going back to core edits now.

Lot of changes in meta-data-manager.
Makes a lot of extensions not compatible

Events renamed in acp_extension

A nice question for you developers

Isn't it really possible to have a little system about naming config value's used by cron.
Again another cron task and again new names for it's time-values: update_hashes_last_cron

That should not be that difficult!

Update was smooth, without problems after clearing installer cache. Catchable fatal error: Argument 7 passed to phpbb\template\twig\environment::__construct() must be an instance of phpbb\event\dispatcher_interface, array given, called in /home/..../public_html/..../cache/installer/container_a5fcce7...

Avatar drivers 3.2 need a - '@upload_imagesize' in their config file as this isn't required in 3.1.
I was hoping for an answer about rmcgirr83 question earlier.

Until now for everything I have a workaround or switch except for the notifications.
So the way it is now I have to maintain two version if the extension uses the noti system.
What is better in the new noti system, it has to be in 3.2 without being compatible with 3.1?

It's a lot more David, uploading, using extensionmanager for example. Also a lot extensions are not in phpbb's cdb but running on phpbb for sure. Admins are using them on mass and it's bad they again have to switch only for a new version of phpbb. phpbb should offer a way to have them compatible and...

https://github.com/ForumHulp/Export-Import-Users can export your users in xml format.
From there you should be able to read them in Excel or whatever you want.

Thanks Pierre, I'm going to look at it. It's bad, if we, only for notifications, have to maintain two versions. The phpbb team should also think about all the work they generate with their versions in just so short time. Personnally I have much clients who stayed on 3.0, waiting 3.1 will be good and...

That's not the problem, i was more referring to constructor and service files notification.yml for example.