3

Closed

'JSON' is undefined

description

Started receiving this error when I upgraded to Windows 8 Pro. It is a fresh install with a new download/install of TweetMyPC v3.9.5 alpha. See attachment for full error:
 
Line: 835
Char: 11
Error: 'JSON' is undefined
Code: 0
URL: https://twitter.com/

file attachments

Closed Oct 5, 2012 at 9:30 AM by BasisBit
fixed by BasisBit and confirmed working by ubelong2matt

comments

harshaanepeddi wrote Sep 30, 2012 at 7:01 PM

Same error for me too plz if u find the solution send to my mail id harshaanepeddi@gmail.com

wrote Oct 1, 2012 at 10:59 AM

wrote Oct 1, 2012 at 11:00 AM

dreamrider wrote Oct 1, 2012 at 11:00 AM

Got same error on Windows 7 Ultimate SP1 (x64). Any suggestions?

ubelong2matt wrote Oct 1, 2012 at 1:37 PM

I had Windows 7 Ultimate 64-bit with SP1 before Windows 8 but I must have had an older version of TweetMyPC as I did not have this error. I found information about this error but it can only be fixed by the creators of TMPC, not a user. Windows 7, with the same error, proves that I think. By the way, my version of Windows 8 is 64-bit as well.

BasisBit wrote Oct 3, 2012 at 3:31 PM

hey guys,

I just came back from vacation and will take a look at this problem now.
My first guess would be that Twitter changed its API at the first of october because thats when you all started reporting those problems.

I am on it now - just wait for my fix :)

BasisBit wrote Oct 3, 2012 at 9:15 PM

this problem should be fixed with the new version 3.9.0.7 which I just uploaded. You can install it instantly by opening TweetMyPC and then clicking on About -> Check for Update.
Don't forget to check if everything works using the "ping" comand.

Please confirm that this fixed the problem and also feel free to report about how good TweetMyPC is working in Windows 8.

PS: in case you have a spare serial number for Windows 8 pro (English oder German), I'd love to use it for testing ;-)

ubelong2matt wrote Oct 4, 2012 at 4:58 AM

You are correct, the problem seems to have subsided. I will keep an eye out for another Windows 8 key. If I find one, I will pass it along to you if you still need it. The support I experienced in this bug report was phenomenal!

Thank you,
Matt

wrote Oct 5, 2012 at 9:30 AM

dreamrider wrote Oct 7, 2012 at 12:45 PM

Where I can get version 3.9.0.7? When I click on About -> Check for Update, nothing happening.

dreamrider wrote Oct 7, 2012 at 3:22 PM

Sorry, all is O.K. I'm downloaded install again from http://tweetmypc.basisbit.de/ and it works! Version what I see is 3.9.5 alpha: http://imageshack.us/a/img42/6535/20121007180323790.png
And About -> Check for Update working, too: http://imageshack.us/a/img208/6223/20121007180311226.png
I am glad for error correction in "Download Location"! In the past, can not change the download directory path on other than C: ! Thank you!

BasisBit wrote Oct 7, 2012 at 5:07 PM

it actually already is at version 3.9.7, but it looks like I forgot to change the name (including the versionnumber) of the window - not really a problem. I will update that with the next version.

wrote Feb 21, 2013 at 11:27 PM

Brooksymike wrote Apr 20, 2013 at 12:08 AM

I have just downloaded this application for the first time at version 4.0.4
I'm running Windows 7 home premium

I get the script error that others have mentioned but this is the latest version? Once I say "yes" the program works as required. However if I hibernate it sometimes stops responding to tweets.

Tried to install a previous version which installed ok and did not produce the script error, but it also did not function or respond to any tweets.

Any suggestions.

Thanks

BasisBit wrote Apr 20, 2013 at 1:41 AM

Brooksmike:
check if you have all windows updates installed, no internet explorer addons which could cause this, working access to the titter website and that your antivirus isn't causing this. please also just a debug log of tweetmypc.
Previous versions don't work any more because twitter changed it's API. The sleeping after hibernating/no network connection is known and will be fixed within the next days or weeks.


Best regards,
Stefan

Brooksymike wrote Apr 21, 2013 at 11:56 AM

Ok thanks for the quick response. I ran windows update and it installed a couple of updates. After this or worked without producing the script error. Thanks again.

wrote May 16, 2013 at 11:18 AM