Release highlights
New Features
Events - More events have been added to the template and the php core
Notable Bug Fixes
Version check of extensions - File caching of extensions' version check file doesn't work
Fix links from /board - Append page name to base url if it doesn't contain it ...
Search found 737 matches
- Fri Apr 10, 2015 7:48 am
- Forum: [3.x] Discussion
- Topic: phpBB 3.1.4 RC2 released
- Replies: 27
- Views: 51675
- Thu Apr 09, 2015 6:03 pm
- Forum: [3.x] Discussion
- Topic: Releasing 3.1.4
- Replies: 8
- Views: 26876
Re: Releasing 3.1.4
I'm sorry, seems like we didn't get them all in this time. But 3.1.5 should be good I guessbrunoais wrote:@nickvergessen Will my events for 3.1.4 be merged?
- Mon Apr 06, 2015 10:19 am
- Forum: [3.x] Discussion
- Topic: Releasing 3.1.4
- Replies: 8
- Views: 26876
Re: Releasing 3.1.4
Sorry this took a little longer, because I moved in the meantime, then the internet provider messed up things, so we are kind of late.
3.1.4 has been frozen on github now, everything new should go into 3.1.5, the plan is to do the RC today, tomorrow or the day after,
depending on the availabilities ...
3.1.4 has been frozen on github now, everything new should go into 3.1.5, the plan is to do the RC today, tomorrow or the day after,
depending on the availabilities ...
- Mon Mar 02, 2015 9:30 pm
- Forum: [3.x] Discussion
- Topic: Hide avatar image in notifications menu
- Replies: 2
- Views: 5890
Re: Hide avatar image in notifications menu
I think it should just follow the existing option
- Sat Feb 28, 2015 12:39 pm
- Forum: [3.x] Discussion
- Topic: Extending DBAL query builder for boolean generation
- Replies: 10
- Views: 14529
Re: Extending DBAL query builder for boolean generation
I think doing thinks like this is a step in the right direction.
Maybe you can extract the sql_build_query method into a new class because otherwise that code will just get even bigger.
Maybe you can extract the sql_build_query method into a new class because otherwise that code will just get even bigger.
- Tue Feb 24, 2015 10:00 pm
- Forum: [3.x] Discussion
- Topic: Releasing 3.1.4
- Replies: 8
- Views: 26876
Releasing 3.1.4
Todo List for 3.1.4
Estimated release date: March 21, 2015
Freeze date: March 13, 2015 - Afterwards only critical blockers
Make sure phpBB/docs/AUTHORS is up to date ✔
Make sure Contributors have their ranks ✔
Make sure all reports in the security tracker are closed or invalid ...
Estimated release date: March 21, 2015
Freeze date: March 13, 2015 - Afterwards only critical blockers
Make sure phpBB/docs/AUTHORS is up to date ✔
Make sure Contributors have their ranks ✔
Make sure all reports in the security tracker are closed or invalid ...
- Tue Feb 24, 2015 7:56 pm
- Forum: [3.x][Archive] RFCs
- Topic: [RFC] composer phpBB versions and installation
- Replies: 16
- Views: 42747
- Tue Feb 24, 2015 11:30 am
- Forum: [3.x][Archive] RFCs
- Topic: [RFC] composer phpBB versions and installation
- Replies: 16
- Views: 42747
Re: [RFC] composer phpBB versions and installation
That's the plan, we just didn't manage to finish that in time for 3.1RMcGirr83 wrote:could we not disable the enable button in the ACP if the phpBB version in use doesn't meet the requirements of the soft-require?
- Wed Feb 18, 2015 11:10 pm
- Forum: General Development Discussion
- Topic: Git development branches
- Replies: 23
- Views: 71435
Re: Git development branches
we will merge PRs that go against develop* branches into the respective 3.*.x branches.
develop is now called master.
The develop branches are abandoned and will not be kept in sync.
They will also be dropped as soon as the PRs against them are merged.
develop is now called master.
The develop branches are abandoned and will not be kept in sync.
They will also be dropped as soon as the PRs against them are merged.
- Tue Feb 17, 2015 6:27 pm
- Forum: General Development Discussion
- Topic: Git development branches
- Replies: 23
- Views: 71435
Re: Git development branches
The new branches have been created.
Please send new Pull Request to the new branches. Existing PRs can be kept, to avoid duplication.
Once most of the PRs are merged, we will delete the develop* branches.
Please send new Pull Request to the new branches. Existing PRs can be kept, to avoid duplication.
Once most of the PRs are merged, we will delete the develop* branches.