1.1.9

1.1.9

• Fix: Re-apply live data-allow-close on Divi FAQ cache hits so a settings-only cache cannot keep the attribute at 0 after Foundation’s fsm-divi-accordion-close kit is enqueued (which previously hid the close icon and blocked kit close via capture-phase stopImmediatePropagation).

1.1.8

1.1.8

• New: Icon size setting (px) under FAQs → Settings → Toggle Icon, applied to Divi and generic accordion icons.
• Fix: Open-state (close) toggle icon is shown only when “Allow an open FAQ to be closed…” is checked; otherwise it stays hidden like default Divi. Visibility is gated by data-allow-close.
• Fix: FAQ close JS always loads for Divi markup and respects data-allow-close in capture phase, so an enqueued (even empty/commented) Foundation divi-accordion-close.js can no longer disable or double-fire close on [fsm_display_faqs].
• Fix: When Foundation’s fsm-divi-accordion-close handle is enqueued, Divi FAQ markup keeps data-allow-close="1" (close icon visible) even if the settings checkbox is unchecked, matching the kit’s global close behavior.
• Fix: Toggle hover background also applies to open FAQ items when close is afforded (data-allow-close="1"), for both Divi and generic markup.
• Fix: Generic accordion title padding and button height scale with icon size so large icons (up to 64px) do not overlap question text or get clipped by overflow:hidden.
• New: Animated toggle icons — chevron/caret/angle rotate 180° in place; Plus/Minus morphs via CSS bars on the generic accordion and still swaps glyphs instantly on Divi.

1.1.7

• Fix: Keep the open-item toggle icon visible when closing is allowed — Divi accordion CSS sets display:none on .et_pb_toggle_open > .et_pb_toggle_title::before; Settings-driven SVG/ET icons now force display:inline-block !important on open state when allow_close is on.

1.1.6

FSM FAQ 1.1.6

Bugfix release for Page FAQs query limit ordering.

Fixes

• Query limit + menu_order: When a page has more assigned FAQs than fsm_faq_query_limit, the shortcode no longer pre-slices page_faqs by ACF relationship order before sorting. WP_Query now receives the full membership set, sorts by global menu_order, and applies posts_per_page — so globally earlier FAQs are not dropped when they appear later in the relationship list.

Upgrade notes

• Sites on 1.1.0+ update via the Cloudflare broker; this release syncs via GitHub Actions → broker
• Affects pages with more than 50 assigned FAQs (default limit); re-check FAQ output if a page was missing expected items

1.1.5

FSM FAQ 1.1.5

Bugfix release for ordering, answer sanitization, and media captions.

Fixes

• All FAQs drag-and-drop: Uses Screen Options edit_faq_per_page for pagination offsets so incomplete last pages no longer corrupt global menu_order
• Front-end order: Shortcode always orders by menu_order; Page FAQs is membership only (bidirectional Display On sync no longer blocks global drag order)
• Answer HTML: wpautop runs only when content has no block-level HTML, avoiding empty paragraphs from double-autop on save and display
• Captions: Allow div (and figure id/style) in answer kses so non-HTML5 div.wp-caption wrappers from Add Media are preserved

Upgrade notes

• Sites on 1.1.0+ update via the Cloudflare broker; this release syncs via GitHub Actions → broker
• After updating, re-check FAQ order on pages that use Display On / Page FAQs — front-end order now follows All FAQs drag-and-drop

1.1.4

FSM FAQ 1.1.4

Feature release: settings page, native drag-and-drop ordering, security hardening, and Cloudflare broker updates (bridge already shipped in 1.1.0–1.1.1).

What's new

• Settings page (FAQs → Settings): brand colors, toggle icons (ET Modules / Font Awesome / SVG), border thickness/color, first-open and closable-toggle behavior, corner radius, item spacing, schema mode
• Ordering: drag-and-drop on All FAQs (menu_order); ACF Page FAQs order wins per page when set
• Schema modes: inline JSON-LD (default), merge into Yoast / Rank Math / AIOSEO, or off
• Security: hardened FAQ capabilities and content escaping
• Updates: production installs use https://updates.fullspectrummarketing.com (no per-site GitHub tokens)

Upgrade notes

• Remove staging-only mu-plugins/fsm-faq-staging-branch.php after updating (it was for feature-branch testing)
• Sites on 1.1.0+ already talk to the Cloudflare broker; this release syncs via GitHub Actions → broker
• Keep the GitHub repo public until client sites are confirmed on 1.1.0+, then privatize per update-broker/CUTOVER.md

1.1.1

What's new

• Release packaging uses an explicit allowlist (no root secret/dotfiles in the public update zip).
• Updates continue via the FSM Cloudflare broker: https://updates.fullspectrummarketing.com/fsm-faq.json

Sites still on ≤1.0.5 can update via GitHub to 1.1.x while the repo remains public, then future updates come from the broker.

1.1.0

Bridge release

Default updates now come from the FSM Cloudflare broker:

• https://updates.fullspectrummarketing.com/fsm-faq.json

Keep the GitHub repo public until client sites are on 1.1.0+, then privatize (see update-broker/CUTOVER.md).

No client-site GitHub tokens required.

Release 1.0.5

Full Changelog: 1.0.3...1.0.5

Release 1.0.3

Full Changelog: 1.0.2...1.0.3

Release 1.0.2

Fix curly quotes in HTML output.