[RFC] Remove phpBB 2 Convertor

[DavidIQ]

On topic: I don't think we need 2.0 => 3.1 conversion.

I completely agree. If there are users still on 2.0 then they can upgrade to 3.0 first and then to 3.1. Let's cut out some of the excess fat.

[DarkBeing]

On topic: I don't think we need 2.0 => 3.1 conversion.

I completely agree. If there are users still on 2.0 then they can upgrade to 3.0 first and then to 3.1. Let's cut out some of the excess fat.

+1

[Erik Frèrejean]

We still see support topics every week about converting from phpBB2. If it works, I would suggest leaving it. If it is sufficiently broken, then I wouldn't put much effort into fixing it.

That

[Oleg]

Since testing the converter requires a phpbb 2 board, if anyone wants to see it remain part of phpbb 3.1 they need to check if it is still working.

If there is no one who cares enough to test the converter, we should probably remove it.

Note that there is already a PR to remove it. If there are no volunteers who would test it I will merge that PR at some point.

[imkingdavid]

IMO, it makes no sense to include a 2.0->3.0 converter in the 3.1 core package. If it were a 2.0->3.1 converter, then sure. If someone wants to convert from 2.0->3.1, they need to download 3.0 anyway to convert to that, and then upgrade to 3.1 from 3.0.

[Noxwizard]

If there is no one who cares enough to test the converter, we should probably remove it.

One simply needs to ask. The only issue with the convertor in 3.1 right now is that the search systems are now prefixed with phpbb_search_. The file name differs from the class name, so instantiating the class fails on line 755. This could be remedied by pre-pending $search_type with the prefix. (Edit, this has been fixed by PHPBB3-10637) Other than that, it doesn't appear to have any issues converting everything.

IMO, it makes no sense to include a 2.0->3.0 converter in the 3.1 core package. If it were a 2.0->3.1 converter, then sure. If someone wants to convert from 2.0->3.1, they need to download 3.0 anyway to convert to that, and then upgrade to 3.1 from 3.0.

It wouldn't go to 3.0, it would be going 3.1. Unless there are significant database structure changes, the current convertor will most likely continue to work with 3.1.

[MichaelC]

The converter will still be available, just not in the default package, similar to how subsilver 2 will be. Available but not in the main package.