Jump to content

How do I prevent Login Page Customization from being wiped out after an update / patch?


Recommended Posts

May you please help me keep the Login Page Customization files from being nuked during any future updates?

 

• /admin/templates/login.tpl

• /admin/templates/login.css

 

I'm reading over the 6.0 Release Notes and I just don't see any clarification. I've previously edited these files, but during a recent update they were wiped-out. I was thinking, maybe I could add these files to my theme folder (which is a duplicate of the template six) but a login.tpl file already exist and I forsee bad news if I nuke that.

 

Thanks for your time and happy days!

 

p.s. - currently I just have these files backed up and after each update I just overwrite, but there has to be a better way! right?

Link to comment
Share on other sites

I'm reading over the 6.0 Release Notes and I just don't see any clarification. I've previously edited these files, but during a recent update they were wiped-out. I was thinking, maybe I could add these files to my theme folder (which is a duplicate of the template six) but a login.tpl file already exist and I foresee bad news if I nuke that.

that sounds like a bad idea to me.

 

p.s. - currently I just have these files backed up and after each update I just overwrite, but there has to be a better way! right?

I think that's going to be the easiest way - or just don't upload the updates for those two files when you upgrade.

 

I have previously posted an admin hook that would allow you to use a custom.css in your admin area, but it wouldn't work on the login page as I think it's considered to be outside of the admin area... I thought that might have at least solved the css issue, but not to be.

 

http://forum.whmcs.com/showthread.php?111051-Change-Tab-Color-and-Text&p=452667#post452667

 

I can see alternatives, but they're all more long-winded then just replacing the files after each update - I guess, excluding betas, there's only about a half dozen updates per year... so probably just easier to carry on the way you are.

Link to comment
Share on other sites

Thanks for the clarification.

 

It would be nice to have this automated because the autism in me wants a matching color theme with the rest of the site. Just imagine how much more awesome WHMCS would be if there was a half a dozen more updates each year!!

 

Mwhahahha

 

Thanks and gl

Link to comment
Share on other sites

Thanks for the clarification.

 

It would be nice to have this automated because the autism in me wants a matching color theme with the rest of the site. Just imagine how much more awesome WHMCS would be if there was a half a dozen more updates each year!!

 

Mwhahahha

 

Thanks and gl

 

Your best option is take notes, and list the files you changed and then compare them with the update files to merge the changes.

 

You can use a software like Beyond Compare to easily merge changes from file to file. This is what I do on each update and yes, I compare file by file, it's takes it time but gladly WHMCS offers patches with only the changed files for small updates. This is the only way you can really guarantee updates will not overwrite your changes.

 

If you just upload each update over your file, you will always end up overwriting something you forget you changed.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use & Guidelines and understand your posts will initially be pre-moderated