Did something break?
Report a Bug
Shipped
JetEngine and Meta Box fields not appearing
After updating Clutch WP plugin to v2.0.0, custom fields created via JetEngine and Meta Box are no longer appearing in the Data to bind to.
Canceled
Fix PayloadCMS Dependencies
I love the idea of both the front end and back end in the same NextJS installation. I’ve been playing with Payload a bit and saw they have support for installing as a backend in an existing NextJS app but it can’t be installed in Clutch because of the current eslint version.
Shipped
New projects not using the latest versions of libraries
When a new project is created, it is not using the latest versions of libraries. After doing a hard refresh (perhaps the same will also happen after sometime), the updates are shown: The libraries should automatically be at their latest versions when a new project is created.
Unable to Use Scroll Bar on Windows
On windows you cannot use the scroll bar without hitting the play button first which makes navigating taller pages tedious or having to use the mouse scroll wheel excessively. More important though, there’s no ability to drag an element while simultaneously using the scroll wheel to scroll the page or structure bar. This makes moving elements from one part of a page to another non visible part of a page painful as you have to leapfrog the element repeatedly into places you can view before scrolling and repeating until you get it where you want.
Can not create variants
Creating composition variants is not working. When you click new variant and type the name it overrides the first variant.
Shipped
Allow entering zero-prefixed values in style inputs (e.g. 0.05em)
Currently, the style input fields block entering values that start with 0, which makes it frustrating to input things like 0.05em. I keep having to trick the input (e.g. typing 1005, adding the period, then deleting the 1).
Shipped
css properties cause crash
Clutch crashes when entering some css properties in custom styles. it happens to me with text-decoration-thickness and text-underline-offset .
Shipped
Bug: orderBy property on queries is not working.
Setting a value to orderby does not do anything
Shipped
Contact Form 7 - form(s) do not get populated in the dropdown
Tested in v2.0.0 of the CF7 library. https://discord.com/channels/949340418229800990/1367408802718027777/1367655725265846292
Shipped
id nin getPosts filter not working
It does not seem possible to filter out the current single post from a list of blog posts using the id filter with any operator. https://discord.com/channels/949340418229800990/1367609379192573952 Using slug works.
Canceled
Contact Form 7 submit action - Runtime Error
https://help.clutch.io/en/help/articles/0456392-contact-form-7 doesn’t seem to work. In Clutch’s console:
Clutch WordPress Plugin Removes Existing Permalink Settings
Description: When the Clutch plugin is installed on a WordPress site, it removes the site's permalink settings entirely. This creates a serious issue for live or production sites where permalink structures are critical for routing, SEO, or archives. Steps to Reproduce: Install Clutch plugin on a WordPress site with custom permalink structure (e.g., /learning-center/%category%/%postname%/). Observe that permalink settings are removed from the WP dashboard. Remove the plugin — previous permalink structure is not restored. Expected Behavior: Clutch should not modify or remove existing permalink settings. At the very least, it should: Detect if the permalink setting is using "Plain" and warn the user to update it. Respect existing custom permalink formats. Actual Behavior: Permalink settings are removed entirely. Dashboard option for permalink structure disappears. Custom structures are wiped on plugin uninstall. Impact: Breaks routing and archive pages on client sites using custom permalink formats. Makes the plugin unsafe to use on live sites without prior caution. Suggested Fix: Add detection for current permalink settings during plugin install. Warn user if "Plain" is active and recommend switching to "Post name" or another clean format. Preserve user settings and restore them on uninstall. Reported by: @Speshled Confirmed by: @MatthewHager Related: Clutch plugin compatibility with REST API and clean slugs.
Shipped
Add Section Modal Scrolls Out of View Before Layout Can Be Selected
when using the in-canvas add section button, scrolling to select a premade layout from the modal is challenging. The modal quickly disappears from view as you scroll before you can make a layout selection. https://app.screencast.com/PoHThyCfOUG2Z
Update Error – "The folder does not exist" during automatic update
Issue: During every automatic update on macOS, users receive an error popup: After clicking "OK," the update proceeds normally and Clutch installs successfully. Steps to Reproduce: Launch Clutch on macOS with an outdated version (e.g. v1.392.0) Wait for the auto-update dialog Observe error dialog before the update continues Expected Behavior: The update should proceed silently or with only one confirmation dialog, without throwing an error about a missing folder. Actual Behavior: Users are interrupted by a confusing system error dialog every time an update is triggered. Notes: Appears to be related to a missing intermediate file or folder during the update extraction process Does not block the update, but causes unnecessary friction Priority: Low severity, high annoyance. Doesn’t block functionality but reflects poorly on the update UX. Suggested Fix: Investigate the update packaging script or auto-updater logic for missing folder creation or cleanup issues.
Sections can be nested inside other Sections via Insert Menu (bypassing drag restriction)
Problem: Sections are not supposed to be nestable within other Sections. This restriction is correctly enforced when using drag-and-drop — users are prevented from dropping a Section inside another Section. However, this rule can be bypassed when: A user selects an element inside a Section Then clicks to insert a new Section from the Insert Menu This results in a Section being nested inside another Section, which breaks intended layout logic and potentially causes rendering or structure issues. Expected Behavior: Inserting a Section should be blocked if the current selection is within a Section The Insert Menu should respect the same placement rules as drag-and-drop Steps to Reproduce: Add a Section to the canvas Select a child element inside that Section Open the Insert Menu and click to insert another Section Observe that the new Section is inserted inside the existing one Priority: Medium – breaks structural expectations and could result in confusing or invalid nesting Suggested Fix: Add a placement guard to the Insert Menu logic that prevents Sections from being inserted into Sections — regardless of selection context.
Embed Components Append Semicolon After </iframe> on Save
Issue: When saving an Embed component that contains an , a stray semicolon (;) is appended after the closing tag. This character renders visually on the site. However, the bug only occurs when the embed contains no HTML comments. Adding a comment — either before or after the iframe — prevents the issue. Example (broken): Published Output: ; Example (working): or Expected Behavior: The embed should not append any additional characters unless explicitly added by the user. Actual Behavior: A semicolon is injected after the closing tag — but only when there are no comments in the markup. Steps to Reproduce: Add an Embed component with only an Save and publish Observe semicolon appearing after the iframe Workarounds: Add a dummy comment anywhere in the embed content (before or after the iframe) Impact: Medium – breaks visual polish and introduces confusing behavior for users embedding external content. Notes: This may be due to a parser quirk or a serialization artifact that gets bypassed when the content includes an HTML comment. Suggested Fix: Sanitize embed output on save to strip unintended trailing characters. Investigate parser behavior for content without comments.
Numeric Width/Height Values Sometimes Published Without Units
Issue: In certain situations, setting a numeric value for width or height in the Style Panel results in the value being saved and published without a unit, causing invalid CSS like: This breaks layout rendering and can go unnoticed until inspecting the published styles. ✅ How to Reproduce (Most Reliable Case) Set width or height to auto in the Style Panel Then change it to a numeric value (e.g. 800) Don’t press Enter or type px manually Publish immediately without refreshing the page Resulting CSS: width: 800; Note: The bug can also occur in other scenarios — this is just the most consistent way to reproduce it. 🤔 Expected Behavior Any numeric input for width/height should default to px unless another unit is explicitly set — and this should persist in the published output, regardless of prior state or interaction. 🚨 Actual Behavior In certain cases (e.g. after setting auto), Clutch accepts and publishes a numeric value with no unit. This can happen: Without a page refresh If the user doesn’t press Enter or reselect a unit Even though px is shown as selected in the UI 🛠 Workarounds Manually type 800px Or press Enter after entering the number Or refresh the page before publishing ⚠️ Impact High UX risk — silently causes invalid styles in production builds, confusing both designers and developers. ✅ Suggested Fix Always coerce numeric values to include the selected or default unit before save Validate units before publishing Ensure unit defaults are applied reliably, regardless of previous style states (like auto)
Canceled
Dragging a Window Affects Other Windows When Multiple Are Open
Issue: When two or more layers of windows (e.g. modals, overlays, or panels) are open in the editor, dragging one window can unintentionally cause other windows to move as well. This leads to unexpected behavior and UI glitches. ✅ Steps to Reproduce Open multiple draggable windows in the editor (e.g., Inspector + Insert Panel or a modal + nested dialog) Try to drag the topmost window Observe that other windows may also move or jump with it 🤔 Expected Behavior Dragging should only affect the specific window being interacted with. Other windows should remain in place unless explicitly selected and dragged. 🚨 Actual Behavior Dragging one window sometimes results in: Multiple windows moving together Positioning conflicts between overlapping windows Incorrect z-index handling ⚠️ Impact Medium – causes usability frustration and layout instability when managing multiple tool panels or modals. ✅ Suggested Fix Ensure each window has isolated drag behavior Prevent drag propagation between stacked or nested windows Verify z-index and pointer event handling to isolate interactions
Canceled
No header tag in Basic Navbar
By default, header tags should be added. Footer tags are added to the Basic Footer.
Shipped
Clutch app "Read docs" links goes to 404 page
https://clutch.io/marketplace/clutch.functions https://clutch.io/marketplace/clutch.google-maps https://clutch.io/marketplace/clutch.google-analytics https://clutch.io/marketplace/clutch.marketing-templates https://clutch.io/marketplace/clutch.video https://clutch.io/marketplace/clutch.wordpress