Thread

This question may be related to a resolved thread.

Hi,

I am using EE 2.1

I am using the following in an SAEF form.

{custom_fields}
{if required}* {/if}{field_label}
{field_instructions}
{formatting_buttons}
{field_instructions}

{if textarea}

<textarea id="{field_name}" name="{field_name}" dir="{text_direction}" cols="50" rows="{rows}">{field_data}</textarea>

{/if}

{if textinput}

<input type="text" dir="{text_direction}" id="{field_name}" name="{field_name}" value="{field_data}" maxlength="{maxlength}" size="50" />

{/if}

etc..

the tag is applied to the field and not the label so the two get split on the page.

Is there a simple way round this?  Seems strange.

Thanks,  Alex

[Mod Edit: Moved to the CodeShare Corner forum]

Alex,

the tag is applied to the field and not the label so the two get split on the page.

I am not sure I am following. Which tag are you referring to? What gets split up? Can you show a rendered example of what you mean?

sorry I should have been more explicit.

I am talking about the tag.  eg

<textarea id="{field_name}" name="{field_name}" dir="{text_direction}" cols="50" rows="{rows}">{field_data}</textarea>

Which is returning:

* place


<input type="text" dir="ltr" id="field_id_18" name="field_id_18" value="" maxlength="128" size="50" /></p>

for example where place is the field label.

This puts place in a completely different place on the page.

There is also a lot of white space in the html generated.

Thanks,  Alex

fiunary,

Thanks for the detail. Unfortunately this is how it renders by default. As per related thread you are able to build out those custom fields for your self. Check this Wiki article for more detail

Thanks.  I have followed the guidance on the wiki page and it works.  I am finding though that tags like {formatting_buttons}
do not work if they are not wrapped in the {custom_fields} tag.  What am I doing wrong?  Help very much appreciated.  Alex

Hi fiunary,

The SAEF tags are designed to work as described in the docs therefore you may have to find another way of generating the output you need. I’ll move this thread into the CodeShare Corner forum since it is more appropriate there now.

Cheers

Greg

Does this mean the wiki entry I was pointed to is wrong?

Hi fiunary,

Not necessarily but the Wiki is for community contributed articles, hints, tips and tutorials and not all the information may be relevant to your particular installation. For example, the Wiki article was pointed out to you as an example but the original article was written for EE 1.x and not 2.x.

Cheers

Greg

Thanks Greg. The issue here then may be the docs which are far from clear in this instance.  Do input fields in SAEF forms need to be wrapped in the {custom_fields} tag in order to render?

fiunary,

Do input fields in SAEF forms need to be wrapped in the {custom_fields} tag in order to render?

Not as far as I know. You will however need the correct field ids though as per the Wiki article.

Adding {formatting_buttons} should also work. Do not use the {custom_fields} tag

Thanks John.

I am not sure whether this worts in v2?

My custom SAEF works fine it is just the EE tags I am having problems with.

I have {formatting_buttons} tag wrapped in {exp:channel:entry_form channel="snippets" return="site/index" preview="site/entry"}

I only get the buttons displaying if I add the {custom_fields} tag (obviously this messes up the custom fields).

There must be lots of others out there using custom SAEF with {formatting_buttons}?

Alex

Formatting buttons are only available for (and within the scope) of custom fields. Feel free to make an FR to have this changed.