Appointly

cd admin && npm install && npm run build
cd blocks && npm install && npm run build

Historique des changements

2.0.12

• Changed: Dashboard Pro upgrade card now reflects the 8 features actually shipped in Appointly Pro 0.6.0 (custom branding, email template editor, custom service fields, service addons, recurring bookings, direct booking / auto-confirm, blocked dates, customer self-cancel). Previous card listed 12 features, most of which were still on the roadmap.
• Changed: Pro CTA copy — « Join the waitlist → » → « Get Pro → ». The Lemon Squeezy checkout is now live.

2.0.11

• Added: New filter hook appointly_email_template in SettingsRepository::get_email_template(). Free plugin behavior unchanged (no callback registered = defaults returned). Appointly Pro 0.6.0 registers a license-gated callback to inject admin-customized subject and body lines.

2.0.10

• Fixed: Installer now adopts legacy wpbk_response_page_id when upgrading from pre-2.0.7 installs where the prefix migration may have been skipped — prevents a duplicate « Booking Response » page in the frontend menu.
• Fixed: Auto-created Booking Response page is also excluded from wp_list_pages() exclusion arrays (belt-and-suspenders on top of the existing get_pages filter) for broader block-theme compatibility.

2.0.9

• Added: Three new filter hooks (appointly_branding_primary_color, appointly_branding_accent_color, appointly_branding_logo_url) used by frontend shortcodes and email templates. Free plugin behavior is unchanged (defaults to blue/green and the site name as text logo). Appointly Pro 0.5.0 uses these hooks to inject custom branding.

2.0.8

• Fixed: Service image picker in the service editor now opens the WordPress Media Library correctly. The admin bundle was missing wp_enqueue_media(), so window.wp.media was unavailable and the picker silently fell back to an alert.

2.0.7

• Changed: Consolidated all internal prefixes to appointly / APPOINTLY_ / Appointly\ per WordPress.org plugin review guidance. Database tables, options, hooks, constants, namespaces, REST namespace, script handles, JS globals, and CSS classes/custom properties were all unified under a single plugin-specific prefix.
• Fixed: SMTP connection test no longer loads core PHPMailer files directly; uses wp_mail() with wp_mail_failed hook for error capture.
• Fixed: Booking Response page contrast (light-on-light text on some themes).
• Fixed: manage_bookings capability is now ensured on every admin_init as a safety net for file-overwrite upgrades that skip the activation hook.
• Fixed: Cancelling a booking whose service has been deleted no longer produces a stuck « cannot cancel » error — the cancellation proceeds and skips the email step with a clear explanation.
• Internal: DB tables renamed from wpbk_* to appointly_*. CSS custom properties renamed from --wpbk-* to --appointly-*. REST namespace changed from wp-booking/v1 to appointly/v1.

2.0.6

• Added: New filter hook wpbk_booking_initial_status so Appointly Pro can implement direct-booking workflows (per-service auto-confirm).
• Added: Status-driven email routing for newly created bookings — confirmed bookings send booking_confirmed + admin_new_booking, inquiry bookings keep the existing pair.
• Added: New default email template admin_new_booking for admin notifications on direct bookings.
• Internal: DB version bumped to reflect new extension points.

2.0.5

• Added: Direct accept — mark a pending booking as confirmed without sending an offer (offline workflow).
• Added: Status change dialog with an « Inform customer via email » checkbox and optional admin note for every confirm/decline/cancel action.
• Added: Offered bookings can be manually cancelled by the admin (withdraw the offer).
• Added: Decline email template for manual admin declines (pending → declined, offered → declined).
• Added: Status-sensitive action buttons in both BookingDetail and the Bookings list, each with a tooltip explaining what the action does.
• Changed: The cancel booking flow now lets the admin opt out of the cancellation email.
• Changed: Offers sent without a price now show « Price on request » in the customer email instead of hiding the price box.
• Changed: Delete action only available on rows where no customer email has been sent yet (pending) or on finalized records (declined/cancelled).
• Fixed: Several pre-existing German translation errors surfaced during regeneration (Accept was « Angebot annehmen », Cancel Offer was « Angebot annehmen », Price on request was « Offene Anfragen », Decline Booking was « Buchung stornieren »).

2.0.4

• WordPress.org plugin directory compliance release.
• Fixed: Review prompt now uses wp_register_script + wp_localize_script instead of echoing inline tags. Admin notice styled via CSS classes only (no inline style attributes).
• Fixed: All 7 raw SQL queries refactored to use %i placeholder + static literal prepare() strings. Sentinel-value pattern for dynamic filters (BookingRepository::list, ServiceRepository::list), N+1 loop for dynamic IN() clauses (BookingAdminController).
• Fixed: Variables in uninstall.php now carry the $wpbk_ prefix.
• Fixed: Core file includes (PHPMailer, wp-admin/upgrade.php) annotated with rationale comments explaining the allowed exception pattern.
• Fixed: Confirmed bookings can now transition to cancelled (supports Pro recurring series management).
• Changed: Shortcodes renamed from booking_* to appointly_* for prefix uniqueness (BREAKING — no existing public users): [appointly_calendar], [appointly_form], [appointly_response].
• Changed: Gutenberg block namespace renamed from wp-booking/calendar to appointly/calendar (reserved wp- prefix removed).
• Changed: Requires WordPress 6.2+ (was 6.0+) for %i placeholder support.
• Internal: Dashboard hides the Pro upgrade card automatically when Appointly Pro is active.

2.0.3

• Added: Extension point for Pro booking detail sections
• Added: Filter hook for booking data array (wpbk_booking_to_array)
• Fixed: Service description now renders on the public booking form

2.0.2

• New: Opt-in destructive uninstall. Free 2.0.1 wiped all bookings, services, settings, and auto-created pages the instant you clicked Delete in the Plugins screen — with no opt-out. 2.0.2 flips this: by default, deleting the plugin now KEEPS all your data. If you want the old behavior, enable it explicitly under Settings → General → Uninstall Behavior. Matches the WooCommerce / Yoast / WPForms industry standard. Prevents surprise data loss when temporarily deactivating to troubleshoot.
• New: BookingDetail now shows custom field labels instead of raw keys (via custom_fields_meta enrichment in the booking REST response). Both get_booking and update_booking endpoints include the meta so labels persist across status changes.
• New: BookingDetail renders custom field values type-aware — checkbox as Yes/No, numbers locale-formatted (1.234 in DE, 1,234 in EN), textarea with preserved line breaks.
• New: Public booking form inputs now apply min, max, and maxlength HTML5 attributes from the field definition. Browser gives the customer immediate client-side feedback before hitting server-side validation.
• New: Auto-created booking page is marked with _wpbk_auto_created post meta. The uninstaller finds it via meta-query so it’s robust against admin renaming, recreating, or relocating the page.
• These Free 2.0.2 changes ship bundled with Appointly Pro 0.2.0, which adds per-service Custom Fields. All BookingDetail / frontend-form improvements also benefit sites that never install Pro.

2.0.1

• Fix: Calendar showed no days on installs with « Plain » permalinks. The frontend JS naively concatenated ?year=...&month=... to the REST base URL, but the « ugly » REST URL form (/index.php?rest_route=/wp-booking/v1/) already contains a ?, producing URLs with two ? that the REST router treated as part of the route name and returned 404. Calendar now correctly uses & when the base URL already contains a query string. Affects all WP installs that haven’t switched permalinks to « Post name » — long-standing bug, was already broken in 2.0.0 and earlier.
• New: Extension hooks for the upcoming Appointly Pro companion plugin (PHP filters, actions, JS extension points). See docs/PRO_HOOKS.md for the canonical contract.
• Fix: wpbk_email_placeholders filter was dead code due to an early return in EmailService::get_placeholders() — Pro features that injected custom email placeholders never received the filter call. Filter now fires correctly.
• Fix: wpbk_booking_declined action now passes both ($booking, $service) for consistency with all other lifecycle actions.
• New: BookingService::update_booking_date() public method for self-service rescheduling, fires wpbk_booking_rescheduled action.
• New: EmailService::render_preview() public method for live template preview rendering, with wpbk_email_template_keys filter to register additional template keys.
• New: wpbk_calendar_day_annotations PHP filter for per-day annotation strings on the public calendar.
• New: window.wpbkAdmin.proSettingsPanels and proBookingsListRowExtras JS extension points.
• New: window.wpbkConfig.proExtraFormFieldsHTML JS callback for injecting form HTML into the public booking form.
• No user-facing changes — Free 2.0.1 behaves identically to 2.0.0 when Pro is not installed.

2.0.0

• BREAKING — WordPress.org compliance release. Major rewrite to bring the plugin into full WordPress.org Plugin Directory compliance (Guideline 5: no trialware / locked features) and to reposition Pro as a separate companion plugin distributed outside the WP.org directory.
• Removed trialware gates. The license check and feature-gating system (includes/Core/License.php, Limits.php) is gone entirely. Every existing feature is now unconditionally available: unlimited services, unlimited bookings, unlimited custom fields, unlimited add-ons per service, day and timeslot scheduling, automatic offer / confirmation emails, blocked dates calendar, multi-day bookings, and SMTP delivery are all free.
• Pro feature strategy reworked. Stripe/PayPal payment integration, custom email template editor, conversion analytics, and custom branding are no longer part of the free plugin. These and other professional features will return in Appointly Pro — a separate companion plugin sold on appointly.tscholene.com (not on WordPress.org), launching in 2.1.0. The free plugin remains fully functional without Pro. Pro v1 will focus on recurring bookings, group bookings, customer self-service, automatic booking reminders, cancellation policies, and a live preview email template editor.
• New: Rebranded Admin UI. The admin dashboard has been rebuilt from scratch to match the appointly.tscholene.com brand identity — warm plum/violet and amber/gold palette, Instrument Serif hero headings, Plus Jakarta Sans body, DM Mono for data labels. New status pills, stat tiles with accent borders, and a prominent Appointly Pro upgrade card.
• New: Design tokens. All admin UI colours, typography, radii, and shadows are now driven by CSS custom properties scoped to .wpbk-admin, mirroring the website design system.
• Setup Wizard rewritten. The onboarding wizard is now a 4-step flow (Welcome, First Service, Email, Finish) with an honest Free vs Appointly Pro comparison. The previous license-entry and branding steps have been removed.
• New: Extension points for Appointly Pro. The plugin now exposes PHP action hooks (wpbk_booking_created, wpbk_booking_offered, wpbk_booking_confirmed, wpbk_booking_declined, wpbk_booking_cancelled) and filter hooks (wpbk_booking_can_cancel, wpbk_calendar_availability, wpbk_email_placeholders) plus JavaScript extension globals (window.wpbkAdmin.proNavItems, window.wpbkAdmin.proRoutes) so the upcoming Appointly Pro plugin can dock in without requiring any further changes to the free plugin. These are silent no-ops when Pro is not installed.
• Fixed: Compliance issues flagged by the WordPress.org review team. Removed the absolute « The only WordPress booking plugin » marketing claim. Updated the Plugin URI to point at https://appointly.tscholene.com. Fixed the Contributors list to use the correct WordPress.org username tscholene. Added justification docblocks to every REST route using permission_callback => __return_true. Removed the redundant load_plugin_textdomain() init-time call (WordPress 4.6+ auto-loads from languages/ for wp.org plugins; the EmailService runtime call stays because it is load-bearing for the email_language override).
• Database: the wpbk_analytics table is no longer created on activation. Existing installs retain the table until uninstall. Booking rows retain the payment_method and payment_status columns for backwards compatibility but new bookings leave them null.
• Migration: existing license data in the wpbk_settings option is ignored from 2.0.0 onwards and removed on uninstall. No user action required.
• Migration: existing services with booking_mode = 'timeslot' continue to work exactly as before — timeslot scheduling is now a free feature, not a Pro gate.

1.6.5

• Fix: Email preview in admin now renders in the configured email language instead of the admin’s personal profile locale — preview_template() is now wrapped in with_email_locale() like real sends
• Fix: Default email template subjects and bodies are now properly translatable. Previously the Installer wrote hardcoded English strings to the wpbk_email_templates option on activation, which could never be translated regardless of locale. SettingsRepository::get_default_templates() now returns __() wrapped strings resolved dynamically on every read.
• Migration: On upgrade, if the stored wpbk_email_templates option still contains the exact pristine English defaults from 1.5.0–1.6.3 (i.e. the user never customized them), the option is deleted so the translated fallback takes over. Any customization — even a single character — preserves the stored option untouched.
• i18n: Added German translations for all 12 default email subject/body strings (inquiry confirmation, admin notification, offer, booking confirmed, cancellation, payment received)
• DB version bumped to 1.5.0 to trigger the one-time email template migration

1.6.4

• Docs: Updated readme with full changelog for the 1.6.x series
• Maintenance: Synchronised Stable Tag with plugin header version

1.6.3

• i18n: Complete German translation of the admin UI (99% coverage, 418/420 React bundle strings) — dashboard, bookings, services, settings, analytics, onboarding, Pro upsell, email template editor, license manager
• i18n: Generated JavaScript translation JSON files for the admin React bundle (wp_set_script_translations needs per-bundle .json files in addition to .mo)
• i18n: Regenerated .pot template from source (1242 source references) and merged into all five German variants (de_DE, de_DE_formal, de_AT, de_CH, de_CH_informal)
• i18n: All 435 previously-untranslated admin and frontend strings now have German translations (formal « Sie » form across all variants)

1.6.2

• New: « Email Language » setting (Settings → General) lets commercial users force customer emails into a specific language regardless of the WordPress site locale — useful when the admin UI is in one language but customers are in another
• Fix: Email templates now fully translatable — all hardcoded English labels (Date, Time, Service, Name, Email, Phone, Price, Custom Fields, Total Price, Payment Received, Accept Offer, Decline, etc.) wrapped in __()
• Fix: Addon table headers in offer and admin emails (Extra, Qty, Price) now translatable
• Fix: Plugin now calls load_plugin_textdomain() on init so shipped .mo files in /languages/ actually load (previously translations only worked if you dropped the .mo into wp-content/languages/plugins/)
• Fix: EmailService wraps every send in switch_to_locale() / restore_previous_locale() and reloads the text domain on switch (switch_to_locale does not do this for plugin text domains automatically)
• Fix: Email language defaults to get_locale() (site language) instead of determine_locale() — customer emails triggered from admin actions no longer go out in the admin’s personal profile language
• Fix: privacy_policy_url field is now sanitized and persisted correctly via SettingsController (was silently dropped before)
• i18n: 27 new German translations added for the email template labels across all five de_* variants

1.6.1

• Fix (critical): Service dropdown was invisible on the frontend for non-admin visitors whenever the page was served from a cache. Cause was a rest_cookie_invalid_nonce 403 — the cached HTML contained a nonce belonging to a different session, which WordPress’s rest_cookie_check_errors() rejected. fetchServices() then silently hid the dropdown on failure.
• Fix: CalendarShortcode and FormShortcode no longer embed a wp_rest nonce in wpbkConfig. All frontend REST endpoints use permission_callback => __return_true anyway, so the nonce was never protecting anything — it only created the cache-poisoning failure mode.
• Fix: fetchServices() now has an onError handler that surfaces a visible error message instead of leaving the dropdown hidden
• Maintenance: Plugin version bumped to bust browser caches of wpbk-calendar.js

1.6.0

• GDPR / Privacy: WordPress personal data exporter & eraser integration (Tools > Export / Erase Personal Data)
• GDPR / Privacy: Consent checkbox on booking form with configurable privacy policy URL
• GDPR / Privacy: Consent timestamp stored per booking (consent_given, consent_given_at)
• Security: SMTP credentials encrypted at rest (AES-256-CBC)
• Admin: New « Privacy » settings panel for privacy policy URL configuration
• i18n: Added consent label and validation strings (EN + DE)

1.5.0

• Complete plugin state with all features
• iCal calendar feed for Google/Apple/Outlook sync
• Theme mode setting (light/dark/auto) for calendar and emails
• SEO-optimized readme and review prompt after 5 bookings
• Date range booking support (multi-day)

1.0.0

• Initial release
• Booking calendar with day and timeslot modes
• Configurable services with custom fields and addons
• Offer-based booking flow
• 5 HTML email templates with dark mode
• React admin SPA
• SMTP support
• German translation