Hi everybody,
my issue might look a little bit weired, so I try to nail it down in an easy task:
When I have to update EasySocial, usually the update is canceled if the most recent version is already installed. How can I force EasySocial to continue the installation EVEN IF the most recent version is already installed?
If you only answer this question, that´s enough for me.
But if you are curious, why I need this, here is the explanation:
I am using Mighty Sites to clone my website.
So one Joomla-installation is valid for two different domains. Every domain has it´s own database, but some tables are connected.
While the files are all the same (same root on the server), Easysocial is set to "use the same tables exzept of settings". This way, I can change all EasySocial-Settings, but the content ist the same. It´s much easier then it sounds: For the content, the same tables are used, while for the settings different tables are used.
All works perfect, but when I have to update EasySocial, let´s imagine I start the update-process on the main (master) domain:
All files are uploadet and all tables of the master-installation are update.
The slave domain uses the same files, so the files are update for the slave also. And the content-databases the same: They are used for bouth, so with the update on the main-domain this is done.
But ... the settings-tables are not connected. So in the result, I will have "old" settings-tables. This is the state of the installation I have on the slave-domain after updating EasySocial on the main domain:
- Files are updatet
- Content-tables are updated
- Settings-tables are not updated
For most other component it works to simply update the component on the slave. But in case of EasySocial, it will not continue the update after it found out, that the most recent version is already installed. So I need to somehow make the update even if it says "most recent version is installed".
Do you understand my issue?
All th ebest, Julian!
my issue might look a little bit weired, so I try to nail it down in an easy task:
When I have to update EasySocial, usually the update is canceled if the most recent version is already installed. How can I force EasySocial to continue the installation EVEN IF the most recent version is already installed?
If you only answer this question, that´s enough for me.
But if you are curious, why I need this, here is the explanation:
I am using Mighty Sites to clone my website.
So one Joomla-installation is valid for two different domains. Every domain has it´s own database, but some tables are connected.
While the files are all the same (same root on the server), Easysocial is set to "use the same tables exzept of settings". This way, I can change all EasySocial-Settings, but the content ist the same. It´s much easier then it sounds: For the content, the same tables are used, while for the settings different tables are used.
All works perfect, but when I have to update EasySocial, let´s imagine I start the update-process on the main (master) domain:
All files are uploadet and all tables of the master-installation are update.
The slave domain uses the same files, so the files are update for the slave also. And the content-databases the same: They are used for bouth, so with the update on the main-domain this is done.
But ... the settings-tables are not connected. So in the result, I will have "old" settings-tables. This is the state of the installation I have on the slave-domain after updating EasySocial on the main domain:
- Files are updatet
- Content-tables are updated
- Settings-tables are not updated
For most other component it works to simply update the component on the slave. But in case of EasySocial, it will not continue the update after it found out, that the most recent version is already installed. So I need to somehow make the update even if it says "most recent version is installed".
Do you understand my issue?
All th ebest, Julian!