I am new to moblog.
I am trying to set up a travel blog that I can send an email to which contains 3 different fields.  For example: Travel_date, Travel_location and Body.

I would like this information to get added to the blog in the proper field.  I am adding this line to my email: {field:travel_date}July 10{/field:travel_date} - assuming this is the syntax for adding information to a specific field.

When the blog is posted this information is posted as text instead of being entered in the proper field. 

Could someone explain how I can extract specific informaion from my email and have it posted to the proper location in my weblog?

Thanks for the help.

Summary:
  -AIM: Get Moblog to parse emails properly, grabbing several custom fields, and putting them in the appropriate weblog fields.
  -PROBLEM: Moblog only seems to see the entry title, and one of the fields.

Yackbladder: first things first - sorry that you probably got a notification about this post, clicked the link excitedly, and noticed that it doesn’t answer your questions (it just poses it again, with more crap in it this time )! I thought maybe with more info, someone could solve both our problems.

I’m having a similar problem: I have four custom fields in my weblog, and have set up the fields in FreeForm, to email them to a moblog address in hopes of the data being entered into the weblog via the moblog email (all because the SAEF wasn’t validating well enough on the server-side ).

Anyway, initially it was getting the main custom field (‘offense’), but leaving a bunch of the {field… codes at the end. What should have been displayed as the text of the offense field instead looked like this (Yackbladder - yours was the same, I’m guessing):

This is the example text for the submitted offense field
{field:witnessemail format=“none”}{email}{/field:witnessemail}

{entry_title}{title}{/entry_title}

{field:offensesite format=“none”}{offensesite}{/field:offensesite}

{field:offense format=“none”}{offense}{/field:offense}

It wasn’t collecting any fields other than ‘offense’ (but it did work with {entry_title}). I stopped this appended code finally, by changing the default moblog field to “none” (it had been set as ‘offense’).

At this point, it collects the ‘offense’ field correctly (without the field codes below—hooray!) and it gets the entry title properly, but it leaves the other fields blank.

Since the email is sent with FreeForm and requires authorization, the emails are set up to look like this:

AUTH:my_username:my_password

{field:witnessemail format=“none”}{email}{/field:witnessemail}

{entry_title}{title}{/entry_title}

{field:offensesite format=“none”}{offensesite}{/field:offensesite}

{field:offense format=“xhtml”}{offense}{/field:offense}

And the problem doesn’t seem to be on the FreeForm end, because the emails come through as expected like this:

AUTH:PSNP:fakepw

{field:witnessemail format=“none”}admin@psnp.com{/field:witnessemail}

{entry_title}This is my title{/entry_title}

{field:offensesite format=“none”}This is the location.{/field:offensesite}

{field:offense format=“xhtml”}This is what happened: ... .{/field:offense}

So at this point, the question is, how can I get moblog to stop ignoring the other fields??

I hope this post was clear, despite its long-windedness. Thanks to anyone who can help (or anyone who bothers reading)!

I figured it out (i.e., putting data from a FreeForm web form into a weblog—no photos/files, sorry!—with custom fields parsed properly). So for anyone who’s wondering, here’s how I did it. (I’m not paid by EllisLabs, so this ‘tutorial’ might be a bit light).

You’ve got your custom fields (mine are witness, witnessemail, offensesite, and thatoffends). ALL OF THESE FIELDS have to be set as textareas (in “Field Type” under CP > Weblog Admin > Custom Fields > Field Groups)—see here for documented proof; it’s in a red box! The good news is, FreeForm can display text inputs to the user to get the data.

So this is my moblog template. It requires authorization; hence the first line. Also (as a newbie this confused me), the FreeForm email template has to be different: IN THE MOBLOG TEMPLATE, the data is represented by “{text}” between the field tags. Not so in the other template.

Now, if you’ve installed FreeForm from Solspace, you can set up an email template (CP Home > Modules > Freeform > Manage Templates). Whereas the previous template tells EE how to interpret the email to the moblog address, this template tells the form how to send data in a way that EE can interpret. My FreeForm template looks like this:

NB: it looks similar to the other, but it’s different. The field tags are identical, but between them, it no longer says {text}. Instead, it says {author}, {email}, {body}. It doesn’t really matter what these say. These are the names of the FreeForm form fields.

My FreeForm form looks like this:

All the visible form elements have class=“required” because I use javascript to validate the form fields’ contents, using this nifty tool (and advice for implementing it in EE here)—the styling can still be accomplished with id=”“, and without this js there’s no need for class=“required” or for the form_id parameter in the FreeForm tag. It is not necessary for the moblog/FreeForm integration.

There you have it. User enters data into FreeForm. FreeForm formats it and emails it to my moblog address. EE checks the moblog address for emails with the username and password at the top, and parses the form data into the correct custom fields.

Magic! Tedious, time-consuming magic! Hopefully it’ll be less tedious for you readers.