Hi,

I need a little guideance, as I can't seem to figure out using the manual, what to do next.

The situation is as follows: We had a master site running JMS 1.2.97 on Joomla 2.5.8 with K2 2.5.6, which we have now upgraded to Joomla 2.5.14 and JMS 1.3.15 + K2 2.6.7, and below this we have about 28 slave sites.

All upgrades seems to have gone fine, and sites (both master and 28 slaves) are running and working as expected.

BUT - using the "Maintenance"-tab - and looking on slave sites, we can see that the database schemas for booth Joomla core and K2, are still the old schemas J2.5.8 and K2 2.5.6.

But we can't figure out how to bring the schemas up to date? We have backed everything up, and have tried choosing the various Default Rules for Database and clicking "Fix DB", but with no luck. Best case nothing happened and worst case, we crashed the slave chosen, and had to restore database for the slave.

So how do we progress to make sure the database schemas are being updates for all slaves - both Joomla core and extensions?

We have attached a screenshot of a slave, which represents how all our slaves look at the moment.

Kind regards,
Henrik Holm Nielsen

Nobody have a hint on how to progress from here?

Cheers

When there are a modification of the DB structure, there are sevearl possiblities.

First, you intuitive solution to "Fix DB" is correct.
The "Fix DB" present in the maintenance menu is similar to the one present in the "Extension Manager" / Database / Fix DB button.
Concerning the core joomla DB structure, the extension manager / database / fix DB can be used and will fix most of the structure of the joomla core.
So extensions sometime add information in the extension manage / database / fix DB and can also benefit of this mechanism to apply the DB structure modification.

Unfortunatelly, most of the extension does not do that and this is the reason why we have created the "maintenace" menu.
The most important in the maintenance menu is to select the correct rule as reference for the DB structure modification or use the "Free SQL" field to enter the rules that you want to apply.
The JMS maintenance menu provide the detail of what it has detected and is able to compare a current DB structure with either:
- Extensiion manifest file that describe the installation SQL script
- Scan of the extension directory to try finding the SQL files that either contain the full installation SQL or update
- Use the current master website structure
- Use THIS website structure. As the master and this website can be different, THIS is used to identify the current website.

Your screenshot is incomplete and mainly the last columns is cutted and does not allow reading if the diagnosis is succes, error or skipped.

In addition, to make a correct Fix, you need to select the Joomla 2.5 rule and not the default Joomla 1.6.x rule that is proposed for the migration from J1.5


In summary, I suggest that you start using the Joomla extension manager / database / fix DB that will reduce the number of errors and perhaps that K2 also provide to joomla its DB structure update that can be used by this Fix DB.

Otherwise, you will have to use the JMS maintenance menu to fix the DB
Or try re-installing the K2 into the slave site. Some extension are able to detect the DB structure modification during their install and apply the changes.

Hi Edwin,

Thanx for your response!

However, I do have some problems fixing my issues and have now bought some support time from you in the shop, and hope you can help fixing my problems.

Looking forward to hear from you

/Zorroson