This has come up before, each time it’s different. Though I spent a considerable amount of time getting the update good to go, I’m holding off implementing it until I have to. This could be in as few as a couple of months to several months, all depends when the hosting company makes the change. They have stated sometime in 2025, whether that’s closer to January or December is anybody’s guess.
I’m confident in the updates I made, however since everything is working exactly how I want now as is without the updates, I see little reason to make such a major change until absolutely necessary.
I haven’t inquired, but I’m expecting that when the hosting company is ready, they’ll inform impacted customers of the cut off date, not just surprise people.
The other 'Murphy's Law' consideration is that something may have been missed - it's working now, might not if update has problems. Small risk, but there.
I do want to automate as much as possible, and this is just one of those steps towards that goal.
The curiosity to see if everything works is there however, nagging at me to make the switch sooner than later. On the one hand, I'm relieved to know that I have updated code that *should* work - that in itself was no small feat. Perhaps because of all the head scratching and hours spent the desire to see my work in use is the big draw? In any event, at least it's not an emergency. The updates are done and ready to be deployed.
UPDATE 10/19
Well, I've done it. Updates are on the server. Now comes the fun part! Seeing if theory and reality match up and everything works.
UPDATE 10/19 cont.
Unfortunately, errors persist so back to the old files for now.