How does the clipboard affect component creation? When I right click on an element in Chrome and have no clipboard permissions, The Chrome prompt come up to approve or deny clipboard. I can still create the component without approving or denying it. Will this cause problems in some cases if the clipboard is not approved?
I saw Bricks try to autosave and it would not autosave with a new component. I saw the save icon animate as if it was saving and when it was done, the yellow dot was still there. When I closed the builder and reopend the template, the component was gone.
I also saw an autosave and opened up the revisions and chose the last autosave revision. I clicked the apply button and the compents were still there. But when I refreshed the page, they were gone.
Here is a video of me applying the last revision and it show the components in the structure tree, but with the “NO” symbol indicating the component is missing. The revision was an autosave, but it did not save the component.
Hi @macksix,
I’m so sorry for the late response. This topic kind of slipped through, and I forgot to respond to it.
This s true. You have to save the builder once you create the component. I believe you should see a notification about unsaved changes before closing the tab, right?
No, the clipboard API is only used for the clipboard, so if you copy/paste elements, styles, classes, … It will not affect other things.
About the autosave, I believe you opened the same topic, so I’ll just link the answer here: NO BUG: Autosave does not save components - #2 by timmse
Thank you, and sorry for the very late response.
Matej
1 Like
Following up on this, we are no longer experiencing this as an ongoing issue. I believe it was due to one of a possible couple things:
1. multiple users editing the same component at the same time: we’re going through a site build using bricks on a very short timeline; we had multiple users from different locations working on similar pages that used the same components - it’s very possible this cause the issue.
2. not saving correctly: it’s unintuitive that you need to save the component whilst editing, but then also save the template it’s in. I put in a feature request to consider rearchitecting the components implementation to move them to the template level (e.g. components should be able to be created and maintained separately from templates, which opens the door for external component development/import/export, and could allow components to be “locked” when one user is editing it, similar to a page/post))
Thank you @kyle_1 for following up. Yeah, those two points are valid and could be the reason for this. I can see this happening.
Thank you,
Matej