Currently with other instances, a new post is created under drafts. It should be the users name when no collection was specified.
Description
Description
Status | Assigned | Task | ||
---|---|---|---|---|
Resolved | robjloranger | T586 Support any WriteFreely instance | ||
Wontfix | robjloranger | T645 Collection should default to username |
Event Timeline
Comment Actions
So, the PostParams.Collection field was left out of the JSON because it shouldn't ever get sent along with the payload. Instead it's used to set the API endpoint in go-writeas, e.g. /api/collections/{Collection}/posts. Is there another reason it's needed in the JSON?
Comment Actions
Sorry I missed that part. I admit I was eager to do some work yesterday.
The reason is it wasn't working without it present, which is weird. The posts still went up as drafts. I can test again using the previous version.
Comment Actions
No worries. Yeah, the library should be taking the parameter and using it to change the endpoint, as is done here in post.go
Comment Actions
As mentioned in this GitHub comment, we want to support posting drafts with wf-cli, so we don't want this behavior.