Response Time
24 — 48 hours
I recently swapped my photos from "/media/com_easysocial/photos" to "/gallery" as well as the avatars to simply "/avatars" via the ES storage configuration. I moved the files over to the appropriate directories, cleared my browser cache and everything displayed as it should. 
I looked into the database table "_social_photos_meta" and saw that the value column attempts to use the full path. A value example is "/media/com_easysocial/photos/4/5/ed65b451e9f39a0933c73544204f32f5_original.jpg". However this does not seem accurate. The image is being accessed through the new path which is "/gallery/4/5/ed65b451e9f39a0933c73544204f32f5_original.jpg". Because the old path is now deleted, if the entire path was actually read it would not display the image at all. But instead images are loading just fine.
Screen shot of the _social_photos table.
What I'm getting at is that the root path is being ignored which makes me question why the entire path is being written in the first place. The table "_social_avatars" uses perfect form in my opinion. It also produces way less records based on it's structure (1 record per image rather than 6 just to reference the image paths).
Screen shot of the _social_photos_meta table.
Basically I'm looking out for the infrastructure of ES to save you guys and us headaches in the future. (performance wise/potential complaints in the future) In this case it's about saving space where useless information is being stored. Also I'm a bit concerned about the gallery structure in how 6 records are used to access a single image. Why not use the same method as the avatars or at least one that requires accessing less records for a single photo?
I'm still very happy with how the gallery operates from a user point of view. Hoping all is well with the stacked team and wishing you all a happy new year.
I looked into the database table "_social_photos_meta" and saw that the value column attempts to use the full path. A value example is "/media/com_easysocial/photos/4/5/ed65b451e9f39a0933c73544204f32f5_original.jpg". However this does not seem accurate. The image is being accessed through the new path which is "/gallery/4/5/ed65b451e9f39a0933c73544204f32f5_original.jpg". Because the old path is now deleted, if the entire path was actually read it would not display the image at all. But instead images are loading just fine.Screen shot of the _social_photos table.
What I'm getting at is that the root path is being ignored which makes me question why the entire path is being written in the first place. The table "_social_avatars" uses perfect form in my opinion. It also produces way less records based on it's structure (1 record per image rather than 6 just to reference the image paths).
Screen shot of the _social_photos_meta table.
Basically I'm looking out for the infrastructure of ES to save you guys and us headaches in the future. (performance wise/potential complaints in the future) In this case it's about saving space where useless information is being stored. Also I'm a bit concerned about the gallery structure in how 6 records are used to access a single image. Why not use the same method as the avatars or at least one that requires accessing less records for a single photo?
I'm still very happy with how the gallery operates from a user point of view. Hoping all is well with the stacked team and wishing you all a happy new year.
11 Replies
The replies under this section are restricted to logged in users or users with an active subscription with us
