Qaiyo Smart Appointment

Regjistër ndryshimesh

1.3.0

• New: the “Upcoming” agenda card — [qsab_upcoming] shortcode and a widget in Gutenberg, Elementor, Bricks, Breakdance and Oxygen. Today’s date and booking count, then the next bookings with their service colour and time; never who booked.
• Fixed: two customers submitting the same slot at the same moment could both get it. A booking is now re-checked the moment it is stored, and approvals, status changes and reminders are all compare-and-set, so a double click or two overlapping requests act exactly once.
• Fixed: following an Approve or Decline link from the admin email acted on the booking straight away — mail scanners that open every link could approve and then decline a request before anyone read it. The link now shows a confirmation screen, like the customer cancel link.
• Fixed: saving one Settings form (booking rules, say) switched off the options of the others, such as FluentCRM sync. Each form now only changes its own settings.
• Fixed: emails, the admin list and the customer screens showed the buffer around a booking as part of its time. They now show when the service itself runs.
• Fixed: an unpaid WooCommerce order held its time slot forever. It is now cancelled by the store’s own “hold stock” timeout, which releases the slot; and a paid booking is re-checked against the calendar before it is confirmed.
• Fixed: FluentCRM re-subscribed customers who had unsubscribed when they booked again. An existing contact keeps its status.
• Fixed: the appointments list stopped at 200 bookings. It is now paged.
• Fixed: the availability calendar showed a day off as “Fully booked”; it now reads “Closed”.
• Changed: the widgets sit in their own “Qaiyo Smart Appointment” group in Gutenberg, Elementor, Bricks, Breakdance and Oxygen (it used to read just “Qaiyo”, and the blocks sat under Widgets).
• New: a per-connection limit on the booking form, on top of the spam trap.
• New: bookings are included in WordPress’s Export / Erase Personal Data tools, with suggested privacy-policy text.
• Security: stricter output filtering for everything the page-builder widgets print, and error messages are no longer passed through the URL.
• Requires WordPress 6.2 or later.

1.2.0

1.2.0

• New: a “Today’s appointments” card for the Qaiyo ecosystem dashboard widget, shown when the free Qaiyo Admin Booster plugin is also active. Shows today’s booking count and the time of the next one; nothing appears if Admin Booster is not installed.
• New extension point: qsab_ecosystem_card_body, which the Pro add-on uses to replace that card’s body with the next three bookings and a link to the calendar — see the Pro changelog.

1.1.0

• Native page-builder widgets: the booking form and the availability calendar are now available as widgets in Elementor, Bricks, Breakdance and Oxygen (6.x), on top of the existing shortcodes. One shared definition feeds every builder, so a setting behaves identically everywhere and an add-on can contribute a control to all of them at once through the new qsab_widget_fields filter.
• Fixed: the Gutenberg block never actually worked — it was registered on the PHP side only, with no editor script, so it never appeared in the block inserter despite being documented. It now registers properly, with real inspector controls (built from the same shared definition as the other builders) and a live preview.
• A booking form can now be given its own layout per placement, overriding the site-wide default set in Settings.
• Hardened CSS output: branding values (accent colour, font) and per-service colour swatches are now validated for the CSS context specifically, rather than relying on HTML escaping, which cannot stop a value from breaking out of a stylesheet declaration.
• Tested up to WordPress 7.1.

1.0.0

• Initial release.
• Fluid, gap-based slot engine, plus a fixed mode with classic back-to-back bands.
• Booking wizard (shortcode [qsab_booking] + block), with unlimited services, staff members and bookings.
• Working hours per staff member, including split shifts — a second block on a day makes the gap between them unbookable. Anyone without their own hours works the site-wide default.
• Soft hold: pending requests can leave the time slot open for everyone else until you approve one — first approval wins. Built for rental and enquiry-style bookings.
• One-click Approve / Decline buttons in the admin notification email, signed so no login is needed and nobody else can use them.
• Quote requests: a booking mode that reserves nothing. The customer names a preferred day and part of day, so an enquiry never blocks a real booking and two enquiries never collide.
• Per-service booking mode: any service can override the site-wide fluid/fixed setting, so a consultation and an enquiry can behave differently on the same site.
• Editable emails: six messages (request received, confirmed, cancelled, completed, reminder, plus the admin alert), each with its own on/off switch and its own subject and wording, written with merge tags. Blank fields fall back to the built-in text, so clearing a field restores it rather than sending an empty email.
• Appointment reminders: an hourly sweep emails every confirmed booking a configurable number of hours before it starts, flagging each row so a reminder can never go out twice however often WP-Cron fires.
• Public availability calendar: the [qsab_availability] shortcode and matching block show free, fully-booked and closed days without putting any customer detail on the page.
• Spam trap on the booking form — an off-screen field that only an automated submission would fill in.
• Customer cancellation links ask before they act: following one shows the booking and a confirm button, so a mail client or scanner prefetching the URL cannot cancel anything.
• Permanent delete for bookings, one at a time or in bulk, for clearing test data out before handing a site over.
• Online payments: a service can require payment before it is confirmed. The built-in provider is WooCommerce, which creates an order for the price and sends the customer to your checkout; paying it confirms the booking, and a cancelled or failed order releases the time slot.
• Uninstall keeps your data by default. Deleting the plugin only drops its tables and options when “Delete all plugin data” has been ticked under Settings first.
• Configurable currency symbol and position for displayed prices.
• Days off / vacation blocking, and settings export / import.
• FluentCRM sync, and 11 built-in languages.
• Native page-builder widgets: the booking form and the availability calendar are available as Gutenberg blocks and as native widgets in Elementor, Bricks, Breakdance and Oxygen, each with the same settings — which service to preselect, which staff member, how many days to show. One shared definition feeds every builder, so they cannot drift apart, and an add-on can contribute a setting to all of them at once through the qsab_widget_fields filter.
• A booking form can be given its own layout per placement rather than following the site-wide setting.
• Values reaching a stylesheet are validated for the CSS context rather than HTML-escaped, so a branding token from the qsab_branding filter cannot inject CSS.
• Extension points for add-ons: qsab_booking_modes / qsab_mode_slots register a booking mode, qsab_service_form_fields / qsab_service_save_data add its per-service settings, qsab_booking_slot finishes the booking off, qsab_payment_providers / qsab_payment_url register a payment provider, qsab_email_types registers a notification, and qsab_appointment_deleted lets an add-on clean up after a deletion. The booking form dispatches qsab:slots-rendered, qsab:slot-selected, qsab:summary and qsab:collect so an add-on can extend it without replacing any markup.