Hi edwin2win

I cannot replicate the Master template-themes on a Slave (created through "website template")
To be sure, I have verified it by installing of 2 different templates
(lonex.com j!1.6 and joomla-mart.com j!1.7)

I run the discover & install on the slave,
but the theme item does not appear in the "styles" panel
of the "template extension manager".

If I reinstall the theme in the slave it works,
but I see a ghost item in the "templates" panel
of the "template extension manager"

____

-I use only one DB for all master and slaves.

- The "Website template" configurations are:
o- Share whole site=yes
o- deploy folder = ...../home/{site_id}
o- themes folder = {deploy_dir}/templates
o- Folders & files for templates [#16] = "copy"


The site manager panel warns of different number of tables,
but editing slave does not resynchronize.

this is all

update

actually the new slave theme item is missing
in the db table of the styles.

If I use special copy of themes instead of full copy,
(I can see the template-theme symlink in the slave)
the result is the same,
of course I cannot reinstall the theme on the slave.

If the discover is not able to install correctly a joomla template, this is because there are bugs in joomla concerning the "discover".
When a joomla template does has the "templateDetail.xml" that has the field <name> with the directory name then the joomla discover is not able to install correctly the joomla template.

This is a bug in joomla.

When you are re-installing the joomla template from the back-end, in this case, you are using JMS to perform the install and therefore proceed like a first install.

If you have ghost, you have to try uninstall the template and avoid using the "discover" in case where your Joomla template does not take in account the bug present in the "discover" function.

The problem that you describe are due to bugs in discover function and also due to the fact that now Joomla 1.6 and 1.7 create and "extension ID" for the joomla templates.

Solved!

Yes it was J1.73 bug

I patched the xml,
rebuilt the theme zip,
installed it on the master
and finally discovered-installed on the slave.
and now it works!

btw
when we got updated jms documentation?
because there are many details that are
quite confusing using the current documentation, tutorials and the new JMS.

Nonetheless my first impression is that
JMS is a well-done awesome quality software.

We think rewrite the document with the JMS 1.3.x on which we are working for several month.