Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Google+ Hangout will not allow "Accept" button activation of D20 terms an conditions.

Hi - spent time trying to search for an answer for this in the forums but to no success. I cannot seem to get google+ or the roll20 app to allow me to "Accept" roll20's terms an conditions of use. My System info. WIndows Vista Firefox 26.0 Javascript enabled Cookies enabled Flash Version not installed. I am trying to launch the roll20 app into my google+ hangout. By going to my campaign and clicking on the launch roll20 in google+ hangout. Everything loads, it asks me to invite people, I decline, then the roll20 app window popup appears asking me if it is ok to let roll20 access such an such features of my google+ At the bottom is a "cancel" and "accept" button. I can only cancel. The Accept button is greyed out and does not work. Help? I have no idea why I cannot accept the conditions and terms. Been trying work arounds for a few hours.... I can run an launch the roll20 no problem from the roll20.net site. I have the same issue in both Firefox and Google Chrome. Neither allows me to operate the "accept " button. Help...?
I know with some terms and conditions you need to scroll all the way through the text before you're allowed to accept them or some have a check box that indicates that you've read through and understand the terms. It's been quite some time since I set up my Roll20 app in hangouts so I don't precisely remember what it looked like, but could you check to see if either of those is the case?
1391792398
Lithl
Pro
Sheet Author
API Scripter
Alternatively, I have occasionally had Google's accept button simply not work (linking Stackexchange sites to my google account is where I've encountered it personally). Reloading and trying again fixed my problem in the past, although I don't know if that will be your solution, since you say you've already tried it in two browsers (which by necessity implies trying it twice).
Can you also verify you have all extensions disabled for a quick test? It's possible an extension is blocking the OUATH request.
Josh- I am not sure I understand what you mean by extensions?
Chuck, Step 2 on this page gives instructions for disabling browser extensions. Did you have any luck with my previous suggestions?
Sarah, there wasnt anything to scroll through. Just a simple box window that said "roll20 will take certain google+ info from me" with options "cancel" or "accept" Accept was greyed out, so I could not poke it. And there was no check box, like you usually would see in like other similar pop up boxes. Thanks for hte extension link. I went through and checked out if any extensions might have been doing something. I had a AVG Safe Search running? ( not sure what that was...) I turned that off. Everything else was either stuff for other games I play regularly, or all shut off. (I did not retry roll20 at that point) But I also went and put roll20.net, roll20dev.net and app.roll20.net into my list of "Safe and Trusted Websites" in my Control Panel >> Internet Options >> Trusted Website lists. Then I restarted Firefox, and tried roll20 on google hangout, and BAM, it works. So.... not sure if it was the extension thing... or my security just locking out the popup accept access button.... Thanks either way everyone for the assist. I hope maybe this post and my description here helps others if similar occurs. ^__^
1391847212
Lithl
Pro
Sheet Author
API Scripter
AVG Safe Search would be an extension created by AVG Antivirus to try and protect you from malicious websites. (Assuming you have AVG installed as your Antivirus software.) It may be a good idea to turn that back on and see if R20 still works in Hangouts.
Glad to hear it got sorted out, Chuck, and thanks for reporting back on how it was resolved. :)