WelcomeScribe

ცვლილებები

0.4.4

• Translations now come from translate.wordpress.org. The plugin no longer ships its own French files. French sites on fr_FR, fr_BE, fr_CH and other French locales use the French (Canada) language pack when their own locale has none.
• Each public REST route (chat, availability, bookings, booking guide, message guide) has its own permission check: the feature must be turned on, the request must come from this site, the security token must be valid, and a per-visitor rate limit applies.
• Request parameters are validated more strictly (type, length, format, and allowed values).
• Rate-limit counters are keyed by a salted hash of the visitor’s IP address. The IP address itself is not stored in them.
• The cancel / reschedule page loads its styles from a stylesheet file.
• The demo mode and calendar feed notices show only on WelcomeScribe screens, are shorter, and can be dismissed.

0.4.3

• New setting: Quick actions. Shows the Book an appointment, Use the form instead, and Talk to a person buttons under the message box. Off by default, including on existing sites.
• New setting: Back button. Shows the Back button in the guided booking and Talk to a person steps. Off by default, including on existing sites. Visitors can still type “back” or “retour”.
• Booking and Talk to a person still start when the visitor types the request, with or without the buttons.

0.4.2

• The chat widget follows the page language: Polylang first, then WPML, then the WordPress locale.
• Every French locale (fr_FR, fr_BE, fr_CH…) uses the bundled French (fr_CA) translation, including when the widget, guides, and emails switch locale. English locales use English.
• The locale sent by the widget to the REST API is kept as is (fr_FR stays fr_FR), so chat replies, guides, and emails use the same language as the widget.

0.4.1

• New setting for the floating bubble scope: Everywhere, Pages only, or Pages and blog home.
• Floating widget visibility is now evaluated consistently for both front-end rendering and asset enqueueing.
• New filter: welcomescribe_show_floating_widget lets developers override the floating widget visibility decision.

0.4.0

• New providers: OpenAI (key and model, default gpt-4.1-mini) and a generic OpenAI-compatible host (base URL, key, and model). Azure OpenAI is unchanged. Each uses the same request code and the same Test connection button.
• Settings show only the fields of the selected provider.
• The settings screen and this readme no longer promise that data stays in Canada. A note explains that it depends on the provider and region.
• Providers are registered through the new welcomescribe_providers filter, and each provider reports whether it is configured.
• New setting: keep or delete WelcomeScribe data when the plugin is deleted. Deleting stays the default.
• Removed the “Not in this version” list from the settings screen.
• Fixed a PHP warning when calendar settings were saved with a list of addresses.
• readme: External services section, FAQ, and WordPress 7.1 compatibility.

0.3.1

• A signed link in the appointment email lets the visitor cancel or reschedule without an account. The link expires, and the business is notified.
• Appointment emails include a calendar file. Times match the site timezone, including daylight saving.
• One reminder email can go out before a confirmed visit. The default is 24 hours, and 0 turns it off.
• Automatic confirmation stays off, so a request remains pending until you confirm it.
• Paste one or more secret iCal addresses (Google Calendar, Outlook, or iCloud). Busy times block open slots. An unreachable feed keeps booking available and shows an admin warning.
• A private calendar address lists WelcomeScribe appointments. The phone number stays out of the title unless you turn that on.

0.3.0

• Visitors can leave a message for the team from the chat, one question at a time, when they ask for a person or the assistant cannot answer. The business receives the transcript by email. Messages are listed under WelcomeScribe, Messages.
• WelcomeScribe, Conversations lists logged sessions and shows chats, bookings, and messages over 7 and 30 days, plus questions the assistant could not answer.
• A day can have more than one open range, so a lunch break is a closed gap. A service can keep its own hours. Existing single-range hours keep working.
• The chat refreshes the REST nonce before the first post and retries once if the cookie nonce is stale.

0.2.1

• The API key can come from WELCOMESCRIBE_AZURE_OPENAI_KEY or WELCOMESCRIBE_API_KEY in wp-config.php or the server environment. That value overrides the database and is not shown in the settings form.
• Test connection reports the HTTP status, the deployment or model, and the latency. The raw provider response and headers are not returned or logged.
• Out-of-scope questions are declined as outside the receptionist role.
• An ambiguous “jeudi prochain” asks the visitor to choose this week or next week.
• French replies use a typographic apostrophe, leaving URLs, email addresses, and code spans unchanged.

0.2.0

• Knowledge base: import a proposed draft from published pages, with an editable preview, merge or replace, size limits, and an optional Improve with AI step that runs only after an explicit click.
• Contact pages: detected hours go to the hours field.
• Demo mode: Improve with AI restructures the draft on the site and does not send page text to a network service.

0.1.1

• PHP 8.4, plain permalinks, service labels, and consent checkbox fixes.
• Opt-in demo provider, off by default.
• French (Canada) translation.
• Step-by-step booking in the chat.

0.1.0

• First release.