By Troy T. Hall on Wednesday, 30 April 2014
Posted in Technical Issues
Replies 13
Likes 0
Views 1.2K
Votes 0
When migrating jomsocial cover photo's are not imported nor set as "cover photo"
Hi Troy,

I am sorry for the delay of this reply.

Issue fixed internally The fix will be added into next release of EasySocial.
Have a nice day
Sam
·
Wednesday, 30 April 2014 15:48
·
0 Likes
·
0 Votes
·
0 Comments
·
thanks sam. Will it be possible to import the cover photos or will that mess up the profiles?
·
Thursday, 01 May 2014 01:26
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Troy,

If these "data" are already migrated, it would not be possible to re-migrate the same data over again
·
Thursday, 01 May 2014 12:23
·
0 Likes
·
0 Votes
·
0 Comments
·
right, what I'm trying to figure out is.. since only the covers ( afaik ) have not been imported ( all users have ) will the covers be imported or will it be skipped for existing users.
·
Friday, 02 May 2014 02:58
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Troy,

If the user's are already imported, the migrator would not be able to re-migrate these user's unfortunately
·
Friday, 02 May 2014 22:47
·
0 Likes
·
0 Votes
·
0 Comments
·
NUTS!.. ok, ty.
·
Saturday, 03 May 2014 05:33
·
0 Likes
·
0 Votes
·
0 Comments
·
Do you have the old JomSocial data? If so you might be able to work out a solution if your careful.
·
Saturday, 03 May 2014 07:10
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Troy,

Yeah, as Josh mentioned if there are no changes on the "imported" data you could re-import it again but if your users has already make changes to their "new profile", this wouldn't be possible We wouldn't know the data integrity of whether it was imported with that particular value or the user has already changed to a new value.
·
Saturday, 03 May 2014 15:59
·
0 Likes
·
0 Votes
·
0 Comments
·
not to make life harder but maybe some kind of a "if cover folder then" utility. I anticipate they will have modified things, as I have.
is there a way to "copy" the images in /image/covers to easysocial so that it "discovers" them? or maybe a import x into y function?
just a thought.
·
Sunday, 04 May 2014 02:32
·
0 Likes
·
0 Votes
·
0 Comments
·
What if you created a test site where you import the JomSocial data, install easy social, then use the migration tool of ES. From this point forward you would need a way to export the "ES cover photos (formerly JomSocial)" and import them into the beta live site (an exact replica of the real site as it is right now) which can be found in the _social_covers table in the database. Theoretically that part should be fairly straight forward. Getting the meta data properly associated might be more complicated.
·
Sunday, 04 May 2014 10:11
·
0 Likes
·
0 Votes
·
0 Comments
·
that's not a bad idea theoretically, copying the images to given folders, then updating the db is all that's needed. Hopefully we can come up with some form of a workable workaround. I probably am not the only person needing this, though maybe I am. If so it would probably not be a productive use of time.
With Jomsocial I was told this was impossible ( in the case of builk import of photo's )
·
Sunday, 04 May 2014 12:29
·
0 Likes
·
0 Votes
·
0 Comments
·
It partly depends on if any data was copied from the initial migration of the covers in the database. If there are no records at all in the database from the import when you did it back when you did, that will make the situation a whole lot messier. The reason is because if you successfully import the jomsocial covers on the new site, let's pretend one of the cover photos has an id of 461, users who have posted since the migration could just as easily have that id (and many others around that area) taken. As a result the only way to get the cover photos back would be to over ride some people's photo posts since the migration. This terrible scenario is only if not an ounce of cover photo data was imported. If there is, then I think it's still possible to figure this out. As a web detective I enjoy cracking problems. But sometimes they can be scary even by my standards.

I could explain it more, but it would get kinda confusing. Basically the issue might be due to conflicting ids and the system not being able to generate unique ones from an "extra import".
·
Sunday, 04 May 2014 13:44
·
0 Likes
·
0 Votes
·
0 Comments
·
Hey guys,

I think it would be really complex to determine if the use has then switched / updated a photo and there's no real way to "verify" the integrity of the data if the user has already been migrated and he / she updated a photo / cover.

Take a look at this scenario for instance:

1. EasySocial migrates the user's cover from JomSocial -> EasySocial, the cover file gets a new name etc etc.

2. User updates his cover in EasySocial and the cover file gets a new name etc etc.

3. Now, if there are some issues with some of the covers, this would be problematic. There's no way to determine the "differences" between part #1 and part #2. We will never know if the change was by the user or the migration process.

If the cover issue only affects like 1% - 5% of users on the site, I would just suggest them to re-update their cover. It wouldn't take 10 seconds to upload a new cover and it gets less complicated
·
Sunday, 04 May 2014 17:13
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post