Contents
On this page

Booking forms - Plugixa Car Parking

A booking form is a saved set of choices that produces one booking wizard: which steps it has and in what order, which extra questions it asks, which locations and space types it offers, and how it looks. Each form has its own shortcode.

One form is the default form. [plugixa_car_parking], or a block, that names no form shows the default form. Create another form when one page needs something different.

Open the screen from Plugixa Car Parking, then Booking forms in the Configuration group of the sidebar.

The form you start with

Activating the plugin creates one form when the site has none.

Name Default Booking Form
Slug default
Status Active
Default form Yes
Primary colour #1976d2
Design Classic
Steps The standard ones
Locations All locations
Space types All space types

It is created on activation only.

The default form

Since version 1.1.0, one form is always the site’s default, marked Default in the list. “Pages that name no form use this one.” Before 1.1.0 such a page showed built-in steps and ignored the starter form.

  • The default form cannot be switched off or trashed: “This is the default form, shown on every booking page that names no form. Make another form the default first.”
  • To change it, open another form and turn on Default form, or use the star (Make default) on its row in the list. The old default stays an ordinary form.
  • On an update from 1.0, the form with the slug default becomes the default. If there is none, another form does.

The list

The Booking forms list with three forms, the default one marked Default, their locations, space types and a Copy button for each shortcode

Column What it shows
Name The form’s name, with Default on the default form
Locations The locations the form books at, or All locations
Space types The space types it offers, or All space types
Shortcode A Copy button for the shortcode that shows this form
Custom fields How many fields of your own the form has
Status Active or Inactive
Last changed When the form was last saved

The search box (“Search booking forms…”) matches the name and the slug. Filters narrows the list by status, and the Columns button chooses which columns are shown.

Select rows to act on several forms at once: Activate, Deactivate or Move to trash.

A list with no forms shows “No booking forms yet” and a New booking form button.

Creating a form

The fields builder with the built-in fields and custom fields

The form editor with the steps builder and the side panel

Click New booking form. A new form works as it is: its steps are the standard ones, and you can change them now or later.

Name and slug

Field Notes
Name Required, up to 255 characters. “Only you see it. It tells your forms apart.”
Slug Up to 191 characters. “Left empty, it is made from the name.” If the slug is taken, a number is added to make it unique.

The shortcode names the form by its slug. On an existing form the field warns: “Change it and pages using the old one stop showing this form.” Such a page does not show an error. It falls back to the standard form, so check your pages after changing a slug.

Status

Status Effect
Active The form is shown wherever its shortcode or block is placed. New forms start active.
Inactive Visitors see nothing where the form was. Somebody who may edit booking forms sees “This booking form is inactive, so visitors do not see it.” The default form cannot be inactive.

A visitor who already has the page open when a form is switched off is told “This booking form is no longer taking bookings. Please reload the page.” when they try to book.

Appearance

The side panel of the form editor: Default form, Available at all locations, the Space types list, the primary colour and the three designs Classic, Split and Minimal

Primary colour is “Used for the buttons, the current step and the links on the form.” Pick one of the ten swatches or type a Hex code such as #1976d2, which is the default. A value that is not a hex colour is refused with “A colour is written like #1976d2.”

The plugin works out the matching text colours itself. A pale colour, such as yellow, gets dark text on its buttons, and is darkened where it is used as text, so the form stays readable in light and dark mode.

Design

Since version 1.1.0, Design chooses how the form is laid out on the page. The steps, fields and prices are the same in each.

Design What it looks like
Classic “Numbered steps with the summary beside them.” The default.
Split “Steps and summary in a side column. Needs a wide page.”
Minimal “One quiet column with a progress bar.” The order folds into a bar at the bottom.

The Classic design: numbered steps across the top and the space choice below

The Split design: the steps and the order in a column on the left, the space choice on the right

The Minimal design: one centred column with Step 2 of 5 and a progress bar

A page can show the form in another design with the shortcode’s or the block’s design attribute, which wins over the form’s own. See Shortcodes and Blocks. Split needs room: give its block a wide or full width, or use a full-width page template.

Locations and space types

Available at all locations (including ones added later) is on for a new form. Switch it off to choose the locations the form books at: “The form books only at these.” With the switch off, at least one is needed: “Choose at least one location, or make the form available at all locations.”

Space types limits the space types the form offers. “Leave empty to offer every type.”

A form limited to one location shows that location’s name in place of the location list. Only active locations and space types are offered to customers, whatever is selected here. The editor’s What customers will see card lists, for each location, what can be booked on the form, and warns when a location is switched off or nothing can be booked there.

Checked on the server

Since version 1.1.0, what a form allows is enforced by the server, not only by the page. Every request from the booking form carries the form, and is refused if it asks for something the form does not offer:

Request Refused with
A location the form does not list “That location cannot be booked on this form.”
A space type the form does not offer “That kind of space cannot be booked here.”
A space type with no price for the location’s billing unit “That kind of space has no price here yet, so it cannot be booked.”
A coupon on a form whose space step does not offer the coupon field The coupon is not applied
A required field left empty, an invalid email address, or a choice that is not in the list The field’s own message

So a request made by hand, outside the page, can no longer book a location or a kind of space that the form does not offer.

Several booking forms on one page each keep their own steps, fields and settings.

Steps

The Steps card lists the steps of the wizard. “Drag a step to change where it comes: the booking form shows them in this order. The form always starts with the dates and ends with the review.”

Step What it is Can be switched off
Dates and location “The customer picks a location, an entry time and an exit time.” No. Always first.
Choose a space “The spaces free for that stay, with the price of each.” No
Customer details “Name, contact details and the fields you add below.” No
Payment method Lets the customer choose how to pay. Yes
Review and confirm “A summary of the booking and the button that places it.” No. Always last.

The steps that cannot be switched off carry an Always shown label. The middle steps can be put in any order. Trying to move the first or the last step is refused with an explanation.

Payment method behaves in three ways:

  • On, with more than one way to pay: it is a step of its own.
  • On, with one way to pay: the step is skipped and that way is used.
  • Off: the customer is not asked, and every booking made on the form is paid on arrival.

The Choose a space step has one option, Offer the coupon code field on this form. Switch it off to hide the coupon field on this form only. The field also needs Accept coupon codes to be on in Settings. See Coupons.

Fields

The Fields card lists what the Customer details step asks. “Asked on the customer details step. The answers are kept with the booking.”

Four fields are always there and are shown locked: “Every booking needs this field, so it cannot be changed or removed.”

Built-in field Required
Full name Yes
Email Yes
Phone No
License plate No

Click Add field to ask for something more, such as a flight number or the car’s make. Each field has:

Setting Notes
Label Required. What the customer reads. A field without a label cannot be saved: “A field needs a label.”
Type One of the six types below.
Choices For List of choices only. “Type a choice and press Enter. They are offered in this order.” At least one is needed: “Add at least one choice.”
Required The customer must answer. For a checkbox the switch reads Must be ticked to book, which suits a terms-and-conditions box.
Type What the customer gets
Text A one-line text box
Email address A text box for an email address
Phone number A text box for a phone number
Paragraph A text box of several lines
List of choices A list to pick one choice from
Checkbox A box to tick. Stored as Yes or No.

Drag a field to reorder it. Remove field deletes it from the form.

If a field is not finished when you save, the form is not saved and says “Not saved yet: a field below is not finished.”

Where the answers go

Answers are stored with the booking, together with the label each field had when it was answered. Renaming or removing a field later does not change what earlier bookings show. You see the answers on the booking in Bookings, and the {custom_fields} placeholder puts them in an email. See Emails.

Shortcode

Once the form is saved, the Shortcode card shows it:

[plugixa_car_parking form="airport"]

“Paste it into any page or post to show this form there.” Before the first save the card reads “Save the form to get the shortcode that puts it on a page.”

In the block editor, choose the form in the Car Parking Booking Form block instead.

Trash and restore

The default form has no Trash. Trash on any other row moves the form to the trash at once. Delete on the edit screen does the same after a confirmation. Switch the list from Active to Trash to see trashed forms, where each has Restore and Delete permanently.

A trashed form behaves like an inactive one: pages that use its shortcode show nothing to visitors. A trashed form keeps its slug, so restoring it brings every page that names it back to life.

Trashing a location or a space type removes it from the forms that listed it. A form left with no location is switched off.

Bookings made on a form are not affected by trashing it. They keep their answers and the labels those answers were given under.

Permissions

The screen follows the plugin’s capabilities: viewing needs plugixa_carparking_view, creating plugixa_carparking_create, editing plugixa_carparking_edit and trashing plugixa_carparking_delete. Administrators have all of them. See REST API.

What is stored

Forms live in the {prefix}plugixacarparking_booking_forms table, with is_default marking the default form and the design kept in style. Version 1.1.0 removed the form’s unused “layout” setting (wizard or compact). See Privacy and uninstall.

What to do next

Quick Links

Share