View Issue Detail

ID	Project	Category	Submitted / Last Updated
01359	UserSpice	Triage	2021-10-17 13:06:47 / 2021-10-18 07:10:08
Reported	James Erikson	Assigned To	Unassigned
Priority	none	Reported	5.3.5
Status	closed	Resolution Version and Commit
Summary	Updates should mention what files will be replaced
Description	When an update is available, it would be cool if it could mention which files are going to be replaced/reset. For instance, the recent beta update to 5.3.6 replaced the login.php file and I lost my custom login page. Thankfully had a backup to restore from but a warning may help users realize what pages to put their customizations back to :)

November 2021

This is a good change and likely something we'll try to make, but don't edit core UserSpice files. Make changes in usersc/
November 2021

I understand although I use my own login.php file as I can't upload my template to work with userspice correctly (it's a purchased bootstrap theme that I can't give up)... I'll eventually try to see if I can get the usersc templates to work as expected somehow
November 2021

We already offer this information, but just not in bleeding edge. When you go to https://github.com/mudmin/UserSpice5 you can click on the list of commits and every version number is listed and you click on that little commit hash on the right https://i.imgur.com/BWlnFWr.png and you get a full list of file changes in every version. But the point is that we've gone to ridiculous lengths that there is no reason to change the core files in userspice to do what you need to do... so in exchange, we don't give a lot of consideration to what we update. It's sort of like we have "our side" and "your side."
November 2021

Understood. I made a backup of the core files that I need to change so I'll always know how to fix it, no problem. Thanks