Directory not created automatically for save() method

[pechitook]

Hello guys, thank you for this amazing library. I am using its integration with Laravel 4 and it works wonderfully.

I encountered an error when trying to save an image to a directory that did not exist. It is not a permission problem, it is just a feature that is missing: create the directory first if it does not exists. Maybe its an easy fix, but I don't feel comfortable enough to modify the library myself...

Hope you guys can take a look into it for a future release.

Thank you!

[olivervogel]

I am undecisive about this. It seems practical, if the save method creates directories automatically but on the other hand I think it's bad practice, if an Image class messes around in the filesystem.

[Fractaliste]

Maybe let the choice to the developer with a config option and a default value?

[olivervogel]

I think it's bad practice.

Use mkdir to create directories (recursively).

I want to keep it simple, creating directories automatically may cause confusion.

[martinandersen3d]

Suggestion: Please add a flag in the intervention configuration, so the developer can decide if he want intervention to create directories?

[websitevirtuoso]

+1

[DrCod3r]

indeed i need this too