Dear Edwin,

To successfully propagate our tables from our ::master db:: to our slave sites db, we have added these lines into the patches/sharing/dbtables.xml file:
<tables name="Egp" option="com_egp">
<table name="#__egp_%" description="Egp" />
</tables>

However, we are not able to successfully propagate any updates.

Into our xml installation file, we have this schema:
<update>
<schemas>
<schemapath type="mysql">sql/updates/mysql</schemapath>
</schemas>
</update>

Into our ::master db:: we have into #__schemas, a row with our extension id and a version id (ie: "0.2.2").

Is it normal that we don't have this into our slave sites db?

When we update our component, the column version id of the #__schemas table row gets updated and becomes "0.2.3" (and our component tables gets successfully updated too in our ::master db:: ) BUT nothing happens in our slaves db!

We have done some tests -> we manually added the row into the #__schemas of each slaves db with the correct extension id (from #__extensions slave tables) and pushed into version_id the value "0.2.2".

Doing an update with the "fix db" function from the "maintenance" tab, our component tables doesn't get updated into the slaves sites db and the value of each table #__schemas column "version_id" becomes empty.

Can you please explain us what we are missing to resolve our slave db updates issues?

Thanks in advance!

If you have a public extension that you would like that we add in the JMS definition, you can send us the extension in the attachement of an email.
Otherwise, any update that we will do will overwrite you specific modification.

If you have a specific extension, we can also create a specific plugin to let you add in the future other specific definition and sharing.
If you want that we create the plugin for you, this is possible with our billable support and we can do that in 1 hour.
www.jms2win.com/en/joomla-multisite?page...35&category_id=1


Concerning the update/upgrade of the schema in each website, you need to go in the back-end of the slave site to perform the extension manager / database => fix
or perhaps the update menu.

Today, there is no propagation processing to perform the database upgrade automatically in each slave site attached to the standard joomla database fix.

I will cross-check the processing with the maintenance menu to verify the schema update.

The fact that the version number disappear in the slave site seems to be due to the fact that no rule were selected to verify the extension or that no rule were found.

In the next release of JMS 1.3.30, I have added a cross-check to verify that we found the new version number before applying the change in the schema table.