-
-
Notifications
You must be signed in to change notification settings - Fork 314
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
Update published_at only after page has been published. #2331
Conversation
Thanks, there are some git conflicts and it would be great to have the two commits to be squashed into one. And if you are rebasing anyway, could you please move the issue reference into the commit message body? Thanks again |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are related spec fails. Can you take a look?
Thanks for the feedback. I'll look into it. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Somehow a commit sneaked into here.
|
||
def ransackable_scopes(_auth_object) | ||
[:published, :from_current_site, :searchables, :layoutpages] | ||
end |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This commit does not belong here. Can you please rebase the branch and remove it?
Closes #2330 Updating published_at only after a public PageVersion has been created or updated to avoid e-tags being created with old PageVersion. re-add Page#publish! since it was public interface
okay, done. |
Now worries. You can always make this a draft PR telling us that you are still working on it
|
Hey Thomas rebased the PR. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks
Update published_at only after page has been published.
Updating published_at only after a public PageVersion has been created or updated.
What is this pull request for?
Issue #2339
Notable changes (remove if none)
Page#published_at is updated async.
Attribute is used in cache key and should only be updated once the page has been published. Since publication is now done in background, the timestamp needs to be updated in the background as well.
Checklist