Re: Upgrading extensions on slave sites 14 Years, 5 Months ago
|
Karma: 0
|
Hi,
The slave site administrator, components, plugins and modules are all sym links to the master site folders. There are only the sym link folders. When I follow the sym link I can find the sourcer plugin in its system folder, so I don't know why it says that the plugin is not installed on the master site. When you login to the master site and go to plugins the Sourcer system plugin is installed and shows the latest version number.
Any ideas on how to get sourcer to upgrade on the slave site?
Thanks.
|
|
rlab
Fresh Boarder
Posts: 11
|
|
|
Re: Upgrading extensions on slave sites 14 Years, 5 Months ago
|
Karma: 0
|
Hi,
I tried deleting Sourcer on the Master site and then re-installing it, but when I go to install Sourcer on the slave site I am still getting the following message:
* This extension is not found in the master site.
* Please install it first in the master site before installing it into the slave site
* Install Component Error
How can I upgrade the plugin?
Thanks.
|
|
rlab
Fresh Boarder
Posts: 11
|
|
|
Re: Upgrading extensions on slave sites 14 Years, 5 Months ago
|
Karma: 54
|
Would you please send us in attachement of an email the extension that you are trying to install into the slave site.
Some extension like the one distributed by "NoNumber" company may have an experminental installation method that may conissts in using another extension to install the final one. Perhaps this is the kind of extension that you are using and that use a another component name to install the target one.
In this case, you have to identify the "wrapper" extension that may have another version number.
|
|
|
|
|
|