Custom Sass in the Theme editor doesn't save

[X3Technology]

I edited theme.editor.json and set DeveloperMode to true. This enables the Update button in the Theme Builder UX.

I then tried to enter some custom CSS under the Site section:

After I click Update, and then go back, my new Sass value was not saved.

[X3Technology]

Correction. Upon looking in theme.editor.json, I see the new Sass value. However, all of the Controls have been wiped out!

[meetmandeep]

Developer Mode is meant to make changes to the Basic Theme; this should only be used if you're intending to contribute these changes as a Pull Request. Otherwise, a new custom theme should be created. It's exciting to see the community uncover features that are not yet officially documented. I would recommend to bring these questions to our dev series webinars starting early next month.

[X3Technology]

Will do. And I did make a copy of the Basic folder before editing the theme.editor.json file. But I'm pretty sure this is still a bug. I doubt it was intentional to wipe out all the control if any custom Sass has been entered.

[meetmandeep]

But I'm pretty sure this is still a bug.

Yes. Dev team will tag it accordingly after they're able to confirm it.

[meetmandeep]

And I did make a copy of the Basic folder before editing the theme.editor.json file.

I missed this. Did you try the developer mode on a copy of your theme? If so, it wouldn't work as explained earlier that copying a theme folder is not sufficient to create a new theme.

[X3Technology]

It sure does work. I've got two custom themes going now.

[mksmanish79]

We are not able to duplicate the issue. You may be getting the issue as the steps you followed to copy a theme is not correct.

[X3Technology]

I just tried it again and I was unable to duplicate it as well. I will keep playing with it to see if I can reproduce the steps that resulted in the issue.