Justified and Masonry error 
Auteur : John P.
Visité 1462,
Followers 1,
Partagé 0
After trying to load a Justified Gallery, half of the pictures change orientation
I have double checked the files in the forlder and they are correct.
This is also happening to the Masonry Gallery Widget.
I am on X5 20/ 1.7 PC
any help would be wonderful
Thanks in advance
Posté le
Just a longshot:
Restart pc, do a full upload, goto website, press F5, then check if it is solved.
Auteur
Hi Andre
Once again we meet. Alas the project is offline. I saved restarted reloaded but still the same error.
In the basic gallery there is a preview pane and possible to turn pictures, which is not available in the newer gallery's....
So not sure now, and am stuck, maybe i will put individual pictures on the page.
Once again
cheers John
John, I recently had this issue and the only way I found to correct it was to open each problem picture, rotate it and save it (new name) and then add it to the gallery.
I used Irfanview (free) https://www.irfanview.com/ and on a few took the opportunity to crop the original.
In an ideal world Incomedia would add an edit option to each picture (or at least a rotate), but this is the same people who make us look at generic images when laying out the gallery, these should be thumbnails of the chosen images so we don't have to resort to preview to see how it looks (as in an earlier release).
Auteur
Hi Esahc.
Thanks for the info, my problem is that iw alway make sure the pictures are correct before i use them.
maybe as you say it is a naming issue!
I will give it a try
thanks
John
Auteur
A quick update
After info from Andre and Esahc, they have once again solved my problem.
Solution: so i did not need to rotate any images, instead I just renamed them ie: G1 G2 etc for the project
re-loaded and became correct in gallery and preview.
So at the moment all load correct.
Thanks Guys
How very odd! So I may not have had to rotate my files, simply rename? I will try find where I did this because if this is the case it sounds like a bug. I was assuming that somehow embedded meta data in the image was causing the mischief. Many thanks John.