Therefore imagecache is unable to find the targeted file to cache when an incomplete path is passed to it as an argument to the menu callback. (If the file has a an ampersand in it's name).

The tranliteration module resolves this issue handsomely by removing characters like ampersands from file names before writing them to disk. This patch introduces a dependency on transliteration module. This fixes the bug in an elegant way.

How come? This is a major bug in imagecache. It's not reasonable to expect end users (let alone developers) to know that they need to remove ampersands and non-latin characters from filenames, and filenames with these characters are common enough in all languages that it's likely the bug will be encountered on most sites.

> perhaps we should just add a link to it from the imagecache project page.

IMHO this is not a good solution, because it admits that imagecache is buggy yet forces the IC user to search for the fix themselves (even though the fix may apparently be obvious), when the bug could easily be avoided in the first place.

It's obvious to anyone who actually read the available information that the Transliteration patch was applied to the dev version, and temporary roled back before the Beta (security) release, than put back in again.

So this bug should really have stayed closed as it has nothing to do with 6.x-2.0-beta10, but... if we now should be nitty gritty pedantic, it should say on the project page for dependencies:Install and enable Transliteration module (dev version only)

possibly with a note it's recommended for others. I don't know what went round in the head of drewish but I can guess he didn't want to add it as it would have mock up things for those who have a beta installed but not Transliteration, taking into account the beta is the currently recommended version and as such sort of expected to be "stable", while using dev you sort of expect odd things as a sudden dependency happen. Now anyone using the beta can take action and install Translitteration and be prepared for the next step w/o sudden surprises.

So setting this back to dev and Documentation for the dev note above to be added on project page.