Flowpack Expose Documentation¶

Form/Field¶

You can use this ViewHelper to create complete form fields for your form. By default you have to take care of quite a lot of things yourself to render a form field, like

• form control
• label
• relation between label and form control to enable focusing by clicking on the label
• wrapper around the label + control for better styling
• showing validation errors next to the form control
• add a class to the wrapper around the label + control to indicate an validation error
• maybe add an infotext

To make this easier and reduce the fluid code needed you can use this viewhelper like this:

<e:form.field name="foo" control="Textfield" wrap="Default" value="bar" />

<div class="form-group">
  <label for="foo" class="col-sm-3 control-label">Foo</label>
  <div class="col-sm-9">
    <input class="form-control" id="foo" type="text" name="foo" value="bar">
  </div>
</div>

<div class="form-group has-error">
  <label for="foo" class="col-sm-3 control-label">Foo</label>
  <div class="col-sm-9">
    <input class="form-control" id="foo" type="text" name="foo" value="bar">
    <span class="help-block">This property is required.</span>
  </div>
</div>

<f:form action="create" object="myObject" name="myObject">
  <e:form.field property="someString" />
  <e:form.field property="someRelation" />
  <e:form.field property="someBoolean" />
  ...
</f:form>

<form action="...">
   <div class="form-group">
     <label for="someString" class="col-sm-3 control-label">Some String</label>
     <div class="col-sm-9">
       <input class="form-control" id="someString" type="text" name="someString">
     </div>
   </div>
   <div class="form-group">
     <label for="someRelation" class="col-sm-3 control-label">Some String</label>
     <div class="col-sm-9">
       <input class="form-control" id="someRelation" type="text" name="someRelation">
       <select class="form-control" id="someRelation" name="someRelation">
         <!-- Options provided by the RelationOptionsProvider -->
       </select>
     </div>
   </div>
   <div class="form-group">
     <label for="someString" class="col-sm-3 control-label">Some String</label>
     <div class="col-sm-9">
       <input class="form-control" id="someString" type="text" name="someString">
     </div>
   </div>
 </form>

Form/PropertyHasResults¶

You can use this viewhelper to check if a property has validation errors.

<div class="form-group {e:form.propertyHasResults(property: someProperty, then: 'has-error')}">
  ...
</div>

<e:form.propertyHasResults property="someProperty">
  This property has some errors!
</e:form.propertyHasResults>

Form/PropertyResults¶

Checks if the specified property has errors and adds them as a variable to the view.

<e:form.propertyResults property="someProperty">
  <f:for each="{errors}" as="error">
    <p class="help-block">{error.message}</p>
  </f:for>
</e:form.propertyResults>

Format/Ucfirst¶

returns the string with the first character capitalized

given a variable named foo contains a string fooBar

{foo -> e:format.ucfirst()}

Will result in:

FooBar

Format/Uuid¶

Link/Action¶

A view helper for creating links to actions.

= Examples =

<code title=”Defaults”> <f:link.action>some link</f:link.action> </code> <output> <a href=”currentpackage/currentcontroller”>some link</a> (depending on routing setup and current package/controller/action) </output>

<code title=”Additional arguments”> <f:link.action action=”myAction” controller=”MyController” package=”YourCompanyName.MyPackage” subpackage=”YourCompanyName.MySubpackage” arguments=”{key1: ‘value1’, key2: ‘value2’}”>some link</f:link.action> </code> <output> <a href=”mypackage/mycontroller/mysubpackage/myaction?key1=value1&amp;key2=value2”>some link</a> (depending on routing setup) </output>

Link/Filter¶

Link/Sort¶

This viewhelper only works in conjunction with the SortProcessor.

<e:link.sort property="someProperty">Some Property</e:link.sort>

Navigation/Menu¶

Navigation/MenuItem¶

Actions¶

This viewhelper looks for actions annotated with the \Flowpack\Expose\Annotations\Action annotation and filter them by the type of action specified (local, global, batch)

<e:actions type="global">
  <f:for each="{actions}" key="action" as="actionAnnotation">
    <e:link.action action="{action}" class="{actionAnnotation.class}">
      {actionAnnotation.label}
    </e:link.action>
  </f:for>
</e:actions>

Behavior¶

Block¶

Process¶

Property¶

You can use this viewHelper to retrieve a property from ab object based on the name of the property stored in a variabl

<f:for each="{properties}" as="property">
  <e:property object="{object}" name="{property}" />
</f:for>

Render¶

ViewHelper that renders a section or a specified partial

== Examples ==

<code title=”Rendering partials”> <f:render partial=”SomePartial” arguments=”{foo: someVariable}” /> </code> <output> the content of the partial “SomePartial”. The content of the variable {someVariable} will be available in the partial as {foo} </output>

<code title=”Rendering sections”> <f:section name=”someSection”>This is a section. {foo}</f:section> <f:render section=”someSection” arguments=”{foo: someVariable}” /> </code> <output> the content of the section “someSection”. The content of the variable {someVariable} will be available in the partial as {foo} </output>

<code title=”Rendering recursive sections”> <f:section name=”mySection”>

<ul>

<f:for each=”{myMenu}” as=”menuItem”>

<li>

{menuItem.text} <f:if condition=”{menuItem.subItems}”>

<f:render section=”mySection” arguments=”{myMenu: menuItem.subItems}” />

</f:if>

</li>

</f:for>

</ul>

</f:section> <f:render section=”mySection” arguments=”{myMenu: menu}” /> </code> <output> <ul>

<li>menu1

<ul>

<li>menu1a</li> <li>menu1b</li>

</ul>

</li>

[...] (depending on the value of {menu}) </output>

<code title=”Passing all variables to a partial”> <f:render partial=”somePartial” arguments=”{_all}” /> </code> <output> the content of the partial “somePartial”. Using the reserved keyword “_all”, all available variables will be passed along to the partial </output>

Schema¶

User¶

This ViewHelper helps you to use the currently logged in party in your fluid template without littering every controller the securityContext and assigning the current party to the view.

Wrap¶