English (United Kingdom)
Jms Multi Site, formerly joomla multisite.
Create, share multiple joomla sites in few clicks !
Message
  • EU e-Privacy Directive

    This website uses cookies to manage authentication, navigation, and other functions. By using our website, you agree that we can place these types of cookies on your device.

    View e-Privacy Directive Documents

Welcome, Guest
Please Login or Register.    Lost Password?

Upgrading extensions on slave sites
(1 viewing) (1) Guest
Go to bottomPage: 12
TOPIC: Upgrading extensions on slave sites
#4764
Upgrading extensions on slave sites 14 Years, 5 Months ago Karma: 0
Hello,

I have upgraded my master site to have the latest version of all extensions. But when I go to a slave site and try to upgrade some extensions, I am getting errors.

For example, when I try to upgrade Xmap on the slave site I get the following message:


* The version of the extension is not identical to the one installed by the master site.
* (Found version: '1.2.8' expected: '1.2.1')
* Install Component Error


When I try to upgrade Sourcer I get 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

The extension is installed in the master site.

The slave sites are setup to have their own database and share the source code.

How do I get the extensions upgraded on the slave sites to match the master sites?

Thank you.
rlab
Fresh Boarder
Posts: 11
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#4766
Re: Upgrading extensions on slave sites 14 Years, 5 Months ago Karma: 54
That mean that the "upgrade" you potentialy performed has not update its manifest file and still contain a 1.2.1 version

Vierify that the upgrade of the extension also has updated the version number that does not seems the case
edwin2win
Moderator
Posts: 5370
graph
User Offline Click here to see the profile of this user
Last Edit: 2010/07/11 23:33 By edwin2win.
The administrator has disabled public write access.
 
#4770
Re: Upgrading extensions on slave sites 14 Years, 5 Months ago Karma: 0
Hi,

I looked at the manifest.xml file in the master site and on the slave sites and they all show version 1.2.8 installed. Same with sourcer the master and slave sites show that 2.4.6 has been installed.

What do I do to fix the problem?

Thanks.
rlab
Fresh Boarder
Posts: 11
graphgraph
User Offline Click here to see the profile of this user
Last Edit: 2010/07/12 18:01 By rlab.
The administrator has disabled public write access.
 
#4773
Re: Upgrading extensions on slave sites 14 Years, 5 Months ago Karma: 54
You answer is inconsistent as you previously say reported that the expeected version is 1.2.1.
That mean that you have a XML located in the extension that has this version number.
You have to check the manifest (XML) files that are stored on the disk.

Perhaps there are several manifest file in your extension directory.
edwin2win
Moderator
Posts: 5370
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#4781
Re: Upgrading extensions on slave sites 14 Years, 5 Months ago Karma: 0
Hello,

I don't know where the software is picking up the version 1.2.1 from. I tried uninstalling Xmap from the slave site and then try to install version 1.2.8. I get the same error message:

* The version of the extension is not identical to the one installed by the master site.
* (Found version: '1.2.8' expected: '1.2.1')
* Install Component Error

Version 1.2.8 is installed on the master site and that is the version number that is in the administrator/components/com_xmap/manifest.xml file. Is there some multi-site file that keeps track of version numbers that would be causing this problem?

I looked in the database, but the version number was not stored in the jos_components table.

I ended up having to delete Xmap from the master and slave site to get it updated.

But, I still have the problem with Sourcer. Why would I get this error when sourcer is installed on the master site already:

* 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

The slave site just has the plugins folder as a symlink to the master plugins folder, so where would I look for this problem and how to solve it?

Thanks.
rlab
Fresh Boarder
Posts: 11
graphgraph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
#4784
Re: Upgrading extensions on slave sites 14 Years, 5 Months ago Karma: 54
There is no save of the version number in the DB.
The version number comes from a manifest XML file located on the disk.
This is the file that you have to find.

If the slave site does not have a Symbolic Link on the administrator directory then you will find a second copy of the manifest file into this duplicated administrator directory that will be a symptom of a wrong configuration as you will have to maintain the "replicated" administrator directory manually.
edwin2win
Moderator
Posts: 5370
graph
User Offline Click here to see the profile of this user
The administrator has disabled public write access.
 
Go to topPage: 12
get the latest posts directly to your desktop
2Win, Multisite(s) are trademarks of Edwin2Win.
Joomla