Operationally speaking, I don't know what that would entail. If it means putting old, dead, malfunctional code back into tag_manager.php and then overriding it later in the file or in another file, I can't see that as a good idea. It really would be better to make a clean-break fork and require total uninstallation of the old RH Topic Tags and installation of the new one as a stand-alone extension.Well, idealistically it would be revertingtag_managerclass constructor back to its initial state for this to work correctly in "old" migration, and creating a child class with your updated code inheriting from that "reverted"tag_managerclass.
Statistics: Posted by SMcCandlish — Mon Mar 24, 2025 8:09 am