What are you trying to accomplish
Utilize Builder with custom components with Vue. (using @builder.io/vue)
Code stack you are integrating Builder with
How does one register custom components? Trying to use registerComponents() function but doesn’t seem available in the Builder.io: Drag and drop page builder and CMS sdk.
I would recommend to you our current starters that we have for our Vue SDK :
Vue SDK Docs
The READMEs of both link to examples that highlight how they are meant to be used.
I hope this is helpful. If you have any further questions, feel free to reach us again!
Thank you; yes so I changed over to the latest SDK (sdk-vue).
I noticed that the Builder Columns component does not work properly. It creates the columns in the editor and shows an “add block” button for each column. when the button is clicked and a component is chosen (for example, Text) it doesn’t add it to the column but instead to a new row below the Columns component.
Is there a fix to this?
Thanks for reaching us again!
Well, I have tested the Columns component and it seems working fine to me. I followed the exact instructions mentioned by you. Here’s Columns are inside the parent block. The new row is only created if add something after the parent block.
I feel you click on the “Add block after” of the parent columns block.
If you click “Add block after” inside columns then data will add only within columns.
I hope this adds some clarity, if you still need more help you can share your content link so I can have a look!
Thank you for your reply and attempting to help with this issue. Actually, I am not clicking on the “Add block after” plus button. I am doing the following steps as shown in the following series of screenshots:
- after dragging and dropping the Columns component into the Editor I see this
Then I click on the “Add block” button in column one:
Then click on the “Text” component button from the dialog that pops open:
- This text component is then added below the Columns area and not within the column itself, as shown here:
Our content id is d5ed70d67d4d43b1974f52541884b989
We’re still looking into this. I’ll get back to you asap!