The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I create a Drupal 7 version of this module. You can find a first version attached.
Major changes:
- Drupal 7 Field API Compliant,
- exif_helper submodule is no more needed,
- Taxonomy Support by supporting several field types
- text field : same functionality as Drupal 6 version
- term field : add term to a chosen vocabulary following metadata (exif & iptc) structure.
- Content Translation support (if image are locale specific, metadata should be)
Note that I could not create a patch from the branch of Drupal 6 version as it seems you are working on a new submodule (exif_location) so i attached a full exif module.
My TODO List:
- make image field to use selectable by configuration,,
- make vocabulary structure optional (flat vocabulary),
- better handling/formatting of iptc/exif fields,
- create hooks/API so that managing new type of fields could be done by creation of new module (and not with a patch or issue :) )
| Comment | File | Size | Author |
|---|---|---|---|
| exif-7.x-1.x.zip | 63.29 KB | jphautin |
Comments
Comment #1
rapsli commentedI was just thinking about a D7 version for this module. Next time I'll get around I'll take your code and commit it to head, so it's easier for people to test it. Are you interested in maintaining the D7 version?
Comment #2
jphautin commentedIt will be a pleasure. Thanks for the offer. What I have to do ?
Comment #3
rapsli commented@David: since this is your module, is that ok with you?
@jphautin: Do you already got a CVS account?
Comment #4
jphautin commentedNo, I does not have a CVS account.
Comment #5
rapsli commentedSign up for a CVS account: http://drupal.org/cvs-application and point them to this issue here.
Comment #6
avpadernoI have sent an email to the current maintainer.
Comment #7
jphautin commentedHello,
I does not know if I must do something to make us go ahead on this issue ?
Comment #8
rapsli commentedSo do you got CVS Access?
Comment #9
avpaderno@rapsli: I would much prefer to give jphautin a CVS account (for which he must apply, though) if the maintainer, of any of the co-maintainers explicitly report if they accept his offer to become co-maintainer.
Comment #10
rapsli commentedyes. It's oky, if jphautin get's access to commit
Comment #11
avpaderno@rapsli: Thanks for your answer.
Now jphautin needs to apply for a CVS account, as it is not possible to give a CVS account without the user applies for it; that must be done for the user needing it, as it is not possible to require a CVS account for another user.
@jphautin: follow the link reported in http://drupal.org/cvs-application/requirements.
Comment #12
jphautin commented@rapsli : Thank for your answer ! ;)
@kiamlaluno : I does not understand why you ask me to create a new CVS Issue as I have already done one at http://drupal.org/node/701660.
regards,
Comment #13
avpadernoNever mind; I was not able to find it, but that was because I was not looking into your tracker page.
Comment #14
avpadernoFYI, I approved jphautin's application, and granted him access to this project repository.
Comment #15
jphautin commented@kiamlaluno : Wow ! Thanks to reply so fast
Comment #16
jphautin commented@rapsli : I test my CVS Account on the module successfully :)
I see there is no DRUPAL-7--1 Branch. I do not want to create it from HEAD before You think it is the good day/time to do it ( as you were working on new submodule, I think you should have time to stabilize your code before the creation of the new branch, no ?). What do you think about ?
Comment #17
jphautin commentedComment #19
david lesieur commentedSorry for the lack of feedback. I was away for most of February and have not yet caught up with everything. Glad that you guys went forward anyway!
Comment #20
rapsli commented... that's opensource ;)
Comment #21
david lesieur commentedTotally! :)