-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
I've got my plate full for the next couple of weeks, but after that I
can probably pop in and have a fiddle.
Cheers
Jack
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iQEcBAEBAgAGBQJP5SV+AAoJEI3j92WSe+b31E8H/3UcGd15xxG+NWwVQYPghDhp
hnpFBQ2imD0FpzA6itBTPuSOh/Gz7MgUVxMF7O88ocCHDx5RxkuepSBIVkyz31iH
jTmh08+m1azk5/bYk538AZrUixFiulrr/fioF783TcfKqJR/J1FXUe7GAfMQqsFv
Fpz8EqYy12BbsMAQ/omeaFDAWxE7V2Cjdqo/PbHb8DPWJrAqlOHKpJoIM0w2Z+HD
otoBCHSyXLuD7PjHnA1eXiOMQC8lwJCkXfCcqIyaHFm6Lao3oYMQkcuzjWnuN24m
j1B6hZCXLIja/WENUz3j10vJM4R5VJnWiTq+6blwrVifPMoROwBl3o5Rgw41M+8=
=i6WJ
-----END PGP SIGNATURE-----
Good news and bad news.
The good news is, we diagnosed the 'badtoken' problem. In fact, it's fixed
through a hack to AuthDjango, as discussed on OH-Dev!
The bad news is I have no idea what is going wrong now because I can't quite
understand MeetBot's configuration.
I'm bumping the priority of this down for now.
Deassigning myself due to lack of time. Anyone is free to grab it; if they need
to patch the AuthDjango plugin then do so and I'll happily commit patches to the
repo once reviewed.
Hmm, this seems at face value unrelated to the central login system - the site
login works fine (now that I have enabled password login for sufjan) but the
actual API edit call returns:
APIError(u'badtoken', u'Invalid token', None)
It is possible that something in the API is being unintentionally affected by
the AuthDjango plugin. I'll have to dig deeper...