MichaelC wrote:Unlike updating from phpBB 2.0 to 3.0 which was a conversion, 3.0 to 3.1 is an update and therefore things such as the automatic file updater can be used. It would be exactly like an upgrade from 3.0.x to another 3.0.x release except the changeset is huge and should you have modifications you're highly likely to have conflicts & breakages which is why we recommend a fresh file set. The boards don't run along side each other. However, if you're running vanilla phpBB without any code changes then using the automatic updater should work fine for you.
MichaelC has stated and I am sure he is right, that using the AUTO UPDATER to go from 3.0.12 to 3.1 will go smoothly, if old mods (or styles) are "cleaned" beforehand with STK!
My question is, does STK add it's own set of tables/ fields/ columns to your database as it is installed? If so your 3.0.12 will not be vanilla, even after your old mods (or styles) are "cleaned" beforehand with STK because STK's own database variables are now present and quite obviously NOT removed otherwise STK could not work.
OR is STK working without adding anything to the phpBB database?
MichaelC wrote:Some MODs might actually continue to work on 3.1 however the vast majority would stop working and require considerable efforts to use on 3.1. Essentially purging your files and going back to a vanilla version of phpBB gives you a clean slate and, with extensions, file conflicts when updating should become a thing of the past as the majority of people using >= 3.1.0 will be using a vanilla set of files (by that I mean additional files may be present but no file modifications) but your DB will still have remanants of old MODs that could cause problems in future.
I believe the database cleaner in STK strips everything non-vanilla (columns/tables) out so that could be an option should you wish to 'clean up' your database.