DB upgrade and init_includes ?

[hubert]

Hello,

We are in the process of upgrading from 1.3.7 to 1.5.0.
As we are also updating our look and feel we used the "new site" method :
we installed a brand new 1.5.0,
customized the look and feel,
added some plugins and it works quite well.

But during our test time the old site is still online and new customers and new orders have been added in the old database,
so our plan was to :
1) Migrate again the old but still used database to 1.5.0 (install sql patches files)
2) Install all sql patches (those of plugins when they exists)
which theorically sounds a good method but we are facing two problems :
the first one was that there was no menu on admin side.
We discovered, looking into the database, that the superuser profile was 0, so we changed it to 1 and all is ok.

The second problem is that for some plugins the sql patches are in a php file which is in the admin/init_includes folder.
I thought that these patches would get done automatically as they are on first install but it is not the case.
Result is that a lot of my plugins are installed but not in the admin menus.

Can someone tell me how the init_includes files knows if they have to do their job or not, and how to change it.
My hope is that knowing that I will be able to execute all necessary patches and find back my plugins, so my whole site with an up to date database.

Tanks for help

Regards

Hubert

[DrByte]

I recommend you review this article and consider how it compares with your current approach: http://www.zen-cart.com/entry.php?3-...he-new-version


As for init_includes files, they are only loaded if files in the auto_loaders folder tell it to load them.