Development Discussion Board

We've had a similar issue (implemented slugs/SEO and additional filter arguments in the URL that need to be preserved). We also replaced the "start" URL argument with a "page" one, to be compatible with our old forum. This is how we did it:
Implement your own "pagination" service in your extension ...

making this core in 3.2 would be great.
this is the ideal functionality for us:
- ability to enable/disable feature on a forum by forum basis
- implement user permission (to allow some users to like, default to all roles except read-only)
- option somewhere to enable/disable down votes
- display ...

Just a heads up, but we've actually developed such extension. We're migrating from VB, so this is a feature we really needed.
It can be enabled on a forum by forum basis; implements a custom specific user permission, and allows basic un/thanking functionality with stats. It will be released fairly ...

This thread isn't actually relevant anymore since the changes we requested were eventually made some time after beta 3.

bump, would be very interested to hear opinions on last post

A while ago I noticed forum_parents field was being populated fine, so I wrote some code to make use of it when available, but recently (tried a few different nightlies) that this field is no longer being populated with any data.

I tried creating a new category, forum, and moving forums around and ...

Sure, keep the syntax for 3.1, but 3.2 really should try to move things forwards.

It shouldn't be difficult to write a 3.0 to twig conversion tool that style authors can use.

We did exactly that. And was strongly rejected. The event included "modify template" in its name, yet the array was assigned to the template before the event was called. Our suggestion to fix that was denied claiming we should use "global $template". We found a way around our initial request, but ...

Using alter block with the breadcrumbs for example is cumbersome. It was much easier to just destroy the entire "navlinks" block and recreate it.

Mentioned this before, but: events should really be called with template array data before it is assigned to the template.

Not sure why you'd want to preserve phpbb's ancient template syntax. Modern IDEs support twig, and many projects are moving to twig (drupal, et al), so the more standard syntax it is kept the better.