Addressed those issues in most recent commits.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Jun 20 2019
Jun 18 2019
Jun 17 2019
Just opened a pull request (GH#123) for this. I still need to verify that data isn't leaking on some ActivityPub endpoints (namely nodeinfo and webfinger), but the core of everything is there and ready to try out.
Jun 16 2019
Jun 15 2019
Jun 14 2019
Jun 13 2019
An authoritative source for checking the current version number: https://version.writefreely.org
Jun 10 2019
Jun 9 2019
I threw together an offline importer for this: rWFM / https://github.com/writeas/wf-migrate -- for reference in building this into the web application.
Jun 8 2019
Jun 7 2019
This could be reopened as a feature request.
Jun 6 2019
Will do.
I'd say the default behavior should be #1, to generate a unique slug for the imported collection.
Commenting here since this affects all the child tasks:
Jun 5 2019
Here's a library I built to start this rolling: https://github.com/writeas/zip-import
I also put up #30 CLI which returns the errors during delete to the user. Then this can close.
Assuming the #117 fix works in your testing, after reviewing everything I do think this is the right solution.
Jun 4 2019
Just to mention, here's some prior art on publishing text files via the API: https://github.com/writeas/writeas-api/tree/master/examples/go-text-importer
This might be good to do in the near future -- certainly before v1.0 -- because of how much easier it'd make the setup process.
Jun 2 2019
Jun 1 2019
May 31 2019
May 30 2019
May 21 2019
May 20 2019
May 17 2019
Thanks, this all makes sense.
May 14 2019
I'll necrobump this and point out that I think @gytisrepecka is talking about something I'm referencing in T576 (a landing page).
So this is likely a comment that is more meta than the ticket itself, but I think that I'd like the "story" to be something like:
@agd Working on this now. I started off making it so that when a user is unauthenticated, all blogs and posts return a 404 (to not reveal the existence of any blog). But I'm wondering if it'd be better to send a user to the login page, instead, for better convenience. If so, we could still obscure existence of individual blogs by simply sending all routes to the login page when unauthenticated. This could be the same for the API -- all routes would just require authentication.