Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
AI OnAI Off
Five New Optimizely Certifications are Here! Validate your expertise and advance your career with our latest certification exams. Click here to find out more
Looks like a missing feature. If you dig into the code when you fire off the Add method it builds up like this:
public AddRequest Adapt(Comment comment)
{
return new AddRequest
{
Parent = comment.Parent.ToString(),
Author = (string.IsNullOrWhiteSpace(comment.Author.Id) ? "" : comment.Author.Id),
IsVisible = comment.IsVisible,
Body = comment.Body
};
}
So I would make the guess that "Created" is handled on the api server side.
Yea, I figured it was a bug. Thanks for looking into that Spencer.
I may add an imported date to my BlogCommentExtension class to get around this.
Hello, I'm importing comments from a wordpress blog and everything is working as expected except the comment's `Created` property which seems to get overriden to the current time (in our scheduled job). The following lines create the comment, the `epiComment` object has a `Created` DateTime in 2011 but the `addedComment` is returned with the current time:
```
var epiComment = new Epi.Comment(commentId, parent, authorRef, comment.Content, true,
ancestors, comment.Date, hasChildren, hasChildren);
if(!string.IsNullOrWhiteSpace(comment.AuthorEmail))
{
var commentEx = new BlogCommentExtension(comment.AuthorEmail);
var addedComment = _commentService.Add(epiComment, commentEx);
}
else
{
_commentService.Add(epiComment);
}
```