Multi-Part Forms

The Multi-Part Forms extension allows you to break long forms into sections, creating a natural flow for your visitors. You can add a breadcrumb trail through the various sections of the form and a progress bar so that your users know exactly where they are and how much of your form is left.

Introduction

With the Multi-Part Forms Extension you can break up your forms in as many pages as you like. Break forms up by section, function, or any other way imaginable. In fact this is an actual Multi-Part Form you are using now.

These forms are extremely easy to create and a pleasure to edit. Fields can simply be dragged from one page to another.

Features:

  • Break long forms into multiple pages or ‘sections’ using a drag-n-drop interface.
  • Give each section a title and optionally display it.
  • Display a breadcrumb navigation above the form, making each section easy to access.
  • Add a progress bar to your form.
  • Easily move fields between sections.
  • Easily rearrange pages.
  • Conditionally hide and show entire form pages when used in conjunction with the Conditionals Extension.
  • Show a confirmation page to users displaying all of their data on one page before they submit.

1.2.5

Bugs:

  • Multi-part forms should now work properly with the Stripe extension in all implementations.

1.2.4

Changes:

  • Changed the name of the “Confirmation Page” to “Review Page” to make the option’s purpose more clear.

Bugs:

  • Fixed a bug on the review page that caused hidden fields to sometimes be shown as textboxes that could be manipulated.

1.2.3

Bugs:

  • Fixed a bug with page titles that prevented them from displaying properly on conditional pages.
  • Fixed a bug that caused forms with several pages to have scrolling issues in the admin.

1.2.2

Bugs:

  • Fixed a bug with confirmation pages and the conditional logic extension.
  • Fixed a bug that could cause php errors without the conditional logic extension present.

1.2.1

Bugs:

  • Fixed a bug with confirmation pages that could prevent them from working properly.

1.2

Changes:

  • Added support for the new Ninja Forms loading system. This should significantly improve loading speed for forms that use multi-part forms.

1.1.1

Bugs:

  • Fixed translation issues by adding a default language folder, fixing several bad text domains, and adding a proper translation loader.

Changes:

  • Added a jQuery event for ‘mp_change_page’ that fires after the page has successfully changed.
  • Added some CSS for WP 3.8 compatability.
  • Admin scripts should now load the min or dev versions based on the NINJA_FORMS_JS_DEBUG constant.
  • Removed old licensing file.

1.1

Bugs:

  • Fixed a bug that could cause Multi-Part Javascript to run, even if the form wasn’t a Multi-Part form.
  • Fixed a bug that could cause initial page load to be incorrect with a Multi-Part form.

1.0.14

Changes:

  • Added a class to the page title on each multi-part page so that it can be styled with Layout & Styles.

Bugs:

  • Fixed bugs that could prevent the previous and next buttons from displaying correctly.

1.0.13

Changes:

  • Changed the license and auto-update system to the one available in Ninja Forms 2.2.47.

1.0.12

Bugs:

  • Fixed a bug that could cause Multi-Part forms to work incorrectly with the Save Progress extension.
  • Fixed a bug that prevented form settings from being carried from Multi-Part page to Multi-Part page.

1.0.11

Bugs:

  • Fixed a bug that prevented conditional logic from being properly applied to pages within a multi-part form.

1.0.10

Changes:

  • Updated references to wpninjas.com with the new ninjaforms.com.

1.0.9

Features:

  • When creating a multi-part form, page numbers can now be dragged and dropped to re-arrange the pages of your form.

Bugs:

  • Minor bug-fixes.

1.0.8

Changes:

  • Changed the Javascript methods used in order to be compatible with Ninja Forms 2.2.37.

1.0.7

Changes:

  • Updates for compatibility with WordPress 3.6

1.0.6

Bugs:

  • Fixed some minor visual bugs.

1.0.5

Bugs:

  • Fixed a php warning caused by a function running even if Multi-Part forms weren’t enabled.
  • Fixed a bug that was causing breadcrumb navigation to have the incorrect classes applied.

1.0.4

Bugs:

  • Fixed a bug that caused the new, shorter field length to show incorrectly when the settings were saved.

1.0.3

Features:

  • Multi-Part Forms will now allow you to hide or show an entire page when used in conjunction with the Conditionals extension.
  • A new “Confirmation Page” option has been added. If this is selected, the user will be presented with a page showing all of their entered data, separated by page.

Changes:

  • Changed the way that MP forms CSS is laid out to make it compatiable with version 2.2.18 of Ninja Forms.

1.0.2

Bugs:

  • Fixed a bug with Multi-Part Forms and AJAX submissions that might affect some users.

1.0.1

Features:

  • Updated Multi-Part Forms so that the extension works with AJAX submissions.

Changes:

  • The ID of the DIV that wraps the navigation elements has been changed to ninja_forms_mp_nav_wrap from ninja-forms-mp-nav-wrap.
  • A class of ‘ninja-forms-mp-nav-wrap’ has been placed on the DIV that wraps the navigation elements.

1.0

Bugs:

  • Fixed a bug that prevented multi-part from working properly with post creation.

0.9

Bugs:

  • Fixed a bug that prevented two multi-part forms from working properly on the same page.

0.8

  • Field values that are emailed should now appear in the proper order.

0.7

Changes:

  • Added a prev/next wrapper, adjust default styling for breadcrumbs and progress-bar.

0.6

  • Fixed a bug that prevented the Multi-Part extension from interacted properly with the Save Progress extension.

0.5

  • Fixed a bug that was preventing required fields from being properly checked.
  • Fixed a bug with breadcrumb navigation that prevented the page with the first error from reloading if a user skipped to the end of a form and submitted.
  • Fixed a bug that was preventing a form from properly being changed into a Multi-Part form.

0.4

  • Fixed a bug that caused design elements, especially text fields, from showing on multi-part forms.

0.3

  • Various bug fixes including:
  • A bug which prevented all fields from being emailed to the administrator.

0.2

  • Various bug fixes.
  • Changed the way that javascript and css files are loaded in extensions.