Good idea! Does this also support the extra fields created by the Custom Fields/Extra Fields plugins?

I have a entry form with three image uploads, checkboxes and radio buttons, and could do with using this script allowing users to post to it.

Ant, Entry Post currently uses CustomFields to store the Name, IP Address, Email, Image Path, and URL of the person posting the entry. I am not sure exactly what you are asking, but I can tell you still have additional CustomFields configured for your blog, but you won't be able to use EntryPost to populate those fields (at least not without altering the code). You could, of course, populate those fields manually after the entries have been received.

Hi Mark,

Great plugin. One question: since I'm using Tim Appnel's Tags.App to handle my tags, I would need the "tags" field to actually be the "keywords" field (which is how that plugin handles tags). Does your plugin allow me to do this? Thanks!

Alternatively, I could just bite the bullet and use MT's internal tag interface, but using two tag management systems would prove to be a little confusing.

Hi roderick,

Yes, you can do that. Entry Post supports the Keywords field. Instead of a adding a field to your form called tags (such as <input type="text" name="tags") -- simply name the field keywords (<input type="text" name="keywords") and the contents of the Keywords field will be populated.

Note that the "Default Tags" setting would not work with the Keywords field, but you can simulate that by adding a hidden field to your form (such as <input type="hidden" name="keywords" value="books, new toys">)

Questions:

1) Image file upload. Are the images resized, or accepted as uploaded?

2) Authentication. What's the check? Typekey? Others?

3) The template for the advanced posting screen is not included. Perhaps having that would make understanding how to use the other features easier. Can you make that available as a text file?

Notes: When submitting or getting an error, the screen displayed is just the basic information message. Since this is controlled out of the cgi file, perhaps it could use it's own template with a "Continue" and/or "Back" button.

Kevin, here are the answers to your questions:

1) Images are accepted as uploaded. Images are renamed in the format of *entry_id*.jpg to ensure that all image submissions have unique filenames. Image upload functionality is very basic at this point, and could be enhanced in future if there is enough interest.

2) TypeKey is currently supported by the authentication feature. Others may be considered for future versions.

3) Yes, linking to a text file for the advanced form example sounds like a good idea. This is an example I created for demonstration, but I like your idea to make the template code available as a sample.

Thanks for the suggestion on the error screens. There is some room for improvement in those areas.

Here is link to the template code for the advanced form used on the Entry Post test blog:

Example template code for advanced form

I run on MT 3.2. I know the requirements says 3.3+, but still, will this work on MT 3.2? I really need this but cannot go for upgrade for a very large blog I manage. Can you kindly let me know?

Darsh,

Yes, you can, but there are 2 things you need to do:

1. There is a module in 3.3 that is not included with 3.2. It is MT::I18N and this plugin uses two utility functions from this module. If you upload this to your 3.2 install, the plugin will work. Since this MT 3.2 does not look for this module, it won't break or otherwise affect your MT3.2. The required files can be found here and here, or from the 3.3 zip file.

2. Since 3.2 does not have tags, this feature of the plugin will not work. To avoid errors, you should be sure not have a form field named 'tags' and be sure to leave the "Default tags" setting blank. Otherwise, the plugin will try to add 3.3-style tags and may throw an error.

What are your thoughts? The more I think about it, I might be able to update the plugin to support 3.2 out-of-the-box, hiding the tags feature from 3.2 systems. If there is enough interest, I might do this.

Thanks Mark for your reply.

1. Can you ps. explanin when you say, you can upload this to your install - where do we need to put the code/files now?

2. Somewhere on this blog, I read that the keywords feature used as tags - I already have a plugin which does that. Do you think the entry post can work with it?

Darsh, you can disregard what I said in my previous comment. I have just updated the plugin to work with MT 3.2. No need to upload extra files, etc., it just works.

Regarding you questions about using the keywords field as tags: yes you can do that. Just add a field like the following to your form:

<input type="text" name="keywords">

When you have a field named 'keywords' like the one above, the contents of that field will get placed in the Keywords field for that entry. I can't comment specifically on the plugin you are using, but Entry Post can be used to submit text into MT's Keywords field, which should do the trick.

Thank you very much Mark. I was away and just read this today. Will I have to buy the plugin or is a trial version offered? Once again, thank you very much for your help.

Hi Darsh, there is no trial version for this plugin. If you want to try it out, I can provide access to the test blog on my server.

Hi Mark,

I'm thinking of using this impressive plugin for a non-profit blog I'm running. The info tells me about all I need to know, except for one thing. Would it be possible that the author of the entry not only publishes the entry but can delete the entry as well, after publication? Maybe with the help of a 'retrieve entries by author/ with email as password' functionality?

Ton, in the current version, that is not possible. Posters don't have the ability to delete the entries that they submit. They would need to request a blog administrator delete the message for them.

I'm wondering if this plugin is active - i tried to test it but after logging in usin typekey was not given an option to post.

thx

tim, I have fixed that problem. It should work now.