A preserved archive of the Logical Gamers community forums, 2009-2025. The original threads and posts, served read-only. Registration, posting and private messages are gone for good.

Issue with Logical Gaia - LG Button not showing

1.2k views · started by Rog Fulace ·
#1
Issue with Logical Gaia - LG Button not showing
I downloaded Logical Gaia on an older computer I was using on Chrome and it worked just fine.

I decided to hook up my newer PC and install it, and the LG button is missing where it's supposed to be.

I checked Tampermonkey, and it says the script is enabled, so what's going on?
#2
Press F12 in Chrome to open the debugger. Click "Console" on the far right of the top-left menu. If LGaia is giving an error (for why it's not executing), it will be displayed there, though it may not be intuitive which error is from LGaia.
#3
I don't know if this is related to something one of my relatives did relating to Yahoo! Messenger or something, but this is what I get upon Tampermonkey executing the script:

Tampermonkey started
ERROR: Execution of script 'Logical Gaia' failed! Cannot read property 'YAHOO' of undefined
TypeError: Cannot read property 'YAHOO' of undefined
at Object.eval (17:23)
at Object.eval (73:4)
at HTMLDocument.ah (203:50)
at HTMLDocument.eval (http://www.gaiaonline.com/:10:68), 1:24)
at HTMLDocument.<anonymous> (http://www.gaiaonline.com/:10:62)
at TM_do (86:10)
at am (378:25)
at M (204:10)
at n (445:2)
at X (449:85)
#4
That would be the error. Did you download the script using this same account when you installed it on your other computer?
#5
GAMEchief wrote:
That would be the error. Did you download the script using this same account when you installed it on your other computer?


Yes, I downloaded it and used it on the same account.
#6
I mean LG account.
#7
GAMEchief wrote:
I mean LG account.


I downloaded it using this account again on a different computer that only had Tampermonkey installed.
#8
I found out the issue. I found out that my Java wasn't somehow updated to the latest version, now it's fixed.
#9
That shouldn't cause that error, but hey -- if it works.

whisper:
Nothing should have caused that error anyway. Stupid technology!