Skip to content

1.5.5: restore the Gutenberg color picker - #78

Draft
matthummel-pa wants to merge 1 commit into
mainfrom
cursor/fix-gutenberg-color-picker-992e
Draft

matthummel-pa wants to merge 1 commit into
mainfrom
cursor/fix-gutenberg-color-picker-992e

Conversation

@matthummel-pa

Copy link
Copy Markdown
Owner

The block editor color picker could not apply a color. Tailwind v4’s theme(static) dump wrote 288 oklch() swatches into theme.json and Sage’s default left custom: false, so Gutenberg had no custom hex control and could not parse the palette.

Fix

  • Acreline hex palette: Forest, Clay, Navy, Burgundy, Harvest, Lake, Orchard, Charcoal, plus paper, ink, and white
  • custom: true so the hex picker is back
  • disableTailwindColors: true so Vite does not regenerate the oklch rainbow
  • Runtime wp_theme_json_data_theme filter so the picker stays hex even if a stale build is present
  • Editor canvas loads Identity CSS after the compiled sheet (same order as the public layout)
  • Settings color fields copy a typed hex onto the native color input on save

Test

  • Edit a page. Select a paragraph. Color panel: Forest swatch, then a custom hex. Text should change in the canvas.
  • Appearance → Acreline Settings → General: Accent / Paper / Ink still save.
  • Appearance → Customize → Colors: Accent / Paper / Ink still open.

Version: 1.5.5 (style.css, readme.txt, changelog).

Open in Web Open in Cursor 

Tailwind v4 dumped 288 oklch() swatches into theme.json and left
custom colors off, so the block editor could not apply a pick.
Ship the eight Acreline hex styles plus paper/ink/white, turn the
custom picker back on, and stop generating Tailwind colors.

Co-authored-by: Matt Hummel <matthummel@proton.me>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants