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

Draft "Update Entry" opaque behavior in multi site setup (Could lead to unexpected content changes) #4642

christianruhstaller opened this issue Jul 23, 2019 · 0 comments


Copy link

commented Jul 23, 2019


If you have a multisite Craft installation and you want to work with drafts the behavior when updating an entry from a draft is not what a normal user would expect and could lead to changed content on the entry on a different site.

If you create a draft for an entry this draft will be created for all the sites (If configured) and this is expected. Now you want to use this draft only for the english site. This draft is scheduled to be published in 3 days. In the meantime you fix an error on the german site of the same entry (not via the draft) und save the entry.

After 3 days you will publish the draft from the english site. The english sites draft is published and works perfectly. But what you do not know is that your fix on the german site was overwritten by the german sites draft entry which was not updated by the fix you made on the german entry which is in my opinion a valid and practical workflow.

Steps to reproduce

  1. Create an entry on a multisite instance (english + german)
  2. Create a draft on the english site (Will create also a draft for the german site)
  3. Edit entry for the german site
  4. Publish draft on english site

Observed behavior

After you publish the draft your changes on the german sites are overwritten by the state of the german draft

Expected behavior

You only want to publish the draft for the english site and not the german site.
Actually it could be quite confusing that a draft will get automatically created for another site.

A typical use case could be a promo action only for the us site and not the german site.
I think this "feature" needs some refinement.

Additional info

  • Craft version:

@christianruhstaller christianruhstaller changed the title Draft "Update Entry" opaque behavior (Could lead to unexpected content changes) Draft "Update Entry" opaque behavior in multi site setup (Could lead to unexpected content changes) Jul 23, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.