Stand-Alone Entry Forms

FieldFrame 1.1 added support for Stand-Alone Entry Forms, or “SAEF” for short.

Given the complexity of many FieldFrame fieldtypes, FieldFrame handles things a bit differently than native fieldtypes. Instead of having to manually write each field’s HTML, you simply call the field by name with a single tag:

{exp:weblog:entry_form weblog="default_site"
    return="site/index" preview="site/entry"}

  {my_ff_matrix_field}

  {my_playa_field}

{/exp:weblog:entry_form}

Importing the CSS

As of FieldFrame 1.3, importing the SAEF CSS is up to you:

<link rel="stylesheet" type="text/css" href="/themes/cp_themes/default/ff-saef.css">

Importing jQuery

If you’re using a fieldtype that requires jQuery (like FF Matrix or Playa 2), you’ll have to add the jQuery and jQuery UI script includes yourself:

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.3.2/jquery.min.js" charset="utf-8"></script>
<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jqueryui/1.7.1/jquery-ui.min.js" charset="utf-8"></script>

Editing Entries in a SAEF

If you’re using a SAEF to edit entries, make sure that you place your {exp:weblog:entries} tag pair inside your {exp:weblog:entry_form} tag pair:

{exp:weblog:entry_form weblog="default_site"
    return="site/index" preview="site/entry"}
  {exp:weblog:entries weblog="default_site" url_title="{segment_3}" limit="1"}

    {my_ff_matrix_field}

    {my_playa_field}

  {/exp:weblog:entries}
{/exp:weblog:entry_form}