All changelogs

Plugixa Car Parking Changelog

A car park booking and reservation system for WordPress, with a step-by-step booking form, live availability, flexible pricing, coupons, a payments ledger and a calendar of every stay.

Latest
v1.2.0
Released
Nov 3, 2026
Total releases
6

v1.2.0

Latest

Three new payment gateways in Pro, and safer handling of everything a payment provider reports after the customer has left.

New 5

  • Pro: Mollie payments through Mollie's hosted checkout, with cards, iDEAL, Bancontact and the other methods you choose. Refunds go through Mollie, and dashboard refunds and chargebacks are reported back. No webhook to set up.
  • Pro: Adyen payments through Adyen's Hosted Checkout. Refunds go through Adyen, and refunds made in the Customer Area and chargebacks are reported back. Needs a Standard webhook with an HMAC key.
  • Pro: Klarna payments through Klarna's Hosted Payment Page. Each payment is captured as soon as the customer completes it, and refunds go through Klarna. No webhook to set up.
  • A customer who comes back before the payment provider has decided sees "Confirming your payment" instead of "Payment not completed".
  • The site is emailed when a customer's bank disputes a payment, on any gateway that reports disputes, so the provider's deadline is not missed.

Improved 1

  • Developers: a gateway's webhook handler may answer several events from one notification, retry to have the provider send it again, or refund_failed to take back a recorded refund. handle_return() may answer processing.

Fixed 4

  • A payment that arrived after a booking's hold had run out could confirm the booking even when its space had gone to someone else. The booking now stays expired, the money stays on its Payments panel, the site is emailed and the customer is told.
  • A refund the provider accepted and then failed to make stayed on the booking as if the customer had the money. It is now marked Failed, the booking holds the money again and the site is emailed (Stripe, PayPal, Mollie and Adyen).
  • On a site with a page cache, a booking form served from a copy more than a day old said "Your session expired" and could not book. A signed-out visitor's form now keeps working for as long as a cache is likely to keep the page.
  • A booking's summary link and the screen shown after paying are now kept out of page caches, so a customer never sees a stale payment status or another customer's booking.
Read the article: Plugixa Car Parking 1.2.0: Mollie, Adyen and Klarna Payments

v1.1.2

Improved 1

  • The plugin no longer stores or prints custom CSS. Move any rules you kept in its custom CSS setting to Appearance > Customize > Additional CSS, or to Styles in the Site Editor. Your old value is kept but no longer used.

v1.1.1

Improved 3

  • Security: the PDF library used for invoices (Pro) is updated to dompdf 3.1.6, which fixes a published security advisory. The Freemius SDK is updated to 2.13.5.
  • The readme's External services section now says exactly what each service receives and when.
  • Developers: the filters plugixa_carparking_quote_request_fields and plugixa_carparking_form_settings are removed, because they passed the raw request to every callback. Use Quote::add_claimer() and FormService::add_setting_claimer() instead.

Fixed 1

  • When the database refused to create one of the plugin's tables, activation reported success anyway. The plugin now checks each table, tries again after five minutes, and shows administrators a notice with a Try again button.

v1.1.0

Improved 20

  • Monthly payments (Pro): a location can let customers pay a stay of two months or more month by month, by card through Stripe. The first month and any one-off fee are paid when booking, then the same amount is taken on the same day each month. A missed month marks the booking overdue and emails the customer and the site, and the plan stops by itself once the booking is paid in full. Customers change their card from the booking's summary page.
  • Rolling monthly plans (Pro): a location can also offer plans that carry on after the stay until the customer cancels. The stay chosen is the shortest they commit to, the space is held for them as far ahead as anyone can book, and when the plan is cancelled the space is free again after the last month paid. Subscribe the Stripe webhook to invoice.paid, invoice.payment_failed, customer.subscription.updated and customer.subscription.deleted.
  • Three designs for the booking form: Classic, Split and Minimal, chosen on the form or per page with the design attribute or the block's Design setting. The block now takes wide and full widths, and the booking summary prints as a clean invoice.
  • Numbered spaces can be added in a run, such as A1 to A20, from the location's Spaces panel (Pro). A booking always holds a real, free space: one the customer picked, or one assigned to them. The "hourly" inventory mode is removed; locations that used it count by capacity, as they always did.
  • A "Booking setup" panel on each location shows what customers can book there, which forms offer it, and what is missing.
  • A stay billed by the month is now counted in calendar months. 1 January to 1 January is twelve months, not thirteen.
  • The locations and space types a booking form is limited to are now enforced by the server, not only by the page. A request made by hand can no longer book a location, or a kind of space, that the form does not offer.
  • A booking form can now be limited to some space types as well as some locations. The form editor says "available at all locations" with a switch, instead of an empty list meaning all.
  • One form is the default form, and a page that names no form shows it. Previously such a page showed built-in steps and ignored the "Default Booking Form". The default form cannot be switched off or trashed; make another form the default instead.
  • A space type with no price for a location's billing unit is no longer offered there. It used to be booked for nothing. The location's Booking setup panel and the space type's prices list what is missing. A price of 0 is still a free space.
  • A booking is always priced in its location's billing unit, whatever the request asks for.
  • A form's custom fields are checked by the server: required fields, email addresses and the options of a list.
  • A coupon is applied only on a form that offers the coupon field.
  • A location, a space type or a space with upcoming bookings can no longer be trashed. Trashing a location or space type removes it from the forms that listed it; a form left with none is switched off.
  • Several booking forms on one page now each keep their own fields and settings.
  • Security: a booking reference alone no longer starts a payment or shows a payment result. Payment links carry a private key, and booking summary and payment pages are kept out of search engines.
  • The admin menu is now called "Plugixa Car Parking" and opens the app directly, without sub-items.
  • The form "layout" setting (wizard or compact) and the "default billing unit" setting are removed; neither did anything.
  • Paying the rest of a booking that was part paid (a deposit, for example) charged the whole total again. It now charges what is left.
  • A booking page whose location setting was not one of its form's locations could not be used. It now starts on the form's first location.
Read the article: Plugixa Car Parking 1.1.0: Monthly Payments, Three Form Designs and Stricter Booking Forms

v1.0.1

Improved 6

  • PayPal payments were taken by PayPal but not recorded on the booking, which stayed unpaid, and the customer was shown "payment not completed". They are now recorded. A payment missed by 1.0.0 is recorded, refundable through PayPal, when the customer's PayPal return link for that order is opened again.
  • Security: the Stripe webhook no longer accepts unsigned events. Sites using Stripe must set the webhook signing secret.
  • Stripe: handles delayed payments, expired checkouts, refunds made in the Stripe dashboard and disputes; admin refunds are sent through Stripe.
  • PayPal: new verified webhook (set the Webhook ID in the PayPal settings) for captures, refunds made on PayPal, reversals and disputes; admin refunds are sent through PayPal; deposits paid by PayPal are recorded as deposits.
  • A refund with no amount after a part refund now refunds what is left, instead of being refused.
  • The "payment not completed" page shows the booking reference again.

v1.0.0

In this release 13

  • Any number of parking locations, each with space types, capacity, opening hours, closures and special days.
  • A step-by-step booking form with live availability, placed with a shortcode or a block.
  • Prices per minute, hour, day, week or month, with an optional one-off fee and prices per location.
  • A form builder for the booking form's steps and your own fields.
  • Coupon codes with percentage or fixed discounts, usage limits, a minimum spend and valid dates.
  • Pay on arrival with your own instructions, and a payments ledger with refunds.
  • A bookings list with search, filters, CSV export and a trash, a calendar and a dashboard.
  • A customer page to find and cancel a booking, and a printable booking summary.
  • Confirmation emails to the customer and the administrator, with a message log.
  • Accessible public pages with a dark mode and right-to-left support.
  • New in premium: numbered bays, a pricing-rule engine, deposits, bookable extras, tax rates and customer groups.
  • New in premium: Stripe and PayPal payments, SMS and Telegram notifications, reminders and a daily report.
  • New in premium: PDF invoices, rescheduling by the customer, a Google Maps location map and a dark admin theme.
Read the article: Introducing Plugixa Car Parking 1.0.0: Car Park Bookings, Run from WordPress