Would it be possible to change the image file names to the title (alt tag).
Example:
The Title is: Another great picture
instead of generating something like:
4884.jpg
it would be better to get:
another_great_picture.jpg (or another-great-picture.jpg)
I keep reading that the filename is important for ranking on Image Search. I think this feature shouldn't be too hard to implement, seing that the filename is already generated automatically and the alt tags too.
That would be a killer feature.
Andre
Comments
Comment #1
vhmauery commentedNo new features for 4.7.
Comment #2
andre75 commentedAlright then, I changed it to version 5 :-)
Comment #3
vhmauery commentedIn Acidfree 5, the images already retain their original filename. So if you upload files as "my dogie in georgia.jpg" or "kitty_in_france.jpg" they will be stored just like that. Changing the title of the image/video, however, does not change the file name. So if you uploaded "kitty_in_france.jpg" and it's title was "Kitty in France" and you changed the title to "Kitty in Paris", the image would still be kitty_in_france.jpg.
If you want to go farther into this and have nodes rename their files when you change the titles, you will have to file feature requests with Video and Image modules individually, since Acidfree 5 is more about node management and less about file management.
Comment #4
andre75 commentedThats good enough. I just have to upgrade to Drupal5 / Acidfree5 and a bunch of other modules.
How does Acidfree handle it if already have kitty.jpg in the album and try to upload another kitty.jpg?
Andre
Comment #5
vhmauery commentedInternally image and video use the drupal core file api. They add the files using the rename option, which will append a number to the filename and increment it until it is unique. Continuing the example, this would give you kitty.jpg, kitty_1.jpg, kitty_2.jpg, etc. I am not positive on the numbering scheme, but suffice it to say that they will have unique filenames.
Comment #6
andre75 commentedSounds good. Just two more question:
Is it a push button upgrade from 4.7 (will all my previous structure be fully supported)?
Can I still limit the number of files per directory?
Comment #7
vhmauery commentedHehe. Pushbutton, eh? No, but nothing that is worth anything is pushbutton easy. :) I can't say for sure whether or not you structure will be preserved. But with a site as large as yours, I would certainly be interested in seeing the results of an upgrade (in a sandbox of course!). All the previous structure _should_ be preserved though.
As for limiting the number of files per directory, this feature is not available as a built-in part of the drupal files api. I will be the first to admit that the files api is somewhat weak. That is part of the reason I went with filemanager. But neither Image nor Video modules use filemanager -- they both use the core files api. What are your concerns with too many files? From what the ext3 filesystem developers I know tell me, this is no longer a concern with modern ext3 filesystems. Now that they use a btree rather than a list or an array to store the directory entries, it is not a real issue. Searching times are now O(log2n) rather than O(n). If your concern is simply manageability of that many files, I don't know what to tell you, but to be truthful, the way filemanager broke the files up was even less intuitive than a flat directory structure.
Comment #8
andre75 commentedWell, by pushbutton I meant pretty much what you concluded. A way to make it work without me having to redo the entire site.
My concern is, that although I am hosting on a VPS now, there is a limitation on the number of files allowed per directory.
I don't exactly remember what it is, but it was a number that is not unrealistic for a large number of Albums.
In either case, it should also be usable to people on shared hosting accounts and all I know impose a limitation as well.
That said, I don't think it would be impossible to move files on the unix level and run a little script on the database itself to update the locations in the database tables, so its not inherently bad, just something that is good to know.
While I am telling you all my wishes, I have noticed entire Albums go supplemental on Google. I have traced it back to this issue:
Lets say I have one album that is split into multiple smaller ones (via pagers).
So I get:
http://www.example.com/album1.html
http://www.example.com/album1.html?page=1
http://www.example.com/album1.html?page=2
Which essentially have the same title and content (except for the pictures themselves). I was wondering if there is a way that lets me stick some unique text on each of them, independent of the other.
Yeah I know, I am always nagging. Just something to think about.