Post subject: Fixing Socialite on WDP Posted: Sat Feb 11, 2012 6:40 am
1337 Beta Collector
Joined Wed Sep 09, 2009 2:17 am
Location New Jersey, USA
Favourite OS 6.2.9200
I found a way that someone posted on pastebin to fix the problems Socialite has on the WDP. Enjoy!
Socialite for Windows Developer Preview workaround ---------------------------
As you may know, the Socialite app in Windows Developer Preview has a bug that doesn't let you log in. Luckily, this can be sidestepped with this workaround. It's dirty, it's unstable, it can be confusing to some, but it works and that's pretty much what we want at the moment.
1. Gathering info -------------------- First of all, you well need to gather some info from your Facebook profile. You will need:
- Your profile ID (8-11 digit number) - Socialite authorization token
Profile ID If you don't have a username on Facebook, go to your profile page and look at the URL. It should look something like http://www.facebook.com/profile.php?id=##########. Copy the numbers that come after "id=" into any empty text file for future use.
If you do have a username, go to http://graph.facebook.com/<username>. Replace <username> with your username. You will be asked to download a small .js file. Download it, open it in Notepad and look for the "id" field inside. This is your number. Save it for future use.
Socialite authorization token: Open up Internet Explorer and follow the link below.
If it asks you to log in to Facebook, do so. If it asks you to allow Socialite to post on your wall etc., click on "Allow". Eventually you will get to the page that says "Success". Look at its URL and copy the long string of characters between "access_token=" and "&expires_in". Save it somewhere with your profile ID for future use.
2. Modifying the code ---------------------- Open up the Control Panel from desktop. Change the view to "Large icons" or "Small icons" if necessary. Go to "Administrative Tools" and double click "Computer Management". On the left pane, expand "Local Users and Groups" and select "Users". In the middle pane, double click on Administrator and uncheck the box that says "Account is disabled". Apply changes, press Ctrl-Alt-Del and click on "Switch Users". You will see the Administrator account along with your normal account. Log in as Administrator.
After logging in, open up Windows Explorer and go to "C:\Program Files\Applications". This is a hidden system folder, so to be able to see it, you need to unhide hidden and system folders in Folder Options. If you still don't see it try "C:\Program Files (x86)\Applications". It might be in there, I'm not sure.
Once you're in Applications, open up the folder that starts with microsoft.socialite. Find a folder called js and open up Socialite.js with Notepad. Find this block of code:
Insert your profile ID between the quotes in the first line and your authorization token between the quotes in the second line. Delete or comment out (put // in the beginning of the line) the last two lines, then save the file. If it doesn't let you save, go into the file's properties and go to the Security tab. Click on Edit, select the Administrator account in the top list and check "Modify" in the bottom list. Apply changes and try saving the file again. Log out of the Administrator account and log back into your normal account.
Go into Task Manager (Ctrl-Shift-Esc) and check if Socialite is running. If it does, end it. Run Internet Explorer and make sure you're logged into Facebook. Finally, open Socialite and, hopefully, you will see a menu instead of a log in screen. Good job, you!
----------- Other stuff ----------- Since this is a temporary workaround, there are a few limitations. If you want to log in with another Facebook account, you will need to do all these steps again because the authorization token is tied to your Facebook account. Also, I would not recommend logging out from Socialite, although I haven't tried to do that.
If you get permission errors when you're trying to modify the application code, ask around on Facebook, I'll probably answer you or modify this document with instructions on resolving this issue. If you have any other issues, ask around on Facebook, but please do not post your authorization token, it's a huge security risk.
Now, this was posted on the 8th and did state that it could be "updated"