NO BUG: Autosave does not save components

The autosave does not save a component.

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.

This happend on v2.0.2 and v2.1-beta.

https://jam.dev/c/2a062b70-6923-4418-a38f-2084fd342e07

Hi Mark,
Thanks so much for your report!

The autosave only saves the Bricks element of the current page/template.
Global data like components, theme styles, etc. need an explicit save and are not captured by the autosave. We’ll add a description next to the Autosave setting, but it’s not a bug.

Best regards,
timmse

1 Like