Eightkill wrote:it could be a workaround indeed :) , but you have to admit it's weird for an anonymous visitor to see a picture with all EXIF information he does not care about and should not even see, instead of having a pleasant UI you desperately configured and only getting the HTML Gallery version :)
Perhaps, but have you tried the concept of "Sharing Images" from any other website? Like any other website, it will share a unique URL for the image specifically. When the link is opened, it will show THAT image. It can't possibly link to the parent gallery URL, simply because that is "wrong".
Even Facebook itself works like this. If I SHARE a link to an image (or open in new window, which is technically the same), the link will represent the image only, outside it's gallery context. Example:
Facebook Coca Cola image
Furthermore, there is actually a small bug in X3.22. But in new version X3.23.0, when a shared link is clicked in X3, the visitor will initially see the image in the POPUP. It would look like this:
When visitor CLOSES the popup, it will naturally show the image-landing page, as any other website.
Eightkill wrote:At least is it possible to remove all EXIF infos on this page or change the design to get close to the one in the gallery ?
Easiest way to do that, panel > settings > custom > Custom CSS:
.x3-file .meta {
display: none;
}
Eightkill wrote:I tried to changed some files without any success, i tried to modify exif_reader.php, exif_reader.bac and module.gallery.html
Templates in X3 are pre-rendered now, so that wouldn't work. Besides, it would be bad practice to edit template files that get overwritten on X3 updates.
I thought perhaps we had an option to disable EXIF on landing page, but now I'm not sure. Will check for new release coming soon ...
Eightkill wrote:It's quite an important topic, because if people start to share things on social networks, they will keep getting HTML Gallery pictures, and it will be the main way to access the pictures, instead of using the very nice X3 features that you worked so hard to create, thus the traffic on the website going in a way it was not intended to at start, killing the experience :s
Really no way to fix this though. The image landing page needs to be a unique page for the image, with unique page <title>image title/name</title> and text-content, which specifically represents the image. Not only for sharing, but for sake of SEO. We can't redirect it to the parent gallery page ... Even if we could hack it to redirect, that would involve tricking Facebooks robots to NOT follow the redirect. Facebook wants to know exactly WHERE a link goes to, so it uses humanized robots (with javascript) to find where a page redirects. We don't intend to implement features that try to do things that are not meant to be.
This is how any other website that shares IMAGES directly on Facebook operates.