Entry Post is a plugin for Movable Type that enables visitors to your site to submit entries using a form. Visitors do not need a user account and they do not need to login. Similar to posting a comment, they can simply fill in a form and submit.
New features in version 2.0
Entry Post 2.0 contains the following new features:
- Native Field Support - This means that the EntryPost plugin now manages fields by itself, so you don't need to install CustomFields or any other plugin. You can use Entry Post 2.0 alongside other fields plugins -- there are no known conflicts.
- Extra Fields - In addition to the standard Name, Email Address, URL, and Image fields, you can now use Entry Post to submit extra fields "on the fly".
- New Template Tags - New tags make it easier to display information about the poster (and any extra fields) in your blog pages.
- Support for MT4 - Entry Post two can be used with MT 3.2, 3.3, and now 4.0. tested with MT4 beta5.
I have been using external forms and scripts to do this for several years. Examples include Mars Rover Forum and Seinfeld Forum. These MT-powered forums enable forum members to post new topics (entries) using an external form. Based on this experience, I have converted the entry posting script into a plugin -- and added a bunch of additional features.
Basic Features
- enable visitors to post entries to your blog
- new entries can be set to "Published" or "Unpublished" (pending admin/moderator review)
- supports TypeKey authentication (optional)
- entries can be scanned against MT's Junk Filters
- entries can be previewed before posting
- email notifications of new entry submissions
- entries can be added to a category (set a default or allow poster to choose)
- entries can be tagged (default list of tags, or specified by the poster)
- included default templates include spam-protected form
Advanced Features
- enable posters to upload an image with the entry
- other entry fields supported (Extended Entry, Excerpt, Keywords)
- option to disable rebuilds when an entry is posted
- option to disable entry creation (makes the form work as a 'contact me' form with email notification turned on.)
- xml response option
- support for extra fields defined by you
Try Entry Post Now
I have set up an Entry Post test blog that you can use to submit test entries. You can use one of two forms:
- Basic Form (default form installed with Entry Post)
- Advanced Form (an example form to demonstrate advanced features)
By using the forms above, you will quickly get an idea of the visitor experience with Entry Post. In its simplest form, it is very similar to posting a comment.
The Administrator Experience
Entry Post has been designed to be easy to install and configure. Simply upload the files, change some file permissions, then configure the plugin via the Plugin Settings for each blog. Required templates are installed with a single click (which can then be customized, if desired).
The settings area for Entry Post looks like this:


By using the above settings, you can configure most of the features of Entry Post.
Template Tags
New in version 2.0, EntryPost includes the following template tags that you can use to display information posted using the plugin:
- <MTEntryPosterName> - The name of the poster, as submitted in the "Name" field. If the name field it blank, the plugin assumes that the entry was not submitted via Entry Post, and this tag will display the name of the author of the entry. This makes it very easy to update your templates, simply replace the <MTEntryAuthorDisplayName> tag with the <MTEntryPosterName> tag, and it will "just work", regardless whether the netry was posted by an author or posted by a visitor to your blog.
- <MTEntryPosterEmail> - The email address of the poster, as submitted in the "Email" field. If the "Name" field is blank, this tag outputs the email address of the author. For privacy and anti-spam reasons, I don't recommend using this tag in your templates.
- <MTEntryPosterURL> - The URL of the poster, as submitted in the "URL" field. If the "Name" field is blank, this tag outputs the URL of the author.
- <MTEntryPosterIP> - The IP address of the poster. For privacy reasons, I don't recommend using this tag in your templates.
- <MTEntryPosterImage> - The relative path of the image uploaded by the poster.
- <MTEntryPosterLink> - Outputs the linked name of the poster. If the "Name" field is blank, it will display the author's linked name. Supports the same arguments as <MTEntryAuthorLink>.
- <MTEntryPostField> - This tag can be used to to display the value of any extra fields submitted using Entry Post. A single field argument is required, which should inlcude the name of the field, without underscores. For example, <MTEntryPostField field="Favorite Color"> would display the value of the Favorite Color field.
Advanced Use - Adding Extra Fields
Entry Post 2.0 makes it very easy to add extra fields. All you have to do is add the extra fields to the form. First, browse to Templates and then Template Modules and edit the 'EntryPost Form" module. Now add a field to the form in the following format:
<input type="text" name="entrypost_Favorite_Color" />
..and you are done! Note that the "name" argument above must begin with "entrypost_", followed by the name of the field. Use underscores ("_") instead of spaces, if the field name has more than one word. You can add multiple extra fields in this manner, and they will automatically be added to the entries posted, and displayed automatically on the admin Entry screen.
Requirements
- MT 3.2+ (Note: The tags and TypeKey login features require MT 3.3+)
Limitations
- Under MT 3.2, you will be able to see the Entry Post fields on the entry screen, but you won't be able edit them.
- Under MT 4.0, the Typkey sign-in feature doesn't work reliably. The next version of Entry Post will focus on support for MT4's native authentication system.
Installation
- Download the zip file and extract the contents.
- Upload the "EntryPost" directory (and all its sub-directories and files) to your MT 'plugins' directory.
- Change the file permissions to 755 (CHMOD 755) for the EntryPost/mt-entrypost.cgi and EntryPost/signin.cgi files.
- Login to MT and go to the 'Settings' area of a blog and choose the 'Plugins' tab. Then click the "Settings" link for EntryPost. You should now see the available settings for EntryPost, as shown above.
- Enable the plugin by checking the Enable checkbox, choose other settings, and the save the settings.
- Return to the EntryPost settings and install the templates by clicking the provided link. After the templates have been created, you can customize them, if desired, to suit your needs or match your site design. The primary template is an index template called "EntryPost Submit Page" - this page includes the form to post entries.
- You will probably now want to provide a link to the Submit Page from your main index. One way to do this is to use the provided "EntryPost Submit Link" widget (using WidgetManager). Alternatively, you can manually create a link such as <a href="<MTEntryPostSubmitPage>">Submit an Entry</a>.
Get Entry Post
Commercial License - $97
If you site or blog is for-profit, a commercial license is required. The license includes all future updates to Entry Post and priority feature requests.
Personal License - $33
For use on a personal site or blog, a personal license is required. The license includes all future updates to Entry Post.
If you would like to use Entry Post on a non-profit or charity site, please contact me.
Live Demo
If you are interested in purchasing EntryPost, but would like to try it first, that can be arranged. To experience the poster side of things, visit the Entry Post test blog using the links provided above. If you would like to login to see the admin interface, please contact me.
As always, feedback, suggestions, and product questions are appreciated. Please reply to this entry.
Note: - While Entry Post 2.0 includes built in support for poster fields and extra fields, it is not intended to be used as a general purpose "extra fields" plugin. Fields can only be added via the external Entry Post form. If you are interested in a general purpose fields plugin, there are several available, including CustomFields and RightFields.


Comments (20)
I've installed entry post and it worked great the first time with the exception of the <MTEntryPosterName> tag. Perhaps I'm not understanding the directions, but I though I could simply replace <a href="<$MTEntryAuthorURL$>"><$MTEntryAuthor$></a>
with
<a href="<MTEntryPosterURL> "><MTEntryPosterName> </a>
Unfortunately, the use of the latter does not provide an author for my prior blog entries.
Posted by tim | July 16, 2007 4:45 AM
Posted on July 16, 2007 04:45
tim,
That usage seems correct. It should work as desired. What version of MT are you using? Can you provide a link to your site (if you want, send it privately via my contact form).
Posted by Mark Carey
|
July 16, 2007 8:51 AM
Posted on July 16, 2007 08:51
Okay, here's a special one: Client wants submitters to be able to specify whether or not the post should accept comments. I get the impression EntryPost can get at any postdata field, but it's not obvious to me why the form fields get the name values that they do in order to specify those values. Can this be done?
Posted by Su | October 8, 2007 3:25 PM
Posted on October 8, 2007 15:25
Su, there is no way to do this currently, apart from editing the plugin code. The current version of Entry Post always uses the blog's default settings for allowing comments and trackbacks. It is a tiny code edit, however, for those sites who may want to override this behavior one way or the other (either always enable comments or never enable comments).
In future, I could add an advanced feature in which a hidden form field could be used to override the default setting. This would have to be used with care however, as people could submit their own version of the form (sitting on their own server) and set this field to turn on comments for their entries, etc.
Posted by Mark Carey
|
October 9, 2007 2:00 PM
Posted on October 9, 2007 14:00
Wrong answer!
Let's file this under feature requests, then. I can see how it could be a concern in and of itself, but the site I'm working on has every piece of content go through moderation, so the overriding isn't much concern. And really, anyone accepting outside content for immediate publishing is probably opening themselves up to much worse than comment spam, in my opinion.
Generally speaking, I'd always rather have options available with the ability/responsibility to turn them off than for things to just be impossible. Impossible makes me angry *grin*
Posted by Su
|
October 12, 2007 12:15 PM
Posted on October 12, 2007 12:15
Agreed, Su. I will definitely add this feature for the next release. It shouldn't be too much effort. If this is an important one for your client, I could churn out a version for you with this feature quite quickly -- let me know.
Posted by Mark Carey
|
October 12, 2007 2:01 PM
Posted on October 12, 2007 14:01
If it's something that can be worked up quickly, we'd really appreciate it, and I'm willing to guinea pig. I meant to ask if it would involve major surgery or could be bolted on.
Posted by Su
|
October 12, 2007 4:15 PM
Posted on October 12, 2007 16:15
To save anyone else who does this a *headdesk* or two(and as reminder to myself): By default, the EntryPost form uses the same value for the "name" attribute as the default comment form.
I have the form embedded in a sidebar rather than a separate page, and so this was causing it to fail on individual archives. Just change the form's name and adjust the JS immediately below to fix.
Posted by Su
|
October 22, 2007 2:06 PM
Posted on October 22, 2007 14:06
Hi Marc,
is it possible to restrict the usage of your plugin to authenticated (without TypeKey) commenters?
Posted by Yves | October 23, 2007 4:57 AM
Posted on October 23, 2007 04:57
Yves, I assume you are talking about MT4 authenticated commenters. The next major version of Entry Post should include full support of MT4's authentication system, include local MT auth, OpenID, etc. I will likely also include plugin-specific options for requiring/allowing authentication.
Another feature to expect, as requested recently (Thanks Grace!), is that the email notifcations will likely have a template module that can be customized on a per-blog basis. This will make it easy to customize what is contained in the emails, including the ability to add extra fields.
Posted by Mark Carey
|
October 23, 2007 8:51 AM
Posted on October 23, 2007 08:51
Mark (now with a 'k' – double sorry) you're right.
So by now I can only choose between everybody may post to the blog or only TypeKey authenticated user may post to the blog?
Just an idea: If I set MT to 'Any authenticated commenters', force the commenter to either register or log-in and then present your form (instead of a comment entry form). Might this work until your next major version?
Posted by Yves | October 23, 2007 10:34 AM
Posted on October 23, 2007 10:34
Yes, Yves, it will work like that. But, as I noted, Instead of relying on the commenting settings in MT, I may include such an option for Entry Post only. This would enable you to accept comments from anonymous users, but require authentication for posting entries, for example.
In the current version, you can simulate what you want to do (showing the form only if they are logged in), but the entry won't get attributed to their user account, but rather under the default EP user.
In short, you definitely be able to do as you describe in the next version (barring any unforeseen difficulties in adding those features.
Posted by Mark Carey
|
October 23, 2007 11:09 AM
Posted on October 23, 2007 11:09
Sounds worth waiting.
Maybe I can fiddle the commenters data into the posting through some hidden fields and JavaScript (in the meantime) and later fetch them through your new plugin. If I buy today, will I get the new version (timeframe ;-) for free?
Posted by Yves | October 23, 2007 12:04 PM
Posted on October 23, 2007 12:04
Yves, I am not sure what you mean by "fiddle the commenters data into the posting through some hidden fields and JavaScript (in the meantime) and later fetch them through your new plugin" -- so I can't confirm whether than will work. BUT, I can tell you that future updates are included, so if you buy today, that includes any/all future updates. I hope to get the new version out within a month (but no promises).
Posted by Mark Carey
|
October 23, 2007 1:00 PM
Posted on October 23, 2007 13:00
I purchased this and cannot limit my authors to just Typekey.
Can you send an email alert when you have it ready with MT 4 native authentication?
Posted by Merv | October 24, 2007 11:18 AM
Posted on October 24, 2007 11:18
Merv, yes, I will be sending out an email when the new version is released, to all MT Hacks members.
Posted by Mark Carey
|
October 24, 2007 11:35 AM
Posted on October 24, 2007 11:35
Mark, I am currently reviewing several plugins from your site. If a user login via Entry post, then goes to another plugin say to forum plugin will it pass along the authentication? This would be on the MT4 version.
Thanks
Posted by PeteV
|
November 1, 2007 1:32 PM
Posted on November 1, 2007 13:32
PeteV, the answer is yes, however, please notice that the current version of Entry Post for MT4 is not fully integrated with the MT4 authentication system. The next major version of Entry Post will include full support for MT native auth, OpenID, etc, and will probably include a few extra settings so you can control who can post entries -- they settings would be separate from the commenting settings.
Posted by Mark | November 2, 2007 10:17 AM
Posted on November 2, 2007 10:17
I've been using this for a while, and am using it primarily as a form to email system. I need a way to, when images are attached, either have them go with the email, or for the email to contain a link to the file. Please help me make this happen! I need it!
Posted by Mark Fischer | January 11, 2008 4:02 PM
Posted on January 11, 2008 16:02
I was waiting for the developer of RF to release a new version, but I hear no news about the development, so I decided to transfer to CF.
Since MT4.1 is ben released I was wondering if the same directions will still apply for the conversion?
water softening
Posted by andy | December 22, 2008 5:04 AM
Posted on December 22, 2008 05:04