when you say rehack you mean just the php files or even reinstall sql??

Just the php files that have changed from the upgrade...

You shouldn't usually have to worry about the SQL, lol.. that would suck if you do....

Refer to this for a 3.0.5 security patch involving private.php
https://vborg.vbsupport.ru/showthread.php?t=74035

D'oh!

My private.php is rather hacked. I guess I'll be patching the file for the first time ever.

i am with Mark.B on this... not to be rude, but this is a pain in the butt to constantly have to reinstall every hack because there's a new update every week or two

it is already unsatisfactory that every aspect of this particular company has to be paid for (after paying $160 to be able to have an owned license, the last thing i should have to pay for is yearly access to the members' section (which only has one important feature - software updates)... true it is not a lot of money, but that is not the point....

the point is, i am quite sure that everyone would've been more than happy to stick it out on vB2 until vB3 was THOROUGHLY finished and had none of these constant "oops, we found something... get the latest download ASAP" issues :ermm:

I would take a security fix over a possibly less-well-coded third-party modification any day. However, I do agree in my opinion that they should not charge access to the Member's Area for releases in the same major.minor group (i.e., 3.0.x). I know they usually post fixed files in the announcements, but there are dozens of bug fixes in each release that get left out.