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

comment_date and comment_date_gmt out of sync? #52

Open
kevinlisota opened this issue May 26, 2018 · 8 comments
Open

comment_date and comment_date_gmt out of sync? #52

kevinlisota opened this issue May 26, 2018 · 8 comments
Labels

Comments

@kevinlisota
Copy link

Running sync on a batch of comments that didn't auto-sync.

In the database, I see the field comment_date_gmt appears to be accurate with the time the comment was made. However, the comment_date field is the time it was synced. That doesn't seem correct.

@dmatt dmatt added the bug label Aug 13, 2018
@turpoint
Copy link

We have the same issue, with both comment_date and comment_date_gmt. Any fix for this?

@tterb
Copy link
Contributor

tterb commented Jan 13, 2021

@kevinlisota @turpoint We just published a plugin update on Monday that addresses this issue, so I would encourage you to update to v3.0.19 if you haven't already.

@turpoint
Copy link

Are there any timezone settings we need to set? comment_date and comment_date_gmt get synced with a 6 hour time difference.

@hlgott1593
Copy link
Contributor

@turpoint The timezone settings are up to you, if you want comment_date and comment_date_gmt to match you will need to set the wordpress timezone to UTC.
https://coschedule.com/support/troubleshooting/wordpress-issues/how-to-change-your-wordpress-timezone/

@turpoint
Copy link

Those are my timezone settings:

Screenshot 2021-01-15 at 20 26 25

But the latest comments (couple of minutes ago) have the following timestamps:

Screenshot 2021-01-15 at 20 29 47

@turpoint
Copy link

The timestamp are correct when using the manual sync, but not auto sync.

@NoodweerBenelux
Copy link

Bump this topic to further solving the issue :)

@hlgott1593
Copy link
Contributor

This issue as well as a few other related to sync have been carded up and are being looked into.

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

No branches or pull requests

6 participants