-
Notifications
You must be signed in to change notification settings - Fork 49
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
Strange time stamp problem #80
Comments
Thank you for your reply. But, my simple question is why these time stamps have different values.
When I post WordPress content manually without using C#, Have you ever experienced a time stamp problem that I reported, when you posted by using C# with WordPressSharp library? |
Hello, I now understand the reason for this problem. The following is a complete send request
|
I know that the difference between UTC time and ISO8601 is the way of expression. |
Hi, |
Hello,
I am using WordPressSharp with VS2017 on Windows10.
When I posted a new post with the following settings,
post.PublishDateTime = DateTime.Now;
post.Status = "publish";
I could successfully post.
However, I found a problem.
The Date/Time of the post is 9 hours future in edit window of the post.
But, the Date/Time of the post is 1 minutes before in posts list window.(Good)
My local time is UTC+9.
Then I changed post parameter as below and posted.
post.PublishDateTime = UTC time
The Date/Time of the post is 1 minutes before in edit window of the post.(Good)
But, the Date/Time of the post is 9 hours before in posts list window.
I tried many things but I could not solve the 9 hours difference.
If the post has this strange time stamp,
the client.GetPosts() fails with the following error message.
'response contains invalid dateTime value [response : array mapped to type Post[] : element 0 : struct mapped to type Post : member FeaturedImage mapped to type Object : struct mapped to XmlRpcStruct : member date_created_gmt : dateTime]'
If you know the solution, please let me know.
The text was updated successfully, but these errors were encountered: