Is that possible to make a Local JSON feature like ACF did?
Reference : ACF | Local JSON
The things is save all Bricks Builder data on the local json file, and when we do some update on the page or template (included settings of the page / or template itself), it’ll update it on the json file.
If this is possible, we can start development on localhost and sync it with git, any changes on localhost will saving at json file, and when we pushed to the git, it’ll update on the git and ready to deploy on the production site.
+1 for this!
It will simplify maintenance of website in the long run.
The dowside of builder (like ACF for custom field, or Bricks/Elementor for theme builder) is that the “code” is in the database.
This feature will bring back “code” to “code” so we can version control it.
Oooh this is a good idea. I always struggle as developing on local introduces weird things to the DB that I don’t want when I go live.
This would allow me to pass a clean design to the live site.
Has anyone added it to the Ideas list?
Not all ideas are accepted. I believe the Bricks team do some evaluation of ideas before accepting them. I have certainly raised quite a few that never see the light of day.
Im wondering if changing the title of this post can help folks that do not use ACF to understand the feature better.
It could help get traction here in forum.
“Save bricks template to JSON file, to let version control them” maybe is more easy to grasp …
Well I framed it slightly differently as I don’t use ACF.
Just asked for a local page export to allow backups or in my case the ability to move a design cleanly to a new site. So implies an import ability too. All design elements, styles and classes etc would have to be included - which makes it more complicated.
Lets see what they say.
When fully used this feature means that all Bricks template are saved as JSON file to a specific directory every time you click Save in the builder.
Let’s assume “wp-content/bricks-templates” is the directory.
Then, when the frontend page is rendered , the Bricks code instead of getting all templates from DB it look for that directory.
This means that, if we do updates to Bricks template in a dev or staging environment, when it’s time to migrate changes to production we can simply replace the “wp-content/bricks-template” and boom.
I’d love to see this feature as well. It’d be great if I can set things up so anything exportable from/importable to Bricks automatically goes to a specific place in my project’s file system. Then I could version control changes to templates/etc, and also if working in a team become aware of other people’s changes to those things.
Similar to ACF’s Local JSON as somebody else has mentioned in this thread.
This is an excellent idea and aligns with something I’ve been considering lately. We’re currently working on a large eCommerce store, and while tools like WooCommerce are making progress with separate tables for orders, there are still elements – such as Bricks Builder templates – that are stored in the database. This poses challenges when syncing between staging (local) and live environments. Storing Bricks Builder data in JSON files would provide a more efficient solution in this context.
Without knowing about this feature request, I have developed this functionality as a stand alone plugin and plan on releasing this month. If you are interested, please check out brickssync.com for the temporary landingpage where you can subscribe to my mailinglist to stay in the loop when it’s being released!
Brickssync (which adds local JSON capabilities) has been Launched! There is Founder pricing online for the first week or the first 100 licenses sold, whichever comes first. Please check it out at https://BricksSync.com
