v4.4.9 - Block grids + per-site theme UI toggles
Highlights
Block grid normalization and per-site theme UI control toggles.
Block grids and theme polish (#83)
- Consistent column ramp across all grid-capable blocks (Features, Team, Testimonials, Posts, Pricing, Stats, Logos): mobile 1 → sm 2 → lg N. Fixes inconsistent tablet behavior and Logos' reversed scaling on 4/5/6 columns.
- Stats block: replaced daisyUI's
stats stats-vertical lg:stats-horizontalwrapper (which usesgrid-auto-flow: columnand ignoredgrid-cols-N) with a plain Tailwind grid that respects the configured column count. - Strict-match bug: cast
columnsto string in match expressions across Stats / Testimonials / Posts / Pricing / Logos (and standalone Features). Saved configs sometimes stored the value as integer; PHPmatchstrict equality made integer2fall through to default and render the wrong column count. - Theme tokens: replaced hardcoded
bg-white/text-gray-500colors in Parallax CTA and Document List with daisyUI tokens so they respect dark and branded themes. - A11y: added
aria-labels to the close / prev / next icon-only buttons in the Image Gallery lightbox.
Per-site theme UI toggles (#85)
- New per-site SiteSetting toggles let admins hide the theme switcher, search box, or language dropdown without editing Blade.
- Surfaced in the Theme Manager slide-over alongside the Delete action, gated on the active theme so toggles only appear for controls the theme declares it actually renders (
theme.json supports.theme_controller,supports.search,supports.language_switcher). - Auto-save on toggle, multisite-aware (per-site overrides win over Global Defaults). Defaults stay
trueso existing installs keep current rendering on upgrade. - "Configurable" hint icon on the Active badge for theme cards whose active theme has at least one display option.
make:themegains prompts and--include-search/--include-language-switcherflags to scaffold matching component stubs andtheme.json supportsflags.- Bundled TallDaisy and Elevate themes updated to honor the new toggles.
Upgrading
No migrations. No config changes required. All three new SiteSetting defaults are true, so existing installs render exactly as before until an admin flips a toggle.