Skip to content
This repository has been archived by the owner on Nov 3, 2023. It is now read-only.

Auto saving #8133

Closed
xApep opened this issue Nov 26, 2015 · 1 comment
Closed

Auto saving #8133

xApep opened this issue Nov 26, 2015 · 1 comment

Comments

@xApep
Copy link

xApep commented Nov 26, 2015

Hi. This is all version issue, from typolight version, I guess.
Contao works in a way when you create or change something (content element), everything is auto-saved and previewed on front-end - even if you did NOT saved those changes.

Example 1
You copy content element and you paste it. When you past it you can edit it right away (auto-redirect) in backend, but in at the same time in front-end the copied content element is already visiable? Imagine that you are visitor of this website and you run into subpage where you have two complitly the same content. Wouldn't be better when you copy content element that this copied is auto invisiable, and you must un-check it to make it public?

Example 2
You are editing the Text element and you change type from Text to headline. When you change it, on front-end is also changed - in this example, nothing to show, because you didn't jet enter the headline nor you didn't saved any changes - why then the FE changes?

I really don't see any benefit from this, just a really bad experiance for front-end visitors.

Thanks for your consideration.

@Toflar
Copy link
Member

Toflar commented Nov 26, 2015

That's just the way Contao works. You can copy the element, unpublish and save it. Then you can take your time to edit it, change the type, preview it in the front end etc. When you're done, you just publish the new item and unpublish/delete the old one. We cannot get rid of the "auto saving" as you call it because it would literally break everything.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants