like some of us have plugins installed, it'll be more easier to have the source instead of having the full install so that we would not end up replacing the whole lot. by then we would know how we end up with errors or incompatibilities.
In most cases, if you do your mods right, you won't have to change that much. My suggestion? Try to avoid editing the core files as much as possible. I've managed to get all my mods going using just a customfunctions.php file with the exception of watermarking which required a slight addition to the i.php file. All of your hacks, mods, etc. should be contained as much as possible in your custom theme directory, and then all you have to do is make sure that you "port" your theme to the new version if things don't work right when you upgrade. If your custom theme doesn't work, at least you can use another default theme until you fix the errors.
With that said, you can also consider using SVN. I am learning about it as I go along, and it's pretty sweet for doing exactly what you are talking about. If you set it up right, it will only replace what you need it to.
Bingo, what craig said. If you're using modifications to the zenphoto code, I can't promise any of those will work with new versions and frankly I do think it's best to start fresh.
Also, you should be keeping all your mods in your theme directory as noted, and including a PHP file into your theme, which you have full control over. Mods for i.php are a bit more tricky, but you'd have to redo them anyway as i.php is changed in nearly every release.
So it wouldn't be much help anyway - just think, the files you want to hack are probably exactly the files I'm going to change the most :-)
I haven't even gotten around to putting the watermark code back in i.php, since I've been keeping up with the SVN code so much, that it wasn't worth the effort. Besides, my stuff isn't photography or art related, so putting a watermark on it was kind of silly anyhow.
Comments
Why would you want that, out of curiosity?
In most cases, if you do your mods right, you won't have to change that much. My suggestion? Try to avoid editing the core files as much as possible. I've managed to get all my mods going using just a customfunctions.php file with the exception of watermarking which required a slight addition to the i.php file. All of your hacks, mods, etc. should be contained as much as possible in your custom theme directory, and then all you have to do is make sure that you "port" your theme to the new version if things don't work right when you upgrade. If your custom theme doesn't work, at least you can use another default theme until you fix the errors.
With that said, you can also consider using SVN. I am learning about it as I go along, and it's pretty sweet for doing exactly what you are talking about. If you set it up right, it will only replace what you need it to.
Also, you should be keeping all your mods in your theme directory as noted, and including a PHP file into your theme, which you have full control over. Mods for i.php are a bit more tricky, but you'd have to redo them anyway as i.php is changed in nearly every release.
So it wouldn't be much help anyway - just think, the files you want to hack are probably exactly the files I'm going to change the most :-)