Question A note of congrats on a job well done -- upgraded 2.0.7 to 2.1.18 manually

Was worried as heck when my hosting provider decided last minute to remove all PHP versions except 8.1 and later.  I was still on webtrees 2.0.7.  And begrudgingly gone there from 1.7 when they forced PHP 7 on me.  But I downloaded the 2.1.18 release, overlaid it onto my existing 2.0.7 code installation, modified a few things I do (icons, RelationIsDescription / GedcomCodeRela php table), and visited the home page.  After an agonizingly long 90 seconds or so, my familiar page with an updated look popped up for me. Quick checks and everything looks good. Even still pointed out recent changes I still needed to accept. Just felt it worth giving an "everything went swell" and thus congrats on a thorough job well done. Some of my other tool upgrades did not go anywhere near as smoothly.

My only nit is every Individual seems to have a "INDI:_PRIM" that shows up in red on every page.  I think left over from PHPGedView days which I had started with 16-16 years ago . So may need to do a database global replace for that to remove it everywhere. But nice that the unfamiliar / non-standard GEDCom item now shows and shows in red so it is easily noticed.

Check out Control panel | Family Tree | data fixes | Convert OBJE:_PRIM tags to GEDCOM 5.5.1

Looks great. Only nit I would add about that is give the option to retain the old change date. It updates the date on almost every individual to todays date. I would rather keep the last known "true" genealogy data update
Forgot about the tree-wide setting to retain the previous change date. Simply set that on, did the update, then returned it to off.