` (text-align) and `` (src whitelisted to http(s)/relative — blocks data:/javascript:), and the client `` parser was upgraded to map `font- size` (px/em/rem/%/pt, plus CSS named sizes) and `text-align` to safe React style props. Block cards inherit each view’s native card style (Vue 1 5) so they visually blend with the rest of the funnel. #### 2.6.19 * Chat: the “displayed name” introduced in 2.6.18 is now a WordPress-local option instead of being stored in the POS Limitless backend. Changing it no longer requires a backend deployment — set it in PosLimitless > Configuration > Chat en direct > “Nom affiché dans le widget” (right next to the position selector), save, reload. The value is passed to the chat widget via wp_localize_script and overrides the center name on the fly. Backend-side `widgetTitle` field was removed. #### 2.6.18 * Chat: new “displayed name” field in WordPress admin > PosLimitless > Configuration > Chat en direct > Apparence. Lets the admin override the name shown in the chat widget header with a commercial / brand name (e.g. “Escape Room Paris”) instead of the internal center name (“test”). Left empty, the widget falls back to the center name as before. 60-char max. #### 2.6.17 * Chat: new “email required” toggle in WordPress admin > PosLimitless > Configuration > Chat en direct. When enabled, the pre-chat email field is marked “(obligatoire)” instead of “(optionnel)”, carries the HTML5 `required` attribute, and the widget validates the email format client-side before opening the conversation. When disabled (default), the email stays optional. The setting is pushed to and read from the backend chat config, so it applies uniformly across all entry points. #### 2.6.16 * Chat: fix view-switching regression introduced in 2.6.12. The `display: flex ! important` rule added to the pre-chat container was beating the inline `style. display = "none"` that the widget’s `showView()` sets when transitioning to the active conversation view. Result: after clicking “Démarrer la conversation”, the pre-chat form stayed visible on top of the messages list and input zone — they all rendered stacked together. Removed the `!important` on `display` (kept it on `flex-direction` and `flex`) so JS can still toggle the view. #### 2.6.15 * Chat: form fields, welcome bubble, message list and footer were sticking to the left and right edges of the chat window because the widget’s own internal `* { padding: 0 }` reset (specificity 1,0,1) was beating the per-container padding rules (specificity 0,1,0). All container paddings (header, welcome, pre-chat form, messages list, input zone, footer, individual message bubbles) are now forced with `!important` so they survive the cascade and the content gets proper side breathing room. #### 2.6.14 * Confirmation: the 3 payment-mode subtitles (configured per site in WordPress admin > PosLimitless > Confirmation appearance) are now rich-text. Plain `

` fields have been replaced by a TinyMCE editor with bold, italic, underline,
   text color, hyperlink and bullet/numbered list support, so admins can highlight
   a single word in color or bold without raw HTML. Saved markup is sanitized server-
   side with a strict `wp_kses` allowlist (only `<strong>/<b>/<em>/<i>/<u>/<span
   style="color">/<a>/<ul>/<ol>/<li>/<br>` are accepted), and re-parsed client-side
   via a `DOMParser`-backed `<RichText>` component that maps allowed tags to React
   elements (no `dangerouslySetInnerHTML`, no XSS surface). Anchor `href`s are whitelisted
   to `http(s)`/`mailto`/`tel`/relative paths, and span colors are validated against
   hex/rgb/hsl/CSS named color patterns. Applies to all 5 view styles.

#### 2.6.13

* Chat: fix the last empty-area regression in the pre-chat view. The widget’s own
   internal CSS reset (`#limitless-chat-widget * { margin: 0 }`) had higher specificity
   than the `.limitless-chat-prechat-form { margin-top: auto }` rule that was supposed
   to push the form to the bottom of the chat window. Form was therefore collapsing
   right under the welcome bubble, leaving a large blank stretch between the CTA
   and the footer. The flex `margin-top: auto` is now forced with `!important` so
   the welcome stays at the top and the form sticks to the bottom regardless of 
   the cascade.

#### 2.6.12

* Chat: force critical visual properties with `!important` on the chat widget’s
   hardened CSS rules. On host themes that ship CSS later in the cascade than the
   plugin (typical WP load order: plugin CSS first, theme CSS second), even our `#
   limitless-chat-widget`-prefixed rules were losing the cascade tie-break to lower-
   specificity theme rules that were simply declared later. Properties now forced:
   backgrounds, borders, border-radius, padding, color, width on inputs/textareas/
   buttons, and the welcome avatar’s circle. Also forces the flex layout on `.limitless-
   chat-content` and `.limitless-chat-prechat` so the pre-chat form is reliably 
   pushed to the bottom of the chat window instead of leaving a large blank area
   below the CTA.

#### 2.6.11

* Chat: fix regression introduced in 2.6.10 — the `all: revert` CSS reset applied
   to every `<button>` inside the widget also reset the floating chat button’s `
   position: fixed`, making it static-positioned and effectively invisible (collapsed
   into the page flow). The theme-override protection now uses targeted `#limitless-
   chat-widget`-prefixed selectors per property instead of the nuclear `all: revert`.

#### 2.6.10

* Chat: harden the widget’s CSS against host theme overrides. On sites where the
   active WordPress theme applies aggressive resets like `input { border: none }`
   or `* { background: transparent }` (common on dark / glass themes), the chat 
   widget previously rendered with invisible input borders, a transparent welcome
   bubble and a missing agent avatar background. The fix adds an `all: revert` reset
   on the widget’s form elements and prefixes the critical visual rules with `#limitless-
   chat-widget`, raising specificity above any theme class selector. Also fixes 
   a layout bug where the `.limitless-chat-content` wrapper had no flex rules, so
   the pre-chat form was not pushed to the bottom of the chat window — leaving a
   large empty white area below the “Start” button.

#### 2.6.9

* Confirmation: each payment option (Payer la totalité / Payer un acompte / Payer
   sur place) can now have a custom subtitle, configured per site in WordPress admin
   > PosLimitless > Confirmation appearance > “Sous-titres des modes de paiement”.
   Leave a field empty to hide the corresponding subtitle. Applies to all 5 view
   styles.
 * Chat: second visual pass on the website chat widget after end-user feedback. 
   Each message now sits in its own row with the timestamp rendered below the bubble
   instead of inside it, so short replies no longer collapse into tiny pill shapes.
   Bubbles get a softer drop shadow + a min-width so a one-word answer still reads
   like a real message. Pre-chat welcome message is flanked by a small colored avatar
   that matches the chat color, so it reads as a real first message from the team
   rather than floating helper text. Pre-chat form gets explicit field labels above
   each input (was placeholder-only, which disappeared as soon as the user typed),
   stronger input borders, a tinted shadow on the CTA, and an active-press state.
   Send button in the active conversation gets the same shadow treatment.

#### 2.6.8

* Chat: visual refresh of the website chat widget. The pre-chat form now shows 
   the configured welcome message as an agent-style bubble at the top instead of
   a generic “fill in your info” header, the form sits at the bottom with proper
   visual hierarchy (no more giant blank area between the start button and the footer),
   inputs use a focus ring tinted with the configured widget color, and the header
   carries a small green “online” pulse. The footer reads “Propulsé par POS Limitless”(
   was “Propulsé par Limitless”). Error states now distinguish “chat not yet enabled
   for this center” from “network error” so customers get a useful message instead
   of a generic one.
 * Admin: WordPress admin > PosLimitless > Configuration now exposes a “Chat en 
   direct” card to enable the website chat on the center side, pick the widget color(
   native WP color picker) and edit the welcome message, all pushed live to the 
   POS Limitless backend. Display-only settings (enqueue toggle, position) remain
   WP-local.

#### 2.6.7

* New: built-in live chat widget. The standalone “Limitless Chat” plugin has been
   merged into PosLimitless Booking — install one plugin instead of two. A floating
   chat button now appears site-wide when enabled in PosLimitless > Configuration,
   reusing the Center ID already configured for the booking widget. The chat’s color,
   welcome message and operating hours are configured in the POS Limitless dashboard(
   Configuration > Chat). Position is configurable in WordPress admin (bottom-right
   by default).

#### 2.6.6

* Improvement: client portal dashboard — reservations with status `pictureClient`(
   paid + photo captured on arrival) now show a clean “Payé” badge instead of the
   raw internal status string, alongside a small camera icon that jumps to the Photos
   tab on click. On mobile, the tab bar now performs a brief horizontal scroll hint
   on load when it overflows, so customers discover the off-screen Photos tab without
   having to swipe blindly.

#### 2.6.5

* Fix: ad conversion value (Google Ads, Meta, TikTok, GA4) now reports the full
   reservation total after discounts/coupon, instead of the deposit amount when 
   the customer pays a deposit. Previously deposit-mode bookings under-reported 
   their value to ad platforms, skewing ROAS and smart bidding downward.
 * Change: the booking widget no longer manages its own cookie/tracking consent.
   Since the widget mounts directly in the host page (not an iframe), its tags now
   inherit the consent signals from the host site’s Consent Management Platform (
   Complianz, CookieYes, etc.). The widget’s separate “cookies & trackers” checkbox
   has been removed to avoid a duplicate, conflicting consent layer. The privacy-
   policy acceptance checkbox is unchanged.

#### 2.6.4

* Fix: when the booking widget is mounted via a scoped shortcode (e.g. `[poslimitless_booking
   group_id="..."]`), cancelling a payment on the provider’s hosted page (Stripe/
   CAWL / Monetico / Sogecommerce) now returns the customer to the exact page they
   came from, instead of the center’s general booking page. The widget now forwards`
   window.location.href` as `originUrl` on all payment session creation calls; the
   backend stores it on the session document and prefers it (after host validation
   against the center’s known domains, to prevent open-redirect abuse) over the 
   default booking URL when building the cancel redirect.

#### 2.6.3

* Fix: the real root cause of the “extra players” warning breaking French words
   mid-character. Direct API inspection on the live site revealed the stored message
   HTML contained ` ` (non-breaking space) entities between every word — Quill,
   the rich-text editor used in the admin Service form, inserts NBSP whenever the
   user selects text or applies formatting. From the browser’s wrapping perspective,
   an NBSP-joined sentence is a single unbreakable word, so `overflow-wrap: break-
   word` kicks in and slices it at arbitrary character positions to make it fit 
   the column. No amount of Shadow DOM, `!important`, or `word-break: normal` could
   have fixed it — the issue was in the text data, not the styling. The warning’s`
   sanitizeWarningHtml` now decodes ` ` and the U+00A0 character back into 
   regular spaces before injection, so the browser can wrap at word boundaries the
   way the rest of the CSS already expected.

#### 2.6.2

* Fix: the “extra players” warning, even rendered inside a Shadow DOM (since v2.6.1),
   was still breaking French words mid-character at narrow column widths (e.g. the
   320 px summary column in the V5 confirm view). DevTools inspection on the live
   site (enigma78.fr) confirmed the shadow root and the `word-break: normal !important`
   rule were both applied — so the cause was not theme CSS, but `text-align: justify`
   combined with the browser’s default justification algorithm picking break opportunities
   mid-word when stretching short lines. Switched the shadow-DOM scoped CSS to `
   text-align: left !important` and `text-justify: inter-word !important` so justification
   can only happen between whitespace tokens, never inside a word.

#### 2.6.1

* Fix: the “extra players” warning now renders its message inside a Shadow DOM 
   so the host WordPress theme can no longer reach the content with CSS selectors.
   Earlier attempts (v2.5.4 through v2.6.0) tried scoped class selectors, scoped`
   <style>` blocks, inline `!important` styles, and finally `element.style.setProperty(
   name, value, 'important')` via `useEffect` — but on at least one theme (Enigma78),
   even inline `!important` was being overwritten, probably by a MutationObserver
   re-applying global rules. With Shadow DOM the warning lives in an isolated scope:
   external selectors don’t match, only inherited properties can leak in (and we
   override those with a scoped `<style>` block inside the shadow root). The warning’s
   icon and outer border still render in the light DOM, so the existing flex layout
   is untouched.

#### 2.6.0

* Fix: the “extra players” warning text is now immune to host WordPress themes 
   that ship `#main p { word-break: break-all !important }` or similar high-specificity
   rules. Earlier attempts (v2.5.4 through v2.5.9) used scoped `<style>` blocks 
   with class-based selectors, which a theme rule built on an ID selector can still
   beat in CSS specificity. The component now applies the `word-break`, `overflow-
   wrap`, `white-space`, and `hyphens` overrides via `element.style.setProperty(
   name, value, 'important')` in a `useEffect`, posting them as inline `!important`
   declarations on both the warning’s text container and every descendant injected
   by the rich-text editor. Inline `!important` is the highest CSS priority — even
   ID-based theme rules with `!important` cannot override it.

#### 2.5.9

* Fix: re-introduce the scoped `<style>` block with `!important` overrides on the“
   extra players” warning so its text no longer breaks French words mid-character
   on themes that apply `word-break: break-all !important` or `hyphens: auto !important`
   to their global content. The earlier v2.5.5/v2.5.6 attempts at this block were
   correct in principle but were dropped in v2.5.7 because they coincided with a
   layout regression caused by an unrelated missing `min-width: 0` further up the
   tree (fixed in v2.5.8). Now that the column sizing is robust, the scoped overrides
   can do their job without side effects. Also restores `text-align: justify` on
   the warning text so the right edge looks clean inside narrow summary columns.

#### 2.5.8

* Fix: the cart-recap column in the V4/V5 confirm pages no longer expands past 
   its grid track when a reservation has an “extra players” warning AND/OR a long
   service-option label. The root cause was a flex item (`<div style={{ flex: 1 }}
   >` wrapping the per-resa block in `CartRecap`) which defaulted to `min-width:
   auto`, preventing it from shrinking below its intrinsic min-content. Since v2.5.7
   the warning text uses `word-break: normal`, its intrinsic min-content became “
   the longest word” rather than “1 char”, which together with the missing `min-
   width: 0` pushed the column wider than the 320 px / 400 px grid track and made
   content overflow into the viewport margin. Added `min-width: 0` to that flex 
   item, and rewrapped the service-option `<label>` so its text content lives inside
   a `flex: 1; min-width: 0` span, allowing long option names to wrap inside the
   column instead of overflowing.

#### 2.5.7

* Fix: revert the layout regression introduced in v2.5.5/v2.5.6 where the summary
   column could grow past its 380 px grid track on some themes (the warning component
   became a flex sibling that resisted shrinking). The warning now uses its original
   block layout (`div` instead of `span`, no `<style>` injection, no `min-width:
   0` on the outer container) and only keeps the message-sanitization step from 
   v2.5.6: `<p>` and `<div>` tags coming from the rich-text editor are converted
   to plain `<br>` line breaks, and `class=` attributes are stripped from inline
   tags, so the host theme can no longer style our paragraphs into `white-space:
   nowrap` or `display: inline-block`.

#### 2.5.6

* Fix: the “extra players” warning message no longer overflows the summary column
   or breaks French words mid-character on host WordPress themes that apply aggressive
   global rules to `<p>` and `<div>` tags. Previous v2.5.3–v2.5.5 attempts relied
   on scoped CSS overrides which could be defeated by theme rules with higher specificity(
   e.g. `#content p { ... }`). v2.5.6 takes a different approach: the warning now
   sanitizes the message HTML before injection — `<p>` and `<div>` block tags are
   converted to simple `<br>` line breaks, and class attributes on inline tags (`
   <strong>`, `<em>`, `<a>`, etc.) are stripped — so the entire warning content 
   is rendered inside our own `<span>` whose layout properties are inline-styled(
   highest CSS priority).

#### 2.5.5

* Fix: the “extra players” warning no longer widens its parent summary column past
   the viewport on host WordPress themes. The previous v2.5.4 attempt scoped the
   CSS overrides correctly but did not give the warning container its own `min-width:
   0`, so the flex item’s intrinsic size grew with the longest unbreakable word,
   which in turn forced the right summary column wider than the page. The container
   is now explicitly shrinkable (`min-width: 0`, `flex: 1 1 0%`), and the scoped
   style block now also pins `white-space: normal` and resets `<p>` margins so that
   themes injecting custom paragraph styles cannot disrupt the warning layout.

#### 2.5.4

* Fix: the “extra players” warning message no longer breaks French words mid-character
   on narrow summary columns when the host WordPress theme imposes `word-break: 
   break-all` globally. The previous v2.5.3 fix only set the property via inline
   React style, which the theme’s `!important` rules could override. v2.5.4 now 
   injects a scoped `<style>` block with `!important` overrides on `word-break`,`
   overflow-wrap`, and `hyphens` (incl. vendor prefixes) and justifies the warning
   text for a cleaner look in tight containers.

#### 2.5.3

* Fix: the “extra players” warning message no longer breaks French words mid-character(
   e.g. “expérienc-e”, “dégrad-ée”) in narrow summary columns. Some WordPress themes
   apply `hyphens: auto` globally, and the warning component previously relied on
   the non-standard `word-break: break-word` which let the browser insert automatic
   hyphenation. The component now forces `hyphens: manual` and uses `overflow-wrap:
   anywhere`, so lines only wrap at spaces (or at very long unbreakable strings).

#### 2.5.2

* Fix: variable-priced services now display the correct total when the customer
   uses the “extra players” option to exceed the maxPeople defined in the pricing
   grid. Previously the widget looked up `mapPriceByNb[nbPeople]` directly, and 
   when no entry existed for that exact count (e.g. mapping defined for 26 players
   but client picks 7 or 8), the unit price fell back to 0 €, so the total and deposit
   both showed 0,00 €. The widget now falls back to the highest defined key in the
   mapping, so 7 players on a 26 grid is billed as 7 × price(6).

#### 2.5.1

* Fix: paid traffic attribution. Visitors arriving with only a click-ID (`gclid`,`
   fbclid`, `ttclid`) and no `utm_source` were previously bucketed as “Direct” in
   the Acquisition report, even though they clearly came from a paid ad. The tracking
   loader now mirrors GA4’s default behavior: when no explicit UTM is present but
   a `gclid` / `fbclid` / `ttclid` is, the source is inferred (`google/cpc`, `facebook/
   paid`, `tiktok/paid`). This restores accurate attribution for advertisers who
   have not configured a Google Ads tracking template or are running Performance
   Max (which never propagates UTM params).
 * Added: `ttclid` and `fbclid` are now persisted in localStorage like `gclid`, 
   enabling future server-side Conversion API (Meta CAPI / TikTok Events API) deduplication.

#### 2.5.0

* Fix: Google Ads / Meta / TikTok purchase conversion events are now correctly 
   fired on the booking widget after returning from the payment provider. Previously
   the widget always mounted at “booking” step on return, never rendering the success
   page — so no `purchase` event was pushed to the dataLayer and no conversion was
   sent. The widget now detects success URL params (`session_id` for Stripe, `ref`
   for CAWL/Monetico/Sogecommerce) and switches to the success step on mount.
 * Fix: gift card purchases now fire the same set of conversion events (dataLayer
   purchase + conversion, Google Ads gtag conversion, GA4 purchase, Meta Pixel Purchase,
   TikTok CompletePayment) that the booking flow already had. Previously the gift
   card success state showed a “Bon cadeau acheté !” message but did not push any
   tracking. Conversion data (amount, currency, transaction ID, client info for 
   Enhanced Conversions) is stored before redirecting to the payment provider and
   replayed on return.
 * New: gift card success page now redirects to a configurable “thank you” page (`
   sitewebmercibon` field on the center, falls back to `sitewebmerci` if empty),
   aligned with the existing booking flow. The redirect waits for Meta / TikTok /
   Google Ads pixel network requests to actually fire (PerformanceObserver, 5s safety
   timeout) before navigating away, so pixel/server deduplication is preserved.

#### 2.4.9

* Fix: tracking loader is now served …

## Meta

*  Versão **2.6.41**
 *  Última atualização **3 dias atrás**
 *  Instalações ativas **Menos de 10**
 *  Versão do WordPress ** 5.8 ou superior **
 *  Testado até **7.0.2**
 *  Versão do PHP ** 7.4 ou superior **
 *  Idioma
 * [English (US)](https://wordpress.org/plugins/poslimitless-booking/)
 * Tags
 * [booking](https://br.wordpress.org/plugins/tags/booking/)[events](https://br.wordpress.org/plugins/tags/events/)
   [gift card](https://br.wordpress.org/plugins/tags/gift-card/)[reservation](https://br.wordpress.org/plugins/tags/reservation/)
 *  [Visualização avançada](https://br.wordpress.org/plugins/poslimitless-booking/advanced/)

## Classificações

Ainda não foi enviada nenhuma avaliação.

[Your review](https://wordpress.org/support/plugin/poslimitless-booking/reviews/#new-post)

[Ver todas avaliações](https://wordpress.org/support/plugin/poslimitless-booking/reviews/)

## Colaboradores

*   [ poslimitless ](https://profiles.wordpress.org/poslimitless/)

## Suporte

Tem algo a dizer? Precisa de ajuda?

[Ver fórum de suporte](https://wordpress.org/support/plugin/poslimitless-booking/)