Using IMM with existing Xataface install

[aidan]

[shannah]

[aidan]

[shannah]

[aidan]

[neotrode]

This old thread helped me a lot. However, could you guide me to refining this a bit more?
It would be nice to have the following features:
- Uploaded image is saved to the folder in original size but the filename is appended with an aribtrary 10 digit number to avoid duplicate filenames overriding the previous file.
- An automatic copy of the image file is saved at a reduced size

When coded, maybe with a parameter in the fields.ini like this:
[image_file]
Type = container
widget:type = file
allowed_extensions = jpg,png,gif,jpeg
savepath=files/photos
url=files/photos
appendrandomname=10
makethumbnail=yes
thumbnailsize=200x200

Any chance you can offer some guidance on this?

Thanks in advance.

-Frank

[shannah]

Depending on your needs, this may not be necessary. Xataface already provides collision protection for file names. And doesn't delete files unless you manually do it. You can test it out... upload a file twice... you'll see that the second one has a number appended to the name and the first one will still exist on the file system.

-Steve

[neotrode]

Thanks Steve. I should have given it a go and see what happens rather than assume. I like it. It does the job as you said.
What about the thumbnail feature. Is there a way to make it a parameter call in the fields.ini. This way two copies are kept. One with the original filename (or extended name with the extra numbers), the other with a prefix to it like "thumb_". Or...Simply have the same filename and save it in a sub folder called "thumbs". Either way, it would be nice to simply have a call in the fields.ini.

How easy is it to create new parameters in the fields.ini and link a function to it? I guess that is my question.

[neotrode]

Ah! I found it. I could add the duplicate file and resize it code (to make thumbnails) by adding the code to the afterSave() function of the ImagesBaseClass.php in the "tables" folder. Brilliant!

[shannah]

Glad you got it to work.

For the sake of others who may want to do the same thing, can you post the afterSave() method (or at least relevant portions).

-Steve

[neotrode]