Hi,

I’m trying to use the {custom_fields} tags in an SAEF to edit an entry.

(BTW - adding entries is done via the CP, not via this SAEF.)

My problem is: {field_data} is always empty.

Can anyone hit me with a cluestick to tell me what I am doing wrong? The entry’s title and id are generated okay.

Thanks a bunch… Nico

The SAEF isn’t technically meant for editing entries- thus the difficulties.  Have you checked out Solspace’s form helper?  It’s meant to aid with this- and is handy for ironing out the quirks you’ll run into.

I generally hard code the form when I need to edit it- and for dates, use the format:

The date is stored in a different format than it’s displayed.  I suspect that’s the trouble you’re running into.

And I’m going to shift over to ‘How to’, since it’s a bit of a custom job to get an edit form working.  (Doable, though.)

Hi Robin,

Thanks for your reply. What a bummer, though.

Robin Sowell - 09 March 2008 09:36 AM

The SAEF isn’t technically meant for editing entries- thus the difficulties.

I can’t make out from the documentation that an SAEF is for adding entries only. It just states that I can “submit entries”.

Under “Custom Entry Fields” I see:

To me, this indicates that the {custom_fields} tag can supply the data requested.

I will check out the form helper ASAP.

Robin Sowell - 09 March 2008 09:36 AM

The date is stored in a different format than it’s displayed.  I suspect that’s the trouble you’re running into.

That might be the trouble I will run into, but I did see how dates were stored in the database. Thanks for the warning though.

Bye… Nico

Though the SAEF may not be “technically meant” for editing, to say that it is widely used in such a way would be an understatement.  In fact, were the SAEF only be capable of editing it would be quite crippled.

The form helper is very useful but not required.  Actually, the most useful feature of the form helper is the README file and docs because both provide a template of what the “edit form” should look like.

Nico, as you have found, there are a couple of “gotcha’s” when using the SAEF for editing.  Without looking at my notes, here are the two you need to look for.

1. When using the SAEF to create an entry (new entry,) the entry ID is created on the submit.  When using the SAEF to edit an existing entry, the entry ID already exists and needs to be entered with an input field.

If you leave this out, then you will actually create a new entry rather than editing the old one.

2. As already mentioned, the date is the other gotcha.  When using the SAEF to create an entry you use the {entry_date} date as shown in the SAEF docs.  When using the SAEF to edit an existing entry, the date must be added in a specific format as shown by Robin (or in the helpful Form Helper docs.)

I’m sure you guys already have this handled but I just wanted to add my 2 cents to help clarify some things.    By the way, Robin, thanks for the help.

Oh, and I think the problem that you are having regarding {field_data} being empty is that you are not actually viewing an entry.  The weblog fields tag should be filling the fields with data but you are saying all the fields are empty.  This is probably because either you are not using proper parameters to bring up an entry for the chosen weblog (entry could be expired for instance) or you are attempting to view an entry that does not exist for the weblog you are specifying.  If you are unsure, you might setup a basic template that would output the entry in question (without the SAEF stuff) to make sure you are using the correct parameters and other things I mentioned above.

What were the results of this effort?  Success?

We have a similar need and it would be great to know that this is possible.

Editing a stand alone entry form is definitely possible.

Biggest issue is {custom_fields} loop. I could never get that to work, so I hardcoded the fields… which you can do with an entry form as well. You provide field_id_# instead of field_name if you aren’t using Form Helper. I just recently was told about an interesting method using the {query} tag and perhaps that can work for this.

See Cem Meric’s example here:
http://expressionengine.com/forums/viewthread/110825/P54/

Form Helper is helpful. They recommend the following in their instructions (all of which are very important even if you aren’t using form helper although #1 may not be necessary if you can get that {query} to work):
“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.)

2. You will need to pass an entry_id to these tags whether in the URI or hard coded.

3. You will need to capture the entry_id as a value in a field of the form. The field can be hidden like this:
<input type=“hidden” name=“entry_id” value=”{entry_id}” />

4. You will need to capture the title as a value in a field of the form. The field can be hidden like this:
<input type=“hidden” name=“title” value=”{title}” />

5. You will need to capture the entry_date of the entry with a field something like this: (Note that the date formatting is critical.)
<input type=“hidden” name=“entry_date” value=”{entry_date format=’%Y-%m-%d %g:%i %A’}” />

6. You will need to capture the assigned categories of the entry using the field array method. This plugin contains a tag to help with this. (Note that the value of each field in the array must be the category id number.)
<input type=“hidden” name=“category[]” value=”{cat_id}” />”

Shannon - Thanks so much for your keen insight and speedy reply. This is very helpful!

No problem. Please let me know if that query method works. It could save a fair amount of time hard coding forms. It also likely fixes the gotcha listed in that thread with LG Tiny MCE… I’m thinking it might help someone use some of the other “special” fields out there in a saef… like the new data matrix fields.

I’ve gotten checkboxes to work in SAEF (edit and entry) as well (using php, but if I’d known about query, that might have worked there too!). As Cem Meric says, there is always another way… you just have to find it!

I’m hoping that 2.0 improves on the SAEF. It needs work!