Decryption key:
Automatic.css - Utility Framework for WordPress Page Builders v4.0.0 Nulled
Important
This release includes important security hardening. If you’re running an Automatic.css 4.x prerelease, we recommend upgrading to 4.0.0 as soon as possible. Existing v3 sites should remain on v3 because v4 is not backward compatible.
Automatic.css 4.0.0 is here — the culmination of the alpha, beta, and release candidate cycles that shaped ACSS 4. This milestone brings all of that work together and completes the transition to the permanent v4 plugin and licensing setup. Follow the
upgrade guide before installing.
Alongside the work completed throughout the prerelease cycle, this release restores ACSS color workflows in Bricks 2.2+, adds the option to disable effects while editing in Bricks and Etch, improves WordPress 7 compatibility, and includes useful refinements throughout the dashboard and generated CSS.
The changes below are the additions and fixes included specifically in 4.0.0:
Automatic.css 4.0.0 installs as a new plugin
The new Disable Effects In Page Builders option keeps effects out of the way while editing in Bricks and Etch
Manage your Automatic.css license with WP-CLI
Transparent color swatches now insert modern color-mix(in oklch, var(--primary) 10%, transparent) values
Content grid exclusion styles now use lower specificity, giving you more control and making them easier to override.
Dashboard help links open the ACSS cheat sheet
The license key field now asks browsers and password managers to disable autocomplete and save prompts
License requests now identify themselves to our servers
License activation and checks are less likely to be disrupted by third-party plugins.
ACSS color workflows are back in Bricks 2.2 and later! Right-clicking Background and Typography color swatches once again inserts ACSS variables directly into the color field.
Hide Deactivated Classes works correctly on WordPress 7 without triggering the wp_enqueue_script() notice in Bricks
Update checks no longer throw a Class not found fatal when malformed transient data requires a new stdClass instance
Logged entries now render safely in the dashboard, log growth stays bounded, and rotated Activity Log and debug log files remain protected
Dashboard license checks are now restricted to authorized administrators