I was told that the gallery was indeed a MOD or extension which would be made incompatible after updating to 3.2. php_gallery also shows up in the STK Database Cleaner list if this clarifies anything.Where did you read to use the STK??
And there are no mods in 3.1.x so don't understand what you are doing.
The SQL error appears after I attempt to use STK to remove MODs or what's classified as "Extra" (everything's classified as extra ), no updates have been applied as of yet because I can't/don't know how to remove the MODs. Im still at that step.The sql error seems to suggests that an update was tried, and it failed at a certain point.
If you tried to go back to the pre-update situation, then reuploading the old files form a backup isn't sufficient. That only restores the files but the database is not the 3.0.12 database anymore but has been changed during the update.
So you'll need to restore a database backup.
I was not given a mod-less backup. What I have is what I've got: A 3.0.12 board with mods on it.The mods that were installed ... are the installation files in the files backup you have. If not, can you find the installation files on phpBB.com? (those should provide enough information to undo all changes.
You did nothing on your board for ten years en giving us now the wrong info about your version, but it is still phpbb faultIt appears that user friendliness is not a strong suit in phpbb. It's like a maze.
This is confusing:
Code: Select all
What is the most recent action performed on your board? Update from a previous version of phpBB3
There will certainly be some database changes as data was stored.Vard wrote: ↑Sun Dec 29, 2019 10:43 amAs I'm aware, at least according to the update tutorial, I believe I'm going to have to delete all of this anyway. My concern is do I need to make any changes which would see the removal of items from the DB in order for everything to be clear for the update? And if so, what should I look up in relation to the mods I have installed to ensure that everything is cleared out accordingly?
I'll worry about the gallery later; I have it backed up and it's not my primary concern. I'd love if someone could do the update for me, although I'm a little concerned that the issues I'm having seem to elude support just as much as they elude me.Don't remove the Gallery folder!!!
First read this:
https://www.phpbb.com/customise/db/exte ... y/faq/2181
And maybe it is better to ask somebody here to do the update for you, someone who is more experience with phpbb and the Gallery extension.
So plainly, I uninstall all the items listed under AUTOMOD and then I need to find some alternative method for removing what's under MODs, yes?But, you have the automod tab in your printscreen so that module was added (and probably more), perhaps permissions were added. These extras have to be removed before starting the update.
AutoMod was an instrument for applying the file changes for a modification. Database changes still had to be performed manually (although I have to admit that it's been so long ago that perhaps I missed a later version which did apply database changes - I doubt it though).
Alright, I'm able to see that mod files are located in /store/mods. This gives me a much better idea of what's going on, but as to ascertaining what's been modified in the DB, you've lost me completely. There doesn't seem to be anything contained within this plethora of folders which coherently indicates to me what's been modified within the database or why, unless (and likely so) it is located in some other hidden chamber or detailed through various levels of crypsis.However, you probably have a directory mod inside your /store and IIRC that is where the mod installation files were kept (I think) and if those files are still there, the instructions regarding installation, including database changes, are there so that should allow undoing all database changes (manually)
The STK can also be used for that (and is probably safer than manual database editing) but I'm not uptodate with the latest version and I have no idea whether it delivers a totally clean database.
Your best bet is to use the STK on the database (but keep a complete backup: files and database) before making any changes.
Also realise that after using the STK, the changes necessary for the mods to work are not present anymore, and if you use your board with the modded files, you will get errors (so testing should be done with clean 3.0.12 files).
I do recommend testing at that stage because there's no point in trying to upgrade a database which already gives errors. And since you're using 3.0.12, you might as well update to 3.0.14 (an extra test - if it passes you're probably set to go).