If you’re like me, you could probably careless about the social media chat widget thing that is to the right of the NASCAR RaceBuddy and/or Media Center video streams. I do my chatting in a separate Twitter tab within the browser or a separate Twitter application such as TweetDeck. Not only is the chat in these widgets less than desirable at times, but it also seems to cause the video streams to constantly lag and start/stop when the chat widget updates and scrolls items down/up. This is the primary reason I decided to see if I could stop the chat widget from loading in the browser. You can always move or resize the browser window to hide it if that’s all you want to do.
My main browser is Firefox (version 10.0.2 as of this writing) within Windows XP Home/SP3 and this is what I did: After poking around in the source code for the page, I found a JavaScript file being loaded that most likely handled the chat widget. Using Adblock Plus, I added a custom Ad Blocking filter to block ||cdn.gigya.com/JS/socialize.js from loading. This is what the Adblock Plus Filter Preferences dialog should look like after adding the filter:
Success! No more chat widget on those pages and the video was much smoother afterwards. Note: this will affect any webpage that uses the same script to display a similar chat widget.
I haven’t tried it yet but I suspect adding an entry to the Windows’ HOSTS file for cdn.gigya.com to point to 127.0.0.1 would have the same effect and would prevent all browsers from showing the chat widget (or anything else associated with that sub-domain).
As much as I play the game, you’d think I’d have more posts about EverQuest II. Just never thought my exploits within the game were worth blogging about. However, I thought this tip would be helpful.
Update November 22, 2013: I updated the batch file code below to work with the latest version of Adobe Flash. Every version of flash now uses a unique DLL name of the same version so you have to modify the batch file each time. In my case I am using this in a Windows 7 Pro 64bit environment. You’ll need to run the batch file as an administrator for it to be able to rename the file. I still use this to disable the flash content from the in-game browser.
Update June 14, 2012: With the latest patch on June 13th, 2012, the in-game browser has changed rendering most, if not all, of this information irrelevant, out of date, and/or unnecessary LOL. There will probably be some issues with this new browser framework; however, that will be handled in another post if need be. So far it seems to render pages much better and does seem to handle Flash content. I’ll keep the existing information here though.
The problem is (was) that when using the game’s built-in browser (which is more or less Mozilla Firefox 1.X) it chokes on websites that have Flash (usually ads) in them, such as the popular ZAM EverQuest II site. The newer versions of Adobe Flash just do not play well with this browser causing it to lock up or just simply crash the game. After much discussion in the support forums, I think the following two workarounds are probably the best:
1. Batch File to Disable/Enable Flash
The first is a batch file that you run before starting the game to disable flash and then re-run to enable Flash when you are done playing. The credit for this goes to Tatwi in this post:
@rem echo off
CD C:\Windows\System32\Macromed\Flash IF "%PROCESSOR_ARCHITECTURE%" == "AMD64" CD C:\Windows\SysWOW64\Macromed\Flash\
Of course, you have to remember to run the batch file every time before you start the game and after you stop playing because this affects all plug-in type browsers such as Firefox and Google’s Chrome. It will not affect Internet Explorer. If you’re not familiar with batch files, Batch File Help is pretty good at explaining what they are and how to create them.
2. Add user.js file to game’s mozilla folder
This is probably the best work-around and is the one I use as it disables the plug-ins that are most likely to cause problems from loading in the in-game browser. You’ll want to add the user.js file to the mozilla folder in the game’s installation directory. Credit goes to Jrral in this post.
Since this appears to be a file that is not part of the game’s installation and is, therefore, not checked during the patching process, you don’t have to worry about it being replaced. I have not had the in-game browser cause a crash since making this change.
For your convenience, you can download both files in this ZIP file: eq2-userjs-flashbatch.zip. Hope this helps! 🙂
Update March 8th, 2012: It figures that not long after I write this post, they fix the problem according this March 6th Update. It looks like the \mozilla\greprefs\all.js file was updated with the following change:
// Locate plugins by the directories specified in the Windows registry for PLIDs // Which is currently HKLM\Software\MozillaPlugins\xxxPLIDxxx\Path
pref("plugin.scan.plid.all",false);
If you’ll notice, this is the same as the second line in the user.js shown above. Even though they did correct the issue as it relates to Flash, I will still use the user.js file so it doesn’t load the other plug-ins as well.
Just wanted to take a moment to wish everyone a MerryChristmas! 🙂
Like many, I will be spending it with relatives and hope that everyone has safe travels during this season and manages to keep from getting sick during this time.
WordPress 3.3 was just released and I’ve completed upgrading my blog. Nothing to it really. Just clicked the update button and it did the rest. 🙂 Well, I did back-up the database and directory structure before starting the process. I also had to do my usual code tweaks to vars.php and wp-login.php that I do with every upgrade.
They also updated the Twenty Eleven theme to version 1.3; however, since I am using a Child Theme, I lost none of my changes and after doing a file comparison it looks like nothing has changed within the files that my child theme is using, such as header.php.
I also added a GetGlue widget (to find these, go to the Widgets section of your account settings) to both my blog and main website, and updated the Twitter widgets on both as well. After adding the newer Twitter widgets I needed to adjust some of the CSS to allow for a wider side-bar and also widened the main content area of the blog’s main page while I was at it. There was more empty space between the two than there needed to be. I also adjusted the appearance of the H3 header tag when used in the context of a post. It looks cool as a widget title in the side-bar but was getting lost in posts as it’s smaller than the normal text. Anyway, it looks fine now:
H3 header tag In a post.
Here’s the changes I made in my theme’s style.css file to make these changes: