First off, great module! It is almost exactly what I am looking for to expand the functionality of Mailhandler. I see on your todo list that you are planning to extend MMB's capabilities to also handle video and audio as well as being able to process multiple attachments which is great.
I've been using MMB for most part of today, and as far as I can see there are only a few things I would like to see added so that
1) Node Type: Currently when submitting an image attachment via Mailhandler/MMB the content type is set to image, regardless of what you have set it to. The main reason I will be wanting to use MMB is to be able to submit articles (story content type) which will have multiple images per article.
2) Placement of media in Node: following on from my last point, once you get to the stage of adding multiple images per submission it is vital to be able to control where those images are placed in the node. This is especially so in the case of writing articles as you might be directing users to look at a particular image. What I would like to see is being able to place some MMB specific tags in your e-mail to instruct MMB on how and where it should place a particular image. For instance, something like;
[mmbattachment_name:image.jpg][mmbtype:image][mmbtaxonomy:windows,linux,operating systems][mmbposition:center]
- First tag specifies the attachment name
- Second tag specifies the content type
- Third tag specifies the Drupal taxonomy the attachment should be filed under
- Forth tag specifies the horizontal alignment of the attachment in the node
I am happy to help sponsor such functionality, as well as contribute with writing documentation and support.
Comments
Comment #1
sanduhrsAs far as I know it is not possible to attach an image to a node->type other than "image".
There's an issue for audio-type nodes http://drupal.org/node/55654 , which addresses this.
A workaround could be, to create the image-node seperatly if a different node-type has been defined, then inserting the images preview into the body. This could also make posting multiple files possible.
The BBCode-style tags are a nice idea, I'll consider it, when it comes to multiple files.
Thanks.
Comment #2
brashquido commentedI think your workaround suggestion sounds perfect. Is this something you'd consider taking on as a sponsored project? I am going to have very limited access to Internet for an extended period of time later this year, so being able to manage text and images via e-mail are going to be vital to my workflow as I may only have a few minutes of Internet time to submit 10 or 20 articles to my sites.
Comment #3
sanduhrsMy priority list at the moment ist:
1. audio support
2. video support
3. multiple attachments.
If you decided to sponsor (or to organise sponsoring) the multiple attachement thing, it would go to 1.
At the moment Stuart is doing some work on extracting multiple attachements, but he' still working with his mailhandler modification on 4.6.
Note: I'll be offline a few days - probably until tuesday.
Comment #4
brashquido commentedGreat. I would be very interested in looking at sponsoring this, so I'll get in contact with you next week if that is ok.
Comment #5
Stuart Greenfield commentedI must remember to read first - post second. I have got working code for extracting all files from a message body - posted under separate request here.
Thinking out loud...
The code retrieves all attachments in to an array, jpeg, zip, audio etc. If you know the order you attached your jpegs maybe could use an index number in the BBCode?
Also, I wonder if it is possible to trigger a separate save for each image, creating a series of image nodes, and then create a final blog node that ties it all up. That way you could use image to generate thumbnails that could be recycled elsewhere in the site. Could also then choose to use thumbnail or preview size in the final post?
OR, could cheat - call image to generate thumnails, seeing as it has the code to do it, then fetch the thumbnails back (they'd be stored under files/image/temp) and put them in an mmb folder. So let image crunch, but don't generate a node for every file.
Just some thoughts!
Comment #6
sanduhrsBy now this issue has been solved by the pearwiki_filter module [1]
Closing.
[1] http://drupal.org/project/pearwiki_filter
Comment #7
sanduhrsSorry, I ment the inline module [1].
[1] http://drupal.org/project/inline