This is expected behavior, a custom components options won’t be editable if used within a symbol on a page. In order to make these component’s options editable while using the symbol on a page, you would need to either make the symbol inline or add content inputs in your symbol and bind these to the custom component inputs. I’d recommend checking out our symbol with inputs guide, let us know if you have any additional questions!
Currently trying the same, right-clicked a rendered custom component and created a symbol, when I try to edit it it just gives a blank screen so I can’t bind to anything using the above fix- also the right-click menu isn’t working on the symbol on the original page and it’s blank in the symbols menu (where I’d expect a preview).
Thanks.
Wanted to update this forum post, that if you set a dynamic data binding for the various custom component fields, you can use the symbol with inputs workflow, outlined here: Adding Inputs to Symbols - Builder.io to surface the custom component inputs to a user when the symbol is dropped on the page. Try it out and see ifthat works for you!
So custom components that are converted to symbols cannot be used with the fields defined while registering custom components?
I am also facing this issue and haven’t been able to find a workaround. Symbols with input don’t fit me since I must copy all of the field definitions from the original custom component and after that, I don’t know a way to bind newly created fields to the original fields or values.
Do you have any suggestions or manuals for our use case?
