I understand the logic in that from a technical aspect in the workflow of saving layout changes (and being able to cancel those if required), but from an end-user experience point it is not that great. So...
Edit a layout, then edit a custom block and change its text. Save the block (it feels funny by the way that the button says "Save configuration", but lets leave that for another issue*). At this point, a new user would expect that refreshing the page that shows the changes they've just made in the backend would reflect those changes in the front end. That doesn't happen though. They need to return to the layout edit page (thinking that Backdrop "doesn't work") and then they see the "This form has unsaved changes." message that asks them to save the layout (#1656).
As I said, not optimal UX there.
Hello argiepiano. Thank you. It's not clear to me how to populate that global variable in the first instance. Any pointers on that, please?
Hello trapeharde32. I'd create a custom token to output that global variable, use the module token filter to be able to include tokens in text fields, and insert the token in the desired node fields.
I used "none" (no editor plugin) on D7. In Backdrop, I am using CKEditor. From the documentation, it looks like Backdrop (like D7) saves the line breaks without the HTML tags: Why doesn't Backdrop...
Editing nodes makes them lose formatting