The space character causes imagecache to create a directory with space, which to my surprise actually works but imho is prone to break. Also, the img tag gets class="imagecache-Original size imgupl...." which is broken for real. I don't know how this could be fixed, probably if you want to handle the readable names within wysiwyg_imageupload, you should handle them there and provide some spaceless IDs to imagecache.

Comments

eugenmayer’s picture

eugenmayer commented

This will be fixed in BETA5 completely, as Images become Nodes (image entitys) and every use of an image in a node will be a "image entry" in its one relation table. So all those parameters are saved in a table, not passed by GET anymore. The new DB layout will be

File <1:1> Image entity <1:n> Image entry <1:1> Content node

I will use the not-readable name for the presets from now on. Thank you for all the testing and patches!

tuffnatty’s picture

tuffnatty commented

Images become Nodes (image entitys)

Why is this needed? image.module does it like that, too, and this is IMHO too heavy. The whole reason why I liked WYSIWYG image upload, was that it does not store images as nodes, does not use CCK imagefield, and nevertheless stores all needed info about image-node relationship. Also, AFAIU in D7 this approach (images as nodes) is also being dropped.

eugenmayer’s picture

eugenmayer commented

Well as i see there is some dicsussion needed, i opened that issue regarding the new backend :

http://drupal.org/node/694620

I would be very pleased if you give me your arguments there and read about mines. The idea of those entities / entries was not a "non thought about it one".

eugenmayer’s picture

eugenmayer commented

To come back to the issue here, using the machine names is critical and will be implemented

eugenmayer’s picture

eugenmayer commented

Well iam using the machine name now. That "space" bug is actually a bug of imagecache. So i will move it over after we are finished here.

*Update*: Well i guess this is not very critical, as using imagecacheui, you only can have numeric persetids ( machine readable ). Only programmatically created ones are in danger when they use wrong ids (as i did with original..fixed though). So its more a "wrong implementation"

Fixed in BETA5

eugenmayer’s picture

eugenmayer commented
Status: Active » Fixed
eugenmayer’s picture

eugenmayer commented

Eventhough this one is fixed by giving the original size image cache a different name, i cant use the "ID" of the preset..as imagecache is using the descriptive name for folder names...no idea why.

eugenmayer’s picture

eugenmayer commented
Status: Fixed » Closed (fixed)