You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As suggested by Phil Rips in the forums: How to sync L&L files across multiple domains. The idea is to pre-parse templates into JSON files in a theme folder at "compile" time (on save).
If L&L wanted to simplify the migration of templates to other websites/domains, the team could implement something similar to the Local JSON feature for ACF.
Local JSON is a helpful feature which saves field groups, post types, taxonomies, and option pages as JSON files within your theme. The idea is similar to caching, and both dramatically speeds up ACF and allows for version control over your field settings!
All .json files within the acf-json folder are loaded during ACF’s initialization procedure.
The text was updated successfully, but these errors were encountered:
eliot-akira
changed the title
Consider templates folder or template.json in parent/child theme to load for fast access
Consider templates folder or JSON files in parent/child theme to load for fast access
Jul 15, 2024
eliot-akira
changed the title
Consider templates folder or JSON files in parent/child theme to load for fast access
Consider template JSON files in parent/child theme to load for fast access
Jul 15, 2024
eliot-akira
changed the title
Consider template JSON files in parent/child theme to load for fast access
Consider template JSON files in parent/child theme for portability and fast access
Jul 15, 2024
eliot-akira
changed the title
Consider template JSON files in parent/child theme for portability and fast access
Consider template JSON files in a theme folder for portability and fast access
Jul 15, 2024
As suggested by Phil Rips in the forums: How to sync L&L files across multiple domains. The idea is to pre-parse templates into JSON files in a theme folder at "compile" time (on save).
Advanced Custom Fields: Local JSON
The text was updated successfully, but these errors were encountered: