CE Phoenix Upgrader Utility

[Dan Cole]

John, I installed your latest update and it works as expected. I did have a couple of ideas that I thought I would pass along FWIW.

1. It would be nice if you could link directly to the upgrader from within the admin area. Installing it on the admin side of the shop might also allow you to avoid the login and password routines.

2. As I looked at the list of files that had changed I wonder if new files, that aren't part of the core, could also be included? I'm thinking of files that were added, on both sides of the shop, so that a list of those files would be readily identified and available. It might also be nice to have the option to backup those files to a separate directory structure for future updating. Perhaps in a PRO version, you might be considering.

Just some initial thoughts that I figured I'd pass along while the occurred to me.

Dan

[BrockleyJohn]

1. I assume that Preston separated the upgrader from the store code for a couple of reasons. Mainly that a dependency on working admin could break the upgrader mid-upgrade if it involves interdependent changes or is adversely affected by a store addon. This could leave the store in an unknown state that could take some serious investigation to figure out how to untangle it, or require you to restore to the backup you took just before the upgrade (you did remember that, didn't you?). The other reason is to keep its own files out of the core compare.
On the other hand, it might well be useful to have some upgrade-related activities accessible and manageable from within admin since in real life it's not a quick run through but a look at what's involved and then a while working towards it.

2. New files, yes and mostly in a pro version I think, though maybe at least a worklist for them in the free version. There are several different kinds of new files. Template files which are mostly changed core files but might also be extra, addon files, language files and bespoke files. I was thinking that some of these would also bear a version check which would be handy. When core language files have new definitions, additional languages could have the new constants added to prevent the crash you get on php8+. Not sure why you'd want to back them up unless they're being changed though.

[Dan Cole]

Thanks for taking the time to reply John.

Regarding the idea of including the code in admin...I wasn't thinking of making it dependent on core files just more or less having it parked within the admin directory to skip the login functions need for password etc. If that is possible great but if not a simple link to the app would suffice from my point of view.

Regarding the new files idea, I'm not really sure why I wanted to be able to back up those files other than my lack of comfort with what might be updated and possibility overwritten and perhaps, in general, out of an abundance of caution. In any event I'm glad to see that you think there is merit in identifying the new files and perhaps generating a work list. In either case I would be interested in helping in anyway I can, including being a purchaser of a PRO version if you decide to go that route.

In theory updates are said and should be easy to manage but for me it couldn't be farther from the truth. I always find myself way behind, version wise, and I know others struggle with that too. I think it leads to very fragmented community and I'm willing to do my part in trying to make that easier. If I can help just let me know.

Dan.