By Rod Suskin on Friday, 24 January 2014
Posted in Technical Issues
Replies 13
Likes 0
Views 897
Votes 0
Hi
I updated to Easysocial 1.15 using Easysocial's built in updater. It appeared to proceed without a problem.
Ever since the update, though, the news stream no longer shows photographs. If a user updates pictures, updates their profile pic or anything like that, it may (or may not) show in the news stream for a few minutes, and then disappears soon after that, to be left with a blank space or a 'broken image' placeholder. (see attachment)
If you click on the blank space or the placeholder, and click through to the original image, it shows no problem, but in the newsstream it remains an empty space.
Since I am using remote storage on Amazon S3 I am guessing that this is related - once the image is moved to S3 the newsstream can no longer show it? But it worked perfectly before the update!

Please can you help - this has completely ruined my site and makes Easysocial unusable for me,

Thanks
Rod
Hello Rod,

Hm, I have tried to upload a photo and upon synchronizing with Amazon S3, the photo is still available as you can see here, http://screencast.com/t/xr7kxBqXdy . Am I missing anything?
·
Friday, 24 January 2014 18:01
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark

Im not sure the problem is with S3 sync, that was only a guess. I can still see your picture there, there is one posted before yours that has disappeared, and there is one before that which is still there - so Im not sure what is actually causing the problem, all I know is that it only happened since 1.1.15 was installed. Hope you can find the problem!

THanks
Rod
·
Friday, 24 January 2014 18:26
·
0 Likes
·
0 Votes
·
0 Comments
·
Seems to take 2 - 3 hours to disappear so Ill let you know if it does.... the pics that were visible from other users when I first made this post have since disappeared from the news stream and unity pages, but are fine on the user profile.
·
Friday, 24 January 2014 18:57
·
0 Likes
·
0 Votes
·
0 Comments
·
Hm, that's odd. If it has already been uploaded to Amazon S3, it shouldn't dissappear unless Amazon removes it?
·
Friday, 24 January 2014 22:53
·
0 Likes
·
0 Votes
·
0 Comments
·
Further testing has shown that the disappearing trick happens to about 95% of photo uploads by my users. There seems to be no pattern as to which pictures it is. It does not seem to be related to Amazon S3, although it appears that the Remote storage feature of EasySocial does not work properly either - I will open another ticket about that.

So right now, my Newstream is an ugly mess, filled with empty boxes and 'broken images' links.
So far, I have not found your support very helpful at all. Is there someone who can actually make some helpful suggestions?
·
Sunday, 26 January 2014 16:08
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Rod,

Please provide us with the FTP access and also the login credentials that has such issues. The account that you provided to me does not seem to face with such issues, so I have no idea how to really trace back the problems.
·
Sunday, 26 January 2014 20:45
·
0 Likes
·
0 Votes
·
0 Comments
·
Hi Mark

It did seem random and somehow did not affect that account, but I think I have solved the problem.

After I did the research that led to my ticket about S3 behaviour, I realised that the erratic behaviour of the S3 feature probably was causing the problem. I disabled S3 remote storage since its pretty pointless anyway if the local files remain, and now the news stream photos are behaving correctly. It may yet change, but at this point it does seem that the remote storage feature is not working correctly for me (eg it was moving some users' pictures but not others).

I was wondering if it could be related to the various caching services on the SiteGround site?

I must say I am a little concerned with the instability of EasySocial, it seems like its still a beta product to me - I could list lots of other issues to do with not recognising privacy settings, for example - but I do hope you will take issues like mine seriously and get those components working correctly considering the cost of EasySocial almost matches much more mature products on the market.

Thanks
Rod
·
Sunday, 26 January 2014 21:06
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Rod,

Thanks for getting back to me on this. I do take every single issue seriously especially with EasySocial since the product is still in its early stages. If you take a look at all the forums posts / tickets (not sure if you can view them) but every single issue that we found in EasySocial has been resolved (Provided that we are able to reproduce the issue). If we can't reproduce the issue, we are actually trying to fix something and we are blindfolded

I am really not sure what is wrong with the remote storage functionality on the site and there could also be a possibility that the files didn't get transmitted to Amazon but I am just speculating here unless I am able to reproduce the exact issue.

Thanks for understanding Rod.
·
Sunday, 26 January 2014 22:55
·
0 Likes
·
0 Votes
·
0 Comments
·
I do appreciate your hard work and dedication, and Im fully aware of how hard it is to pin every strange behaviour down, no worries
I just want you to have the info for future ref re S3 and possible problems with stream updating.

Thanks for everything,
Rod
·
Monday, 27 January 2014 00:13
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks for understanding Rod, appreciate it very much.
·
Monday, 27 January 2014 01:47
·
0 Likes
·
0 Votes
·
0 Comments
·
Hello Rod,

Just to let you know that I did not gave up and I believe I have found the problems and I think this should fix your issues that you are having with the photos on the stream. Can you download the attached file and upload it into /media/com_easysocial/apps/user/photos/ and overwrite the photos.php file?

Here's what happened, we actually cache the stream so that there will not be too many SQL queries that get's executed. When you upload a new photo or profile picture, what happens is that the photo data is stored in a params column so that later when populating the stream, we don't need to run another sql query just to fetch information about the photo.

However, this plan seemed to backfired us because that data that is stored in the params column is still thinking that the storage is stored in Joomla. I am trying to find another work around for this whilst still be able to optimize the SQL queries on the site. But this temporary solution should fix issues with the stream.
·
Wednesday, 29 January 2014 23:17
·
0 Likes
·
0 Votes
·
0 Comments
·
Thanks so much Mark, I'll do that and test, and confirm if the patch works.

Regards
Rod
·
Wednesday, 29 January 2014 23:37
·
0 Likes
·
0 Votes
·
0 Comments
·
No problem Rod! I am sorry for this delay and thanks for your patience.
·
Wednesday, 29 January 2014 23:48
·
0 Likes
·
0 Votes
·
0 Comments
·
View Full Post