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

Request for Entry "Updated at" timestamps to be unique per their sites #4475

Open
ifrimere opened this issue Jul 1, 2019 · 2 comments

Comments

Projects
None yet
2 participants
@ifrimere
Copy link

commented Jul 1, 2019

Description

Currently, if a secondary site's Entry has it's content updated, the primary site's corresponding Entry has its 'Updated at' timestamp modified. This seems like the wrong behavior, because each site's Entries should have their own unique 'Updated at' timestamps based on when they were actually last updated.

Steps to reproduce

  1. Create a multisite Craft3 site and set EN(US) as default site, and DE as the secondary site.
  2. Access the homepage in DE, modify its content and save/publish it.
  3. Check the homepage in EN(US) to see when it was last 'updated'. It's timestamp should not have changed after the DE homepage was updated.

Additional info

  1. For our Translation Plugin, we have some features that we'd like to implement to help our clients be better notified when their translations are 'out of date' due to Source content changes... and hope that they then order more translation work from us. To best implement these features we are looking to do diffs of 'Updated at' timestamps to see if source content was modified after translations were 'published'.
@brandonkelly

This comment has been minimized.

Copy link
Member

commented Jul 2, 2019

Each time you save an entry, it is saved across all sites. So even if dateUpdated returned the site-specific timestamp, it would still be identical to the other sites’ timestamps.

@ifrimere

This comment has been minimized.

Copy link
Author

commented Jul 2, 2019

@brandonkelly - can this ticket be reopened as a new feature request to add a more granular aspect to the saved entry db record that is specific to ‘unique content’ changes on the children Entries per enabled Sites. Without this feature, if you imagine a source English site and 20 target language sites, how could users have an at a glance understanding of target entries that are up to date and those whose translations are out of sync.

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