Builderius
Forum Replies Created
-
Currently, if you use the built-in contact form, submitting it will simply create a custom post. In the admin area, under the “builderius-form-submissions” page, you can view all form submissions.
There is no native functionality yet to trigger actions like webhooks, but we’ll likely add a hook (filter) on form submission in the future, allowing you to implement custom logic.
Hi @daveden2,
thanks for the question.
Current version of the Collection does not have a feature to not show the JSON on the front end.
However we are going to release V2 version of collection soon (after the the release we are currently preparing, which will bring more power full component properties), which is going to be opt-in for JSON ouput on front end.
You will want to use this feature when you need interactive features like live reload, facets and others.
Hope this helps.
CheersForum: Plugins
In reply to: [Builderius – Landing Page Builder + Dynamic Templates] SCSSHi @flashpoint,
thanks for your query.
Builderius uses vanilla CSS only. So SCSS is not supported. However, this example can now be written like:%selectors% {
width: var(--width-max);
...
:hover {
background-color: black;
}
}And it will work just fine. Of course SCSS offers more but we do not currently support it.
NOTE: this question is related to a PRO only feature, so for those please ask at support@builderius.io in the future.Hi @lovor
That’s a good question. We encourage linear progression in the UI to keep version tracking simple for beginners, but branching is definitely possible.
How to create branches from the same release:- Start with your base release (e.g., version 1.2) as your current active release
- Create Version A:
- Do your work (add slider layout)
- Create release → version 1.3 → tag it “A” → describe and save
- Return to base release:
- Go back to release 1.2 by clicking “Work on this release” button (checkmark icon)
- This replaces all your staging work with version 1.2 content (public site unaffected)
- Create Version B:
- Do your different work (add grid layout)
- Create release → version 1.3 → tag it “B” → describe and save
You can now:
- Preview any version: “Work on this release”
- Publish any version: toggle “publish”
- Base future work on either branch
Pro tip: Both versions are 1.3 because they’re both the next iteration after 1.2 – the tags (A and B) distinguish which design direction each represents. However, you can use different logic for numbering not opinions in the system forcing you to do it this way.
Future releases can continue each branch:
- 1.4 tag A (improvements to slider branch)
- 1.5 tag A (more improvements to slider branch)
Or
- 1.4 tag B (improvements to grid branch)
Does this explanation help?
Forum: Plugins
In reply to: [Builderius – Landing Page Builder + Dynamic Templates] where is the plugin?Hi!
I think you are not using ‘administrator’ role. Builderius admin menu item visible for administrators only at the moment.