Why call this deprecated? Can you really forcibly abandon a module in Drupal? Don't you really mean "Looking for new maintainer, as I'm giving up on this" or something? This doesn't seem right to attempt for force people to do tons of work to make their site use a different module completely. The other module has dependencies people would have to install as well, and its dependency has even another dependency! Sheesh.

Comments

lucuhb’s picture

lucuhb commented

As Gregarios says, FileField source has lots of depencies, and after test, this module doesn't have the same functionnalities . For exemple, IMCE with FileField does not have all the buttons it is entitled to according to the profile of the user.
Why do you say that Imce image is deprecated ? Is there a security problem or anything else ?

gregarios’s picture

gregarios commented
Title: Deprecated? » Why Deprecated? Please search for new maintainer.
gregarios’s picture

gregarios commented

FYI I've opened this issue: http://drupal.org/node/1005548

donquixote’s picture

donquixote commented

Ok, I might jump on the boat and become a maintainer.
(still would be happy about someone else to join)

General idea:
- with filefield sources, every file should have an associated db entry in the files table. This is how filefield sources is supposed to work, although I have my doubts that it really does.
- with imceimage, files should live outside of the files table. I have not looked too closely into the code of imceimage, but I imagine this is how it works, does it?

These two philosophies can live in parallel, if the folder structure is clearly separated. Each approach should have its turf.

lucuhb’s picture

lucuhb commented

Thanks donquixote !

See #1006108: IMCEImage for multi-elements field which allows to add several images together for multi-elements imce image field.
I think this feature may be of interest to be integrated in the module !

gregarios’s picture

gregarios commented
Status: Active » Closed (fixed)