The database cleaner does not remove things that were standard n the version it is running on, as those modules are.wedgef5 wrote: ↑Wed Jan 31, 2018 2:44 amOK...I think that's the last of the 3.0.x artifacts.
I did run the database cleaner, and I said "Yes" to everything it wanted to do, nor did I alter any of the default choices. I don't know what went awry with it.
Thanks again for your patient assistance!
Thanks, that of course sounds logical and reasonable. What I recall of that process when I went through it was "when I uninstalled all styles except proSilver", although the styles list is now empty as expected, the templates, themes and imagesets lists were still populated with other entries besides just "proSilver".
That's a known issue with 3.2, should be solved with the upcoming 3.2.3
Thanks for the confirmation. I was able to confirm at my end that even if I did explicitly go through and delete all of the orphaned "Templates", "Themes" and "Imagesets" from my 3.0.14 board -- so that "proSilver" was the ONLY installed and active item in ALL of these lists -- the ACP_STYLE_COMPONENTS section still showed up in the resulting 3.2.2 installation.
Meaning if your 3.2.x board ends up in this state, you have to just go manually remove the ACP_STYLE_COMPONENTS module and all its child modules (Templates, Themes and ACP_IMAGESETS, if present) because they're not supposed to still be there.Lumpy Burgertushie wrote: ↑Tue Jan 30, 2018 12:34 amgo into the admin panel, system tab, module management, administration control panel, find those modules and delete them. if you get a message about children, you have to click on the module name and delete any modules that are below it. work your way back out until you can delete the main module.
Users browsing this forum: Baidu [Spider] and 16 guests