hello,
I just renewed my subscription for JomSocial
I am running Joomla 2.5.27 (the latest) and for migrating to Joomla 3, I need to update JomSocial before.
Can I directly update Jomsocial v2.6.2 to v3.2.1.5?
Thanks for your help
I read that it was possible to install on v2.6.2 standard (without uninstall) and in order :
v2.8, v3.0, v3.1, v3.2
But my version is standard, not pro, and in older download page I found mainly pro versions.
Is it possible to install pro version in place of standard version to upgrade ?
Hi Jean,
Yes you can, but you should apply the database changes manually, please you download this file for the database changes information
www.dropbox.com/sh/zln48nosnc25l1l/AAAUw...XUBwmenUeDspnIa?dl=0
I hope it will help.
thank you
Thanks a lot for your help,
I have some more practical questions :
- must I install v2.6.3 pro on my v2.6.2 std first ? (with or without modules and apps ?)
- In what order ? I suppose upgrade first and patch in two ?
exemple : I upgrade my v2.6.2 with v2.8.4.2 upgrade files and I apply upgrade_2.8.sql
(following with : v3.0.5.3 pro and upgrade_3.0.sql - v3.1.1 Std and upgrade_3.1.sql - v3.2.1.5 std and upgrade_3.2.sql)
- How do you apply sql patchs files ?
- At what level is it possible to use iJoomla-Installer-Updater found in v3.2.1.5 ? (should have been easier to directly apply it to v2.6.2 ;-))
Hi Jean,
You can upgrade to the latest version 3.2.1.5 directly, and then you should apply the DB patch manually one by one.
eg. you open this file upgrade_2.8.sql first, and execute this code via phpmyadmin :
ALTER TABLE `#__community_photos` ADD `params` TEXT NOT NULL;
ALTER TABLE `#__community_photos_albums` ADD `params` TEXT NOT NULL;
ALTER TABLE `#__community_videos` ADD `params` TEXT NOT NULL;
ALTER TABLE `#__community_register_auth_token` CHANGE `ip` VARCHAR(255) NOT NULL;
Thanks a lot, I'm going to try and will go back here.
I think there is a lake in upgrade_3.0*.sql
ALTER TABLE `#_community_users` ADD `cover` TEXT NOT NULL AFTER `thumb`;
ALTER TABLE `jos_community_groups` ADD `cover` TEXT NOT NULL AFTER `thumb`
ALTER TABLE `jos_community_events` ADD `cover` TEXT NOT NULL AFTER `thumb`
ALTER TABLE `jos_community_groups` ADD `hits` INT NOT NULL
ALTER TABLE `jos_community_photos_albums` ADD `eventid` INT NOT NULL AFTER `groupid`
Because i have no jos_ prefix in my db
so I must consider that jos_ must be replace by my own db prefix too ?
Installed v3.2.1.5 (but forget to uninstall previous version of Jomsocial. Don't know if it is important ?)
Applying upgrade_2.8.sql and following error message for :
ALTER TABLE `(my prefix)_community_photos` ADD `params` TEXT NOT NULL;
#1060 - Duplicate column name 'params'
Applying upgrade_3.0.sql and following error message for :
ALTER TABLE `(my prefix)_community_users` ADD `cover` TEXT NOT NULL AFTER `thumb`;
#1060 - Duplicate column name 'cover'
Applying upgrade_3.2.sql and following error message for :
ALTER TABLE `(my prefix)_community_wall` ADD `params` TEXT NOT NULL;
#1060 - Duplicate column name 'params'
When I go to FrontEnd in photos album page, JomSocial answer :
"Pas encore d'album créé. "
no photo album created
I checked in backend, photos are always presents.
[EDIT 1]
Problem seems to come from ".../galerie-medias/display"
[EDIT 2]
Don't find any place where I could set Albums ?
Hi Jean,
Did you upgarde jomsocial well? I read you have some problem with DB patch, if you have the duplicate fields just skip it, and try to run the query one by one / line by line which delimiter by semicolon ;
Please provide me the backend access so I can check your issue directly.
thank you
Hi,
I tried line by line but still have error message for each line
with
ALTER TABLE `(my prefix)_community_photos` ADD `params` TEXT NOT NULL;
#1060 - Duplicate column name 'params'
with
ALTER TABLE `(my prefix)_community_photos_albums` ADD `params` TEXT NOT NULL;
#1060 - Duplicate column name 'params'
and two flollowings lines same error
I gave You admin access parameters to go in backend
The problem is that I can't access gallery in front (JS says that there is no album) but everyhting else seems to work. No error message in backend.
It seems that each line of patch have been succeed because when I check in tables, params have been well added