FormBuilderProcessor::saveForm() method

Save the form to the database entry, page, or email(s) per form action settings

Usage

// basic usage
$int = $formBuilderProcessor->saveForm(InputfieldForm $form);

// usage with all arguments
$int = $formBuilderProcessor->saveForm(InputfieldForm $form, $entry = 0, $submitType = null);

Arguments

NameType(s)Description
formInputfieldForm
entry (optional)int, array

Optional id of entry (or entry array), if it already exists, 0 if not

submitType (optional)int, bool

Submit type (default=null, which makes it ask from getSubmitType() method in this class)

Return value

int

ID of inserted entry (if saving to entries database) or boolean true if not.


Hooking FormBuilderProcessor::saveForm(…)

You can add your own hook events that are executed either before or after the FormBuilderProcessor::saveForm(…) method is executed. Examples of both are included below. A good place for hook code such as this is in your /site/ready.php file.

Hooking before

The 'before' hooks are called immediately before each FormBuilderProcessor::saveForm(…) method call is executed. This type of hook is especially useful for modifying arguments before they are sent to the method.

$this->addHookBefore('FormBuilderProcessor::saveForm', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $FormBuilderProcessor = $event->object;

  // Get values of arguments sent to hook (and optionally modify them)
  $form = $event->arguments(0);
  $entry = $event->arguments(1);
  $submitType = $event->arguments(2);

  /* Your code here, perhaps modifying arguments */

  // Populate back arguments (if you have modified them)
  $event->arguments(0, $form);
  $event->arguments(1, $entry);
  $event->arguments(2, $submitType);
});

Hooking after

The 'after' hooks are called immediately after each FormBuilderProcessor::saveForm(…) method call is executed. This type of hook is especially useful for modifying the value that was returned by the method call.

$this->addHookAfter('FormBuilderProcessor::saveForm', function(HookEvent $event) {
  // Get the object the event occurred on, if needed
  $FormBuilderProcessor = $event->object;

  // An 'after' hook can retrieve and/or modify the return value
  $return = $event->return;

  // Get values of arguments sent to hook (if needed)
  $form = $event->arguments(0);
  $entry = $event->arguments(1);
  $submitType = $event->arguments(2);

  /* Your code here, perhaps modifying the return value */

  // Populate back return value, if you have modified it
  $event->return = $return;
});

FormBuilderProcessor methods and properties

API reference based on ProcessWire core version 3.0.236

Latest news

  • ProcessWire Weekly #543
    In the 543rd issue of ProcessWire Weekly we'll check out the latest weekly update from Ryan, introduce a couple of new third party modules — both authored by Bernhard Baumrock — and more. Read on!
    Weekly.pw / 5 October 2024
  • Custom Fields Module
    This week we look at a new ProFields module named Custom Fields. This module provides a way to rapidly build out ProcessWire fields that contain any number of subfields/properties within them.
    Blog / 30 August 2024
  • Subscribe to weekly ProcessWire news

“We chose ProcessWire because of its excellent architecture, modular extensibility and the internal API. The CMS offers the necessary flexibility and performance for such a complex website like superbude.de. ProcessWire offers options that are only available for larger systems, such as Drupal, and allows a much slimmer development process.” —xport communication GmbH