Unless you enabled it, its disabled by default.

Its perfectly acceptable.

Were I not on holiday, id post a list of changed files, but as it happens, I am.
The list linked to above seems reasonable from what I remember.

You are correct. If you've invested a lot of time modifying your forum then upgrades are almost like dismantling and reassembling your entire site.

I would suggest avoiding any upgrades if you can.

And how would you suggest such people protect themselves from this exploit? :confused:

Not if you were smart about it. Using tools like Template Modification System (TMS), creating good documentation along the way. Upgrading could be a real pain during the early vB4 releases, I agree - but you really should not run those anyway, bugwise. But if you have file edits that make overwriting the original files of the same version a real pain, then you're most likely doing it wrong. Given the plugin system there is not much need for file edits, but if you do them, keep them properly documented and use diff tools.
Which is a stupid suggestion, really.

I would not pay too much attention to his ramblings.

Given the timing of it, and his general attitude here, I think its little more than a feeble attempt to stir.

Well when you return a changelog would be nice and I'll buy you some Dr. Pepper if you do :D jk jk.

I will be building a PL2 patch when I return, not something I can do from Gran Canaria :)

Lucky bastard!

You mean you will not leave the Canary Islands for us? And I thought you cared.:erm:

Updates are a hassle but good. I just may wait for your patch though Paul!

Anyone have a CMS patch for 4.2.1 from the latest 4.2.2 upgrade? Wondered if 4.2.1 PL1 CMS can be patched to the release for 4.2.2