Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Saving fatigue -Feature request: Turn off the multi entity saving step #32386

Closed
carolinan opened this issue Jun 2, 2021 · 2 comments
Closed
Labels
[Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed

Comments

@carolinan
Copy link
Contributor

carolinan commented Jun 2, 2021

What problem does this address?

I'd like to be able to turn off the multi entity saving step in the same way as was we can turn off pre publish checks.
I "just want to save".

@carolinan carolinan added the [Feature] Saving Related to saving functionality label Jun 9, 2021
@carolinan
Copy link
Contributor Author

The more I work with the site editor, this is becoming more of a problem, because I keep forgetting that I have to do two steps, and then I wonder why my changes are not applied...

@carolinan carolinan added [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable [Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") labels Oct 21, 2021
@SchneiderSam
Copy link

Same here. I have very many problems with this process.

@carolinan carolinan added [Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed and removed [Type] Feedback Issues that relate purely to feedback on a feature that isn't necessarily actionable [Feature] Saving Related to saving functionality [Feature] Site Editor Related to the overarching Site Editor (formerly "full site editing") labels Apr 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
[Status] Duplicate Used to indicate that a current issue matches an existing one and can be closed
Projects
None yet
Development

No branches or pull requests

2 participants