Okay, did some more refactoring and caught some other errors / differences between MySQL and SQLite. Also added the SQLite option in the config setup.

Nice! Good to know.

Sounds great.

Could really use this, especially now that WriteFreely.host is up and running, so I'll get started on it.

Actually, I think this is good for now.

Yep that's perfect, thanks 👍 That way anyone can make changes if needed. I've also changed that default value in the "Create Task" form.

Awesome. Plenty of people asking about that now, so that'll be good. If you want to take the charge on that one, please feel free!

Still need to describe what each setting does, but this is nearly complete.

Great point. This should be relatively easy, so maybe we can get it into the next release.

Some feedback from my initial multi-user testing: so far almost everything looks solid, this is really good work! Only issue so far is something weird going on with scheduled posts. They correctly show as "scheduled" and don't show up for non-auth'd users. But once the published time has passed, the "scheduled" badge correctly drops for auth'd users, but the post doesn't show up for non-auth'd users like it should.

Awesome!! I'll give it a thorough testing this weekend in various configurations and let you know how it looks.

Ah, gotcha. I thought there might be some differences when I was reading through this fork with sqlite support.

Ok cool 👍 let me know if you need anything along the way. Excited to get this in!

Nice! I'm all for adding unit tests for database funcs -- especially with different databases, I agree we should make sure they work consistently.