I also want to keep the original file names.
It is important to know exactly which image is published when you have hundreds of pictures catalogued with their file numbers.
I recently purchased Montage2 Stack, very good but I know I will never use it because it changes the names of the files.
Using Adobe Bridge I can edit the metadata of an image but I don’t know how much SEO value that has. Since the title and alt tags is an html thing and not inherently part of the image, I guess I am hooped until this bug is fixed.
Any progress on that???
So if an image is warehoused, how would that add the alt tag?
Trystero,
From what I understand from this thread, it is not your stack causing the problem but actually a bug with Stacks 3 that will affect any stack.
I just wanted to follow up here and see if there was any sort of ETA on a fix for this. Thanks!
I emailed Yourhead last week about this and got one reply saying pretty much the same thing. “Harder to fix than they thought it would be”. I replied again with frustration that this has been an open issue since last August and it’s ruining the SEO for many of us. No reply to that email. Sort of feels like their going “dark” on us.
@jgoodnough – sorry you didn’t get a reply. we reply to all email and try to get back to everything within 24 hours. i’m not sure what “go dark” means here – but i’m pretty sure that’s something we’d never do. 
we’ve known about the naming issue for a while, but (to the best of my knowledge) it was very limited to just a specific type of image. and we’ve tried to help people find workarounds to navigate safely around this issue.
although we started work on this earlier, the bug concerning this was filed on Dec 4th. our bug history is always open to the public and you can comment/submit/etc here: https://github.com/yourhead/s3/issues/522
we planned on releasing a fix to this along with a more significant overhaul of the image library for speed and memory efficiency. that was scheduled for Stacks 3.1 next month.
then came the SEO tidal wave… 
a couple SEO tools started flagging this (among other things) as a serious problem (IMHO perhaps enflaming it a tiny bit). we’ve tried to help folks work around the issue who have asked, but decided it would be a very good idea to release the fix for this bug sooner rather than later.
the update for was posted for this two days ago, unfortunately i’m not allowed to link to it here on the forum. but if you’re following us on twitter, check our blog, or any other places, you should be able to find it.
but, the fix for this is in beta. the beta is public. and we’ve gotten several reports back that it both fixes the known problem (unscaled images do not honor their user-specified names) AND also improves naming of transformed images in 3rd party stacks.
i would highly encourage you to download it and give it a go and please do tell us what you think or file new bugs.
thanks,
isaiah
2 Likes
Thanks Isaiah. I appreciate your response and the effort you’ve no doubt made to resolve this. I will grab the beta and keep my fingers crossed.
beta 4 is out now too. more updates and fixes. if all goes well this will be the final beta release and we’ll shoot for a final release Friday
2 Likes
Hot dog, this seems to be fixed! 
1 Like
Stacks 3.0.5 was released yesterday (which is mostly the same as the beta that was posted last week). You can read more about it on the blog post: http://blog.yourhead.com/stacks-3/
You should see the auto-update notification the next time you launch RapidWeaver. Or you can download directly from our site. This update is free… enjoy!!!
If you’d like to keep up with other Stacks news and releases they’re always posted here: http://www.weaver.news
2 Likes
@isaiah The release notes link appears to be broken
@tevpot - good catch. typo. fixed. thanks!
Hi Isaiah,
I’m using RW 7.0.3 and Stacks 3.1.0 and it seems the issue is still there…
Hi,
I just retested and it seems to be working for me. Can you tell me exactly what you are doing (what steps)? What type of image? Can you test on a simple page with just an image and see if that works by itself? It may be quicker to figure out the problem if you email me at support@yourhead.com, but we can try to figure it out here if you’d rather.
Christi Carew
YourHead Software
http://www.yourhead.com
1 Like
Hi there,
Seems fixed now, I can’t reproduce the problem now after updating to 7.0.4, false alarm I guess 
1 Like