How SHOULD I Handle MODS, when Upgrading from 4.x to < 4.x

[NashChristian]

Hello everyone,

I'm getting wore out on this 4.0 conversion! Each time I run the upgrade script, when it gets to the styles section at the very end, I get a "Fatal error: Out of memory", (however I have plenty of space in my hosting package, that's not the issue).

Then I have to delete my entire site and the database, and replace it all with my pre-upgrade backups, then go in and revert all my templates, then upload the new files for the upgrade, then run the upgrade script again. It is plain wearing me out!

Ok, I did all of this (a couple times) and made the transition from 3.8.4 to 4.0.1. I honestly didn't think it would be an issue upgrading from 4.0.1 to 4.0.2, but here I am again, facing the same Fatal error.

http://nashvillechristian.com/images/misc/vb-out-of-memory.jpg

Prior to the upgrade from 4.0.1 to 4.0.2, I disabled all my mods, selected the default style as the primary, and even added the 'disable hooks' in the config file, but apparently that wasn't "good enough".

So again I'm deleting the site and database to upload my final pre-upgrade backup. Then I will uninstall a half dozzen mods I've installed, revert all the templates, upload the new files for 4.0.2, and again run the upgrade script.

Here is my question: Can I just disable the mods and revert my templates (instead of uninstalling the mods) OR do I need to uninstall all mods everytime I upgrade my vB? My thinking is that some of the mods may alter the templates when they are installed, so if I just disable them and revert the templates, though that may work for the vB upgrade, it will kill the mods to where I can't just enable them again. I'm thinking that if I physically uninstall the mods, and then reinstall the mods, that whatever changes (if any) they did to my templates, it will perform again when I reinstall them. Am I correct in my thinking? PLEASE tell me that there is an easier way!?!?!? Do I also need to completely uninstall any additional styles?

This has been an EXTREMELY frustrating transition!

How SHOULD I be facilitating upgrades (from within the 4.x family)? (I've probably read 20 different 'how-to' threads on this and am still scratching my head.)

Please help.

Thanks!
:( Jeff

[borbole]

It seems like its a memory issue with php. Try to add the following cose somewhere below the starting php tag in the config.php file and run the upgrader once again:

ini_set('memory_limit', 64 * 1024 * 1024);

[NashChristian]

It seems like its a memory issue with php. Try to add the following cose somewhere below the starting php tag in the config.php file and run the upgrader once again:

ini_set('memory_limit', 64 * 1024 * 1024);

Thanks for the help Borbole.

I've actually got it to work by doing as I said above, restoring the backups, reverting all the templates, then running the script again. I guess I'm really wondering for future upgrades, how I SHOULD handle MODS prior to upgrade. Should I uninstall them all and revert all the templates first, or should I just disable them and revert all the templates first, or ???

This 4.x transition has just been a nightmare so far.

Thanks again for your help.
Jeff

[borbole]

The best way to go about it in my opinion is to disable the mods prior to the upgrade. It lessens the chances of throwing the occasional odd mod related error.

But whatever you do, always make a backup of your db first.