| 开发者 | mijstrebor |
|---|---|
| 更新时间 | 2026年8月23日 05:05 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
clamp()) when needed.
Organize your design system
AFF is not limited to a flat list of variables. Create your own categories and one level of sub-categories to reflect the design system you actually use — for example, Colors organized into Brand / Neutral / Status / Surface, or Numbers into Spacing / Radius / Layout / Sizing. The categories are yours to define.
Work with Elementor — not around it
AFF reads Elementor's V4 variable data and brings it into a dedicated management environment: fetch the variables from your active Elementor kit, organize and edit them in AFF, review which variables are synced, modified, new, orphaned, or in conflict, then commit — explicitly, when you're ready — to write the changes back.
A deliberately controlled write process
AFF is designed around a read-first workflow. Reading Elementor data does not modify Elementor. Writing changes back is always a deliberate, user-triggered action — never automatic or in the background — preceded by a summary showing exactly what will change (modified, new, and deleted variables).
Recommended: use AFF on a staging or local development site, and export a project backup before committing changes to Elementor.
How AFF interacts with Elementor
Read: AFF reads global variables directly from the active Elementor kit's _elementor_global_variables post meta -- the same authoritative data store Elementor itself uses. This happens only when you click "Fetch Elementor Data". It is purely read-only; nothing in Elementor is touched.
Write: When you click "Write to Elementor", AFF writes the current variable values back to _elementor_global_variables on the kit post -- the same authoritative data store, updated the same way Elementor itself updates it. This is the primary and authoritative write. As a secondary, best-effort step, AFF also patches the active kit's generated CSS file directly, so the page reflects the change immediately instead of waiting for Elementor's own regeneration on next load; if this secondary step is skipped or fails for any reason, Elementor's own cache-clear and regeneration (triggered by the post meta update) still produces the correct CSS. AFF writes to no other Elementor data.
Every write is user-triggered (no background or automatic writes, ever), preceded by a confirmation dialog showing exactly what will change, and limited to variables you have managed in AFF. AFF does not touch anything else in your Elementor configuration.
Use on staging or a local development environment only. A corrupted write could damage your Elementor kit's variable data. Always export a project backup before writing to Elementor.
Bringing an existing Elementor site into V4?
AFF can import Elementor V3 Global Colors into your AFF project — both system and custom colors. The four standard Elementor system colors are identified with their familiar roles (Primary, Secondary, Text, Accent), so you never lose track of what each color controls. Bring those colors into your V4 variable-management workflow and map your existing color system as you rebuild your site.
Projects, backups, and portability
AFF supports multiple independent projects within a WordPress site. Each project can be:
.atfrfo.json fileYes. Atomic Framework Forge requires both Elementor and Elementor Pro to be installed and active.
AFF is designed for Elementor V4 and its atomic widget architecture. The 1.4.3 release was developed and validated against Elementor 4.1.3 and Elementor Pro 4.1.1.
No. AFF reads Elementor data when you request it. Changes are written back to Elementor only when you explicitly initiate a commit and confirm the operation.
Not by default. AFF is read-first and non-destructive — it reads your Elementor kit data but never modifies it unless you explicitly click ↑ Variables (Commit to Elementor) in the right panel. A summary dialog shows exactly what will be written before you confirm. When you do commit, AFF updates Elementor's authoritative global-variable data and uses a secondary CSS update where appropriate so changes can appear immediately; Elementor remains responsible for its own normal cache clearing and CSS regeneration.
AFF maintains timestamped project backups, restorable from the project/backup management interface. You should also export a project backup before committing significant changes to Elementor.
Yes. Each AFF project is saved under its own folder in your WordPress uploads directory — for example, a project named brand-colors is stored at /uploads/atfrfo/brand-colors/, with timestamped save files such as brand-colors_2026-08-16_09-15-00.atfrfo.json. Export any saved snapshot and import it into another WordPress site running AFF to bring that project's variables along.
Yes. AFF includes a V3 → V4 color migration feature that imports Elementor V3 Global Colors, including system and custom colors.
Yes. AFF supports categories and one level of sub-categories.
Not yet. Version 1.4.3 focuses on Variables. Classes are in beta on a separate development line and Components are planned for a future release.
— format type for Numbers (z-index, opacity, line-height, etc.).-- prefix while typing variable names.atfrfo_save_file API mismatch after versioned backup refactor).resolve_file() rejecting valid subdirectory paths when the project directory did not yet exist, causing auto-load to silently fail.