-
Notifications
You must be signed in to change notification settings - Fork 308
Conversation
Conflicts: configure-aspen.py gittip/models/participant.py gittip/wireup.py
I should've done this on the last commit but neglected to.
Again, should have been done in the merge.
When LyndsySimon started on the accounts elsewhere refactor (#1369) he also started adding support for Google accounts as well. I've made a "google" branch to keep that code around, I'm ripping it out of the elsewhere branch because our first goal needs to be to refactor accounts elsewhere without any user-visible changes.
HTML-escape some things and fix up API for oauth URLs.
|
We were using "Service" but in the `elsewhere` table we use `platform`.
So it turns out that this branch still contains the |
This branch started under an old version of Aspen that didn't require the .spt extension.
This adds a PlatformRegistry to website, which provides access to instances of Platform subclasses, which have a load method that takes a username on the given platform and returns an AccountElsewhere orm.Model. This is all barely working with one test. Surely other tests are broken now, I haven't even checked. Gonna start building back up and out.
I get the following traceback when connecting a Bountysource account:
|
DEBUG is so generic, it's impossible to know what it's for without a comment.
Per IRC, I'm hitting this problem with Venmo:
That's after I switched to using
|
Next:
|
Not pretty but does the trick. IRC: https://botbot.me/freenode/gittip/msg/11471291/
We're using postgres-2.1.2 in requirements.txt and on master.
@@ -26,7 +26,7 @@ if POST: | |||
<h1>Are you sure you wish to sign out?</h1> | |||
<form id="sign-out" method="POST"> | |||
<input name="back_to" type="hidden" value="/" /> | |||
<input name="csrf_token" type="hidden" value="{{ cookie['csrf_token'].value }}" /> | |||
<input name="csrf_token" type="hidden" value="{{ csrf_token }}" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Changaco Why did we change where csrf_token
is taken from?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@whit537 Because: why not ? It's shorter, and now we always get it the same way.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You're right, I flip-flopped the diff in my mind. Thought we were pulling from cookie instead of the other way around.
refactor accounts elsewhere
Squish another #1369 regression
The need for this import entered with #1369.
Currently we have four accounts elsewhere, three useful for authentication (Bitbucket, GitHub, Twitter) and one that can be connected but not used for authentication (Bountysource). These are implemented in a very WET way and we need to DRY it up. This is an old pull request from @lyndsysimon that I brought over from his fork into a branch on the main repo so we can bring more hands on deck.
Bitbucket
pledge via group elsewhere(Note from Changaco: this is not currently implemented)Bountysource
GitHub
pledge via group elsewhere(Note from Changaco: this is not currently implemented)OpenStreetMap
Edit by Changaco: the following aren't possible for this plaftorm, see #1369 (comment)
view elsewherepledgelock - successlock - failureunlock - successunlock - failureTwitter
Venmo