This answer has been locked, yet when I ask the API about this post it fails to return a locked_date:
It's a rather old lock, but I can't see anything suspicious in the timeline or the Post History.
-
PS: What error(s) does the API give when your script tries to write/edit a locked answer?Brock Adams– Brock Adams2019-01-20 21:39:30 +00:00Commented Jan 20, 2019 at 21:39
-
"Account is not allowed to suggest edits", see the bug report Wrong error message when attempting to edit a locked answerGlorfindel– Glorfindel ♦2019-12-06 09:57:28 +00:00Commented Dec 6, 2019 at 9:57
Add a comment
|
1 Answer
Does it work on answers at all?
- Here's a newer locked answer. Yet, it doesn't have a
locked_dateeither. - It's not a filter issue.
- Nor is it fixed in version 2.3 (yet).
Also, additional bug feature-request:
The post object should also return a locked_date.
A sample locked question does return a locked_date as expected.
-
1Good point(s). I assumed it was fixed because of the [status-completed] tag on the related feature request. And yes, I've encountered situations where a
locked_dateon the Post type would've saved me another API call.2019-01-20 21:31:53 +00:00Commented Jan 20, 2019 at 21:31 -
Alas, that feature request was several hamster lifetimes ago, on a different API architecture. ("Regression testing?! We don't need no stinking...")Brock Adams– Brock Adams2019-01-20 21:35:02 +00:00Commented Jan 20, 2019 at 21:35
-
Something like 'This account is not allowed to suggest edits' even though I have 2k rep.2019-01-20 21:40:57 +00:00Commented Jan 20, 2019 at 21:40