4 ms·
Just as a heads up, after I finish an interview question neither button works (I'm an expert or review later). Clicking on each doesn't seem to do anything. The
by dhammack 13y ago
Just as a heads up, after I finish an interview question neither button works (I'm an expert or review later). Clicking on each doesn't seem to do anything. The only way for me to see additional questions is to head back to the homepage and re-click 'run some practice questions.'
- gameguy43 13y agoThanks for the report! Having trouble reproducing on my end ... are you logged in?
- dhammack 13y agoYes, I am. Here's what shows up in the dev console when I click "I'm an expert" PUT http://www.interviewcake.com/api/v1/viewings/ http://www.interviewcake.com/api/v1/viewings/ 403 (FORBIDDEN) angular.min.js:99 (anonymous function) angular.min.js:99 n angular.min.js:95 l angular.min.js:94 DjangoRESTResource.(anonymous function) angular-django-rest- resource.js:12 DjangoRESTResource.(anonymous function) angular-django-rest- resource.js:18 $scope.updateViewing base.js:31 $scope.markAsComfortable base.js:13 $scope.feelExpertPress base.js:15 (anonymous function) angular.min.js:72 (anonymous function) angular.min.js:144 e.$eval angular.min.js:88 e.$apply angular.min.js:88 (anonymous function) angular.min.js:144 x.event.dispatch jquery.js:5095 v.handle
- gameguy43 13y agoGot it. Digging into this now. Meantime, you might try another auth method? There's also this secret page to walk through the questions by hand: http://www.interviewcake.com/all-questions http://www.interviewcake.com/all-questions Sorry about that!
- ceautery 13y agoSame problem. Looks like we're getting a 403 posting to the server after the initial question. I'm logged in with G+.
- fvrghl 13y agoI'm also having the same error
- BellsOnSunday 13y agoSelecting cancel during the login results in a 500 error and long list of django debug information that you might want to tidy up.
- gameguy43 13y agoThanks for the report. Fixed, and keys cycled.
- gameguy43 13y agoI think this error is fixed now. Thanks for the report! Let me know if you're still having trouble.