vBulletin Upgrades and Saving Hacks!!

[silkroad]

Hi Again!

We just upgrade to vB 2.2.3 and lost our hacks (again!)....

This is quite time consuming... and going back and trying to put in old hacks is not fun.....~!~~! keeping old hacks and adding new hacks if FUN!!

How do other people install hacks to make this process easier and take less time.....? Do others have this problem?

I was thinking about placing hacks in include files..... and then including (php include) the hackin the raw HTML...... because we have manys styles and don't have time to add the hacks to each style via the admin templates area.

Obviously, there must be easier ways What are we doing wrong?? Thanks for your help!

[Admin]

If you bothered clicking 'Install' every time you installed a new hack, you should have a full list of hacks you installed here:
https://vborg.vbsupport.ru/member2.p...bscriptionhack

[silkroad]

Thanks, never saw that... certainly seems like a good way to track installed hacks!!! We will use that in the future!

However, still wondering how others configure hacks to minimize the pain of reinstalling them after upgrades to vB Thanks!

[Admin]

As you install more hacks you will get more accustomed to doing it. Of course people with technical background that know some PHP basics have a huge advantage.

[mvigod]

I think what he's asking is there an easer way to do it rather than run through all the files again reinstalling each hack and template all over again.

At this time there isn't another way that is easier so it really is a PITA.

[silkroad]

I think was going to stick all the hacks in files and use PHP include(), but the problem is that it is not just including lines of code, but commenting out or deleting lines of code.

So, treating hacks like lib or include files only solves a small part of the problem....... geezzzz!

[Recon_Boy]

me thinks that's why they call them 'hacks'...