General discussion of development ideas and the approaches taken in the 3.x branch of phpBB. The current feature release of phpBB 3 is 3.3/Proteus.
Forum rules Please do not post support questions regarding installing, updating, or upgrading phpBB 3.3.x. If you need support for phpBB 3.3.x please visit the 3.3.x Support Forum on phpbb.com.
If you have questions regarding writing extensions please post in Extension Writers Discussion to receive proper guidance from our staff and community.
Version check supports branches - Both the phpBB and extension version check now support branches
Enhancements
Updated dependencies - Updated dependencies to latest versions, e.g. Symfony, Twig
Notable changes
High-res icons in prosilver - prosilver is now using higher res images for the imageset icons
Notable bug fixes
Invalid constructor in FTP file updater - The invalid constructor prevented using the FTP file updater
Multiple issues in text formatter - This caused e.g. issues with some smilies and BBCodes
Fix migration dependency preventing update from before phpBB 3.0.6 - Migration to 3.2.0 didn't check dependency correctly for upgrades from pre 3.0.6 versions
The packages can be downloaded from our package archive. Please test the packages to extend, so we can have a stable final release.
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_a5fcce7799cdc15359366537322eb9a2.php on line 1967 and defined in /home/..../public_html/...../install/update/new/phpbb/template/twig/environment.php on line 62
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
While the metadata manager contains changes, this should not affect extensions. If you think this caused extensions to be no longer compatible, then please elaborate on what changed and causes issues for you.
I think we overlooked the event already being part of a previous release and therefore didn't object to the renaming. That is something that can be undone to prevent potential issues for extension authors.
The only non-bc change in Metadata Mgr is the move of the output_metadata_to_template function to acp_extension, where it belongs. And yes, this affects your "upload" extension.
If you find any other non-bc compatible change, it is unintended, and should be fixed.