I truly believe this is a bug and hopefully will be fixed ASAP.

We always use up to date jms2win component and trying hard to make it work for our needs. Unfortunately every time when trying to upgrade components on the slave websites Every time we get similar error for Duplicate Entry



Error
An error has occurred.

1062 Duplicate entry 'com_jfbconnect' for key 'idx_asset_name' SQL=INSERT INTO `www_assets` (`name`,`title`,`rules`,`parent_id`,`level`,`lft`,`rgt`) VALUES ('com_jfbconnect','jfbconnect','{}','1','1','786','787')

If you have 2 slave is still OK. We delete /administrator/defines.php and instalation folder and then we can upgrade components . But we are expanding and want to have entire system working perfectly and noticed trying to solve those issues cost us more money and time than anticipated.

We do not use strange configuration. just updated to joomla 3.2 hoping issue will be solved. But is not.

Now we are facing simple question is it worth to use jms2win at all?

Please be so kind and help us to solve this issue once for all. We already paid before to solve this issue. Now sorry we are not planning to do so. We truly believe this is a bug and bug fixes should be included withing regular maintenance upgrades.

Thank you for your time

If you remove the "define.php" file, this may cause side effect because it is possible to it run on the master instead of the slave site.

I suppose that the procedure that you used is that you login in the slave site and try to re-install an extension (that is in relation with JFB Connect tables) and that you receive this error.

If this is what you did, that mean that the version number of the extension in the slave site is the same as the master.
If you want to ignore this control, you can also go in the JMS Settings menu and TEMPORARLY set the flag to ignore this control.
Perhaps that could help you.

This problem can also be due by the extension itself.
Most extension are re-developping their own stuff to do the installation and ignore the standard Joomla installation.
Perhaps this is the case of this extension 'com_jfbconnect'.

Send us a copy of this extension in the attachement of an email and we will have a look on it.