I already have a Standalone Entry form that works great.  Is there anyway I can make an Edit page similar to the one on the Control Panel. 

I want to be able to choose the variables to be edited based on who is logged in.  I do not want them to have to edit from the control panel because, there I dont have the ability to choose which variables I wanted edited.

Is it possible to make a standalone edit form?

You might want to add your voice to the Feature Request for a Stand Alone Edit form.

KevinSal,

Though the docs don’t include this yet, I have found that simply including the entry id as one of your form fields turns the stand-alone entry form into an edit form. You have to wrap the exp:weblog:entry_form tag inside an exp:weblog:entries tag pair (of vice-versa). Once you do that you can prefill all of the form fields. One problem is that you can’t very easily prefill the custom fields. I have a plugin that can help with that though. Holler if you need it.

Have fun.
mk

It’s kinda hard to email when you don’t have an email link listed.

He does in his profile....

He didn’t until I called him.

It’s true. Sue saves the day. Thanks Sue. mk

Ok, for those interested, you can dive into the plugin here:
www.solspace.com/software

I ask you to register before seeing available software. This way I can let you know about updates.

mk

Thanks, Mitchell. Looks great, and love the docs.

I’ve already found a use for the form helper as well. I’ve been doing some of these by hand, but your solution is much easier. You’ll be getting some PayPal luv.

You’re the best Sue. You can also pay your donation in cookies. mk
p.s. Friggin’ amazing how many people contact you when they have your email address.

>> amazing how many people contact you <<
Probably a lot when you know how to author plugins and modules!

I have a question about the incredible Form Helper Plugin from Solspace, as mentioned on this thread.

Basically, after a bit of configuration, I have the front-end edit form I always wanted. It works! This is great news, and almost seems too good to be true.

We’re testing it as thoroughly as we can, and it seems perfect. Some PayPal cash on the way to Solspace asap.

But, the big question. Is it secure? I mean, is it totally, 100% secure? We’re planning to use it on a site where thousands of members each have editable articles and (not member based) profiles. I’d hate to think it was an easy way into the database for some evil swine to run a script or similar.

I’m sure it’s cool, but better safe than sorry. Anyone from Solspace or EE tested this aspect?

Simon…
I’ve downloaded it but haven’t had time to play around. Anything tricky in setting it up and getting it to work?
Looks like a really cool plugin.

Pretty easy. They’ve explained it well, and provided a sample script which makes a great head-start. I have had to add formatting tools, make button JavaScriping work, and turn text inputs into textareas to retain link and image info in the fields (quotes seem to break the input fields), but once that’s done it’s easy to further refine it.

Basically, it’s great. But is it secure?

You can always only allow the original author the ability to edit the entry, or a SuperAdmin.

From the plugin docs:

First Principals
1. To create a stand-alone edit form you will need to wrap the {exp:weblog:entries} tag inside the {exp:weblog:entry_form} tag. (Note that you can also wrap them in the reverse order.)

From the EE Docs: Entry Form

Users of this form must be members of the site and must be logged in. Further, the user’s Member Group must have permission to post entries to the appropriate weblog. No content will appear if the user is not logged in.

>> turn text inputs into textareas <<
I noticed on my quick review that they were all text input or drop-downs in the sample. How did you change it for text area?

Here’s an example:

Quote:<br />
<textarea name="{exp:form_helper:field_grabber field_name=’q_quote’}” cols="50" rows="3"
onclick="setFieldName(this.name)">{q_quote}</textarea>

Replace q_quote with your field name.

Ok...now I feel stupid I should have spent a little more time browsing the sample and playing before asking questions.
Thanks Sue

It’s not a stupid question at all. Perhaps Mitchell can update his docs and give an example on adding a textarea field. I always forget how to do it.

I use a third party tool called TreePad to maintain some code snippets. No Mac version, though.