Sitemeter attacks!
posted at 8:37 am on August 2, 2008 by Ed Morrissey
Send to a Friend |
Share on Facebook | printer-friendly
Starting yesterday, Sitemeter has caused thousands of blogs to fail in Internet Explorer 7 for some reason. Both Hot Air and Michelle Malkin sites have been affected. According to Charles Johnson, the problem exists on Sitemeter’s own website. It appears that Sitemeter changed its coding yesterday without warning its users, and without testing it before going live with the changes.
In a way, I feel a little silly posting this, because the people who really need to read this won’t be able to access it, and the people who can read this won’t have the problem. It only affects IE7; all other browsers load the page with no problem. I’m hoping that the message will filter through to our readers and they will start using alternate browsers to access their favorite sites. In the meantime, we are working on disabling the Sitemeter code at both sites to restore full operability.
I use three different browsers for different purposes. Primarily I operate the blog through Firefox, but when blogging, I like to have a separate window for news browsing (I like to alt-tab when writing), and I’ve noticed problems in the past when running two separate windows for Firefox simultaneously. On my laptop, I’ve kept IE7 as the default to open links from my feedreader; on my desktop, I recently switched to Safari. I’m still getting used to Safari, but I believe I like it a little better than IE7 and not quite as much as Firefox. I particularly like the way that it displays history, but don’t like that it doesn’t allow for multiple home pages on startup like Firefox and IE7 does. Safari has only crashed once and doesn’t seem to be the memory hog that both of the others are when running several tabs.
Even if you love IE7, it’s a good idea to have a second browser handy in case issues like this arise. Sitemeter will eventually get its act together, and we’ll have our sites back up shortly. Thanks for your patience.
You must be logged in to post a comment.
Blowback
Note from Hot Air management: This section is for comments from Hot Air's community of registered readers. Please don't assume that Hot Air management agrees with or otherwise endorses any particular comment just because we let it stand. A reminder: Anyone who fails to comply with our terms of use may lose their posting privilege.
Trackbacks/Pings
Trackback URL
Comments
Comment pages: [1] 2 »
I switched over the FireFox yesterday, but IE is working this morning.
Jaibones on August 2, 2008 at 8:43 AM
Ed-
If I use IE7, it seems to be fixed for the hot air main site. If I try to comment on a headline, I am still getting the error.
On another note, for some(not all) of the videos, I cannot hear the sound. I have not figured out which yet, I think the youtube links.
Hope this helps.
dentalque on August 2, 2008 at 8:43 AM
The Samething is happening on Chickaboomer’s Blog, Marty Davis is a E blogger so Google is effected too. The message from ie7 is still popping up on her blog.
Dr Evil on August 2, 2008 at 8:43 AM
Hi Ed,
I use IE7 also and couldn’t get on at all last night (up until about midnight). All appears to be working fine this morning though. Maybe it’s fixed?
IrishEi on August 2, 2008 at 8:45 AM
I reinstalled IE7 and it is working fine. I also downloaded firefox last night and will begin using it today. The Anchoress is the only site that I cannot access with IE7 at the moment. But, as stated above, this is moot with firefox.
Zorro on August 2, 2008 at 8:47 AM
Eh. I was thinking of just taking Sitemeter off my blog until they fix the problem, but apparently, now I don’t have to.
I’m sure it’s fixed. Sitemeter’s livelihood depends on people keeping it.
I doubt they put it out without testing. What probably happened is that it worked on their tests, and didn’t work when it went live. That happens sometimes.
Always sucks when it happens on the day you’re going live with the CEO’s pet project. I know that one from experience.
Meryl Yourish on August 2, 2008 at 8:49 AM
Amazingly, there’s not a single word about this issue at the sitemeter home page.
I’m glad I’m using the non-premium (i.e., FREE) service for my own blog.
They’ve disabled the sitemeter code here and at Michelle’s site, so IE7 users aren’t affected by these two sites.
I just tried pulling up my own blog page with IE7, and got the “operation aborted” error.
flipflop on August 2, 2008 at 8:50 AM
Sage advice right there. Always have a back up plan.
- The Cat
MirCat on August 2, 2008 at 8:50 AM
Whoops…correction. I’ve still got IE6. Shows you how much I pay attention to IE. I use mainly Firefox, myself.
flipflop on August 2, 2008 at 8:51 AM
I found out that if you hit the “Stop” icon (or hit escape) after the main page loads, you don’t get the error. Some sites, like Day by Day, are still affected.
rmgraha on August 2, 2008 at 8:54 AM
Maybe this explains the strange technical difficulaties I had last night. Here at HotAir and other conservative blogs, as well as BlogTalkRadio, as each page was almost fully loaded, I got a dialogue box that said the site couldn’t be accessed, with a single “OK” button. It happened both in AOL and IE. However, there was no such problem with all the non-political sites that I normally visit. I thought that either the Republicans’ actions yesterday had resulted in a blog traffic overload, or some type of sabotage was going on.
Bigfoot on August 2, 2008 at 8:55 AM
Omniweb! No problems! It just works! :)
OldEnglish on August 2, 2008 at 8:56 AM
I am forced to use IE7 when booted to Windows due to the need to run some silly .Net apps. The problem with site meter is definitely not fixed as of this post.
IE7 users can still see the error when going to http://sitemeter.com/
12thman on August 2, 2008 at 8:56 AM
Dozens of sites were hit by this. Mostly on the Right. Huffpost and Kos were available, for example. I spent a bit of time last night cruising blogs. Hot Air. Michelle’s site. Confederate Yankee. Thunder Run. A bunch of them were hit.
Firefox seems to be able to avoid this. Looking at downloading it.
But, it seems that IE7 has “fixed” the problem. I logged on with IE7 this morning.
No, I am not wearing my aluminum foil hat (yet) but, the coincidence of mostly conservative or perceived right wing blogs being hit and left sites being accessible seems to say something about the origin and nexus of last night’s problem.
If I recall, some Obamaniacs did something very very similar to a number of Hillary sites this past Spring.
coldwarrior on August 2, 2008 at 8:56 AM
Yes, I was blocked and sent emails to Allah & MM. I don’t know enough to have thought it was IE7 problem as I got other sites with no problem. I agree with another poster here. You should have a backup plan and/or something to detect the problem.
wepeople on August 2, 2008 at 8:59 AM
It seems that sites that have turned off Site Meter are working again with IE7. Site Meter itself isn’t working.
SouthernRoots on August 2, 2008 at 8:59 AM
wrong
right
12thman on August 2, 2008 at 9:03 AM
12thman on August 2, 2008 at 9:03 AM
Agree.
Still have to wonder about the selection of sites that were accessible and not accessible last night. [Reaching for my roll of aluminum foil as I write...]
coldwarrior on August 2, 2008 at 9:08 AM
If sitemeter can not roll-out error free services for the number one browser in the world it is time to stop using sitemeter and move on.
Wade on August 2, 2008 at 9:10 AM
Yeah. Right now I still have to press “stop” before the headline page is fully loaded so that the operation aborted message doesn’t pop up.
Emilie H. on August 2, 2008 at 9:11 AM
I took sitemeter off my blog last night.
It is still not working with IE7.
Here is the sitemeter homepage.
If you click on this and still see the “Operation Aborted” error message– it’s not fixed yet.
gatewaypundit on August 2, 2008 at 9:14 AM
I was getting by with tapping “esc” right before the page finishes loading. I figured that out AFTER I was scrolling as fast as I can to try to click on the news links before the error pops up (which worked to).
Adapt and overcome - It’s what makes America great.
El Guapo on August 2, 2008 at 9:18 AM
All I can say is that sitemeter code is never allowed in any of my browsers again - no matter which browser I’m using. I’ve never seen such poor deployment practices and I can’t believe that the sites that had sitemeter are not ticked off enough to get rid of it, as sitemeter didn’t seem to care at all. Unreal.
progressoverpeace on August 2, 2008 at 9:19 AM
Ah, the perils of changing ANYTHING on a Friday. I learned not to do that a long time ago!
How many leftie sites did you actually try? I tried a few and got the error on a couple. Crooks and Liars was one, can’t remember what else. Lots of sites on the right didn’t have the error.
Since Sitemeter’s site is still down and this happened to many non-political blogs, I don’t see much chance of political bias here.
MamaAJ on August 2, 2008 at 9:20 AM
I don’t know if it will help, but I only allow cookies for current site, and I don’t allow Javascript to resize or reorder windows. (Omniweb)
OldEnglish on August 2, 2008 at 9:24 AM
To fix click on the menu Tools -> Internet Options. Click on the tab Security. Click on the icon Restricted Sites. Click on the button Sites. Type the text ‘*.sitemeter.com’ (without quotes). Click the Add button.
That will fix the problem on the client side.
Technically this is not a IE7 bug, but rather a problem on the server side. There is an embedded a tag for <SCRIPT HREF=”http://foo.sitemeter.com/foo.js” > inside a block element (such as <TABLE>). That’s a no-no per the standard and results in undefined behavior. In this case when the IE7 sends the TCP SYN packet to fetch the .js script, sitemeter.com is responding with TCP RST packet to abort, and IE7’s renderer bails out of the table format sequence. Ka-blooey.
To fix on the server side you need to move the script tag down to the bottom of the HTML, just before the </BODY> tag.
Gideon7 on August 2, 2008 at 9:25 AM
Sometimes reading the comments on HotAir helps:
FROM:
http://hotair.com/archives/2008/08/01/blackout-pelosi-turns-off-the-lights-as-gop-demands-action-on-drilling/comment-page-11/#comments
WildBillK on August 2, 2008 at 9:29 AM
Normally I would proudly state that I use Opera. However, their latest release crashes nearly every day, even after updating flash/java. I’m not inclined to do a full freakin install from scratch, set up all my mail accounts because they can’t install correctly themselves.
aikidoka on August 2, 2008 at 9:32 AM
Sorry Gideon7, I didn’t see your post here until after I posted my comment above. Thanks again.
WildBillK on August 2, 2008 at 9:32 AM
Although perhaps not technically a standards-compliance bug, you can make the argument that Microsoft ought to be following Postel’s Law better like the other browsers seem to do.
Gideon7 on August 2, 2008 at 9:34 AM
I too switched to Foxfire. Microsoft should sue Sitemeter!
Lonetown on August 2, 2008 at 9:55 AM
OPERA, ED. OPERA. EXCELLENT BROWSER.
auspatriotman on August 2, 2008 at 9:57 AM
FYI, if you use the html code, instead of the javascript, it allows the page to load in IE7. Hits are still recorded, but, the sitemeter button will not show.
William Teach on August 2, 2008 at 10:03 AM
Ed,
I like the picture of the killer bunny from the Monty Python comedy skit you used for this story.
Back in March 2008 I posted a snippet of the skit on my blog about a brave bunny attacking a snake and chasing it up a tree.
WildBillK on August 2, 2008 at 10:10 AM
I have multiple browsers open here all the time and IE7 was and is still failing without modifying the restricted sites in the internet options.
I have two instances of IE open. One is modified and one is not so I can determine when sitemeter gets their fix done.
I run IE simply for a single plugin extension I use with it.
I also have FF3 and Opera open for other purposes and another older browser called Networker (was probably the first tabbed browser).
I have another also open called SpeedResearch which is a heavy customized browser for stock market research.
CommentGuy on August 2, 2008 at 10:12 AM
Opera also has the issue of not able to be using multiple tabs for the home page.
A quick work around for that is to have a folder for your desired starting set in the bookmarks and drag that folder to the main viewing area and it will open all of them in tabs.
CommentGuy on August 2, 2008 at 10:14 AM
Also affects IE6, my friend’s site went down and she uses Sitemeter as well and she has IE6.
She was blaming Microsoft….
AprilOrit on August 2, 2008 at 10:17 AM
Some sites still not working with IE6
Del Dolemonte on August 2, 2008 at 10:17 AM
This kind of foolishness is precisely why we made the decision 12 years ago (OK, we’re dinosaurs) to do our own site-metering on our three commercial web servers after encountering a similar outage from a third-party site monitoring service. It gives us absolute control over changes, as well as allowing us to control precisely what is counted and…more importantly…how it is counted.
The services such as Sitemeter have very nice reports, but we don’t think the security risks, load time penalties, and reliability risks are worth it. We’ve never looked back, as our counting methodology now correlates extremely well with our actual sales: something that the third-party service never was able to achieve.
landlines on August 2, 2008 at 10:18 AM
It appears that Sitemeter is offline.
AprilOrit on August 2, 2008 at 10:18 AM
W3C Standards compliant browser - $0
NoScript Firefox Extension that automatically blocks all javascript code until told otherwise - $0
Watching all the IE users suffer as their “dominant” browser takes a puke on a simple js coding error - PRICELESS
/snarkynerd
Sorry, I just couldn’t resist. ;)
wearyman on August 2, 2008 at 10:19 AM
Interesting info for anyone using Sitemeter -
http://michaelsync.net/2007/04/11/things-you-should-know-before-using-sitemeter
AprilOrit on August 2, 2008 at 10:20 AM
Wrong. It definitely affects IE6 too. I am living proof.
Log on August 2, 2008 at 10:26 AM
It’s just a little bunny rabbit!
Kafir on August 2, 2008 at 10:27 AM
http://blog.wired.com/27bstroke6/2008/08/web-sites-using.html
A number of web sites that use SiteMeter tracking code to monitor the number of visitors to their site are reporting that the code is causing Internet Explorer browsers to crash when users visit their sites.
I haven’t spent time testing a lot of sites, but the Gawker Media sites all seem to be affected. These include Gawker, Valleywag, Gizmodo and Lifehacker, among others.
The problem appears to be affecting IE 5.5, 6.0 and 7.0. Internet surfers using IE to access a site that has SiteMeter tracking it receive a message saying the site cannot be loaded and “operation aborted.” The issue seems to have begun late afternoon Friday.
SiteMeter has not responded to a request for comment and so far has posted no announcement to its web site addressing the issue. But SiteMeter’s blog has a few posts published earlier this week referencing its move to a new platform and changes to its tracking code.
A number of sites are reporting that once they remove the SiteMeter code, the problem disappears and their page loads fine in IE.
Del Dolemonte on August 2, 2008 at 10:30 AM
It always pays to have a backup plan (Firefox, in my case).
I will say that IE8 Beta 1 does fix this, but introduces a few more bugs. I’m running that now, mostly because my feed readers use the IE API to render web pages.
steveegg on August 2, 2008 at 10:32 AM
Man you firefox whores are annoying. You can get javascript blocking addons in IE too. Most of us just don’t bother because we’re not in bed (I suspect in your case it’s quite literal) with a piece of ****ing software. People use IE because it’s there. Every browser I’ve used is a piece of crap as far as I’m concerned but I’ll stick to Maxthon because its interface blows Firefox into the next galaxy.
Darth Executor on August 2, 2008 at 10:33 AM
Damn!!
I just got a new laptop (with the dreaded Vista) and was in the process of upgrading and installing new software last night when this happened.
I couldn’t access MM or HA sites with IE so I thought I had screwed something up with all of the updating I was doing.
So, late last night, I undid several hours of work with a system restore to see if I could fix the browser issue.
Now, I see it wasn’t me at all!! I don’t know whether to feel like a dumbass or a genius.
My wife says the former.
BacaDog on August 2, 2008 at 10:35 AM
You’re both wrong, BacaDog. A genius would’ve gone to Firefox :-)
steveegg on August 2, 2008 at 10:41 AM
LOL! I have Firefox and IE7 installed. Firefox would work, so I thought I had messed up some arcane setting in IE that I’d never be able to fix.
I googled the error message (using Firefox) and got some dire warnings about how difficult it would be to fix, and that it was the worst possible message I could get.
So, I restored.
Shoulda used Firefox to look at this thread and see WildBill’s solution. Woulda saved me alot of time.
BacaDog on August 2, 2008 at 10:45 AM
Poor BacaDog. You just need to be more paranoid and quicker to blame others for problems.
Don’t tell your wife I said that.
MamaAJ on August 2, 2008 at 10:46 AM
Browser preference depends on what you want. I’ve always found Explorer easiest to operate, and prefer it to others.
Unlike some other people, I don’t mind a crash now and then. Since I routinely run 20+ browser windows at a time, I have come to expect the occasional crash as the inevitable price of such heavy usage.
Ali-Bubba on August 2, 2008 at 10:53 AM
I forgot to mention a suuuuuper genius would have went to IE8(B1). Microsoft finally got off their hindquarters to fix the underlying bug.
Now, excuse me while I climb up the branch to the ledge and brush the dynamite residue off my fur :-)
steveegg on August 2, 2008 at 10:55 AM
There was also a new Java update today. Since updating I have not had the problem.
But sitemeter may also have fixed something.
TheSitRep on August 2, 2008 at 10:59 AM
Thanks, Gideon7. I just used your fix and the comments sections at e.g. Hot Air and Ace of Spades HQ are working fine now too and not just on the home pages where they’ve turned off Sitemeter entirely.
I’d just add this caveat to your Security fix:
I did it first typing the *.sitemeter.com with the “www.” because the existing line in the text window included the “www.” URL for Google (my home page), but it didn’t work. So I retyped it just keying-in the *.sitemeter.com and it works fine now, including for opening comments sections like this one.
And for anyone who doesn’t read alot of prior posts but just skips to the page bottom, here is Gideon7’s fix reiterated:
To fix click on the menu Tools -> Internet Options.
Click on the tab Security.
Click on the icon Restricted Sites.
Click on the button Sites.
Type the text *.sitemeter.com
Click the Add button.
That will fix the problem on the client side.
andycanuck on August 2, 2008 at 11:11 AM
Heh. She who must be obeyed is rarely wrong! Please don’t tell her I said “rarely”!
LOL. Where where you with all of this sage advice when I needed you? :)
BacaDog on August 2, 2008 at 11:11 AM
My computer worked fine yesterday a 5pm. I went to eat dinner and came back at 7pm, I could not access mm, ha or several other blog sites.
I am using IE6.
I finally got it going by turning off windows update. I hope I turned update off just as sitemeter repaired their problem, I will update back on later to find out.
allrsn on August 2, 2008 at 11:12 AM
Thank you for the update. That did affect me last night, and it did have me concerned.
BTW, it isn’t so much that IE7 doesn’t work well. It is actually the fact that Sitemeter sucks, and you can tell them so for me. :oP
DannoJyd on August 2, 2008 at 11:12 AM
As one of those elitist Mac users I can only say, what problem? :)
OldEnglish on August 2, 2008 at 11:14 AM
Getting blown up. :-)
steveegg on August 2, 2008 at 11:17 AM
I only read 3 blogs on a regular basis, HA, Michelle Malkin, and Rachel Lucas. I kept getting the message, and thought there was something wrong w/ my computer. Glad it wasn’t on my end.
StephC on August 2, 2008 at 11:19 AM
Microsoft says this is a bug per KB927917. Reported back in October 2007. Affects IE 5.5, 6, and 7. Fixed in IE8.
Gideon7 on August 2, 2008 at 11:21 AM
Couldn’t get in last night either. Switched to Firefox, ask the question why IE wasn’t working, got this response from Gideon:
Sitemeter.com is delivering buggy JavaScript code. To fix IE7: Click on the menu Tools -> Internet Options. Click on the tab Security. Click on the icon Restricted Sites. Click on the button Sites. Type the text ‘*.sitemeter.com’ (without quotes). Click the Add button. That will fix the problem. Gideon7 on August 1, 2008 at 11:48 PM
PROBLEM SOLVED—–SORTA, Now I can’t sign in to comment on IE—-Yo! Gideon….you around?
Rovin on August 2, 2008 at 11:22 AM
I couldn’t get HA or Michelle last night, but assumed it was this operator and not the computer. Switched to the iPhone and it worked fine.
jintrabar on August 2, 2008 at 11:25 AM
FireFox Forever ! ! ! !
dalec on August 2, 2008 at 11:25 AM
If you love IE7 .. [deleted in the spirit of tolerance]
corona on August 2, 2008 at 11:36 AM
PROBLEM SOLVED—–SORTA, Now I can’t sign in to comment on IE—-Yo! Gideon….you around?
Rovin on August 2, 2008 at 11:22 AM
Fixed
Rovin on August 2, 2008 at 11:36 AM
W-H-E-W! My router’s had indigestion lately and I couldn’t get on bunches of sites last night.
Yay! ♫ Not my problem! Not my problem! ♫
eeyore on August 2, 2008 at 11:37 AM
Wasn’t Pelosi singing that tune when she turn the lights out last night?
Rovin on August 2, 2008 at 11:41 AM
As one of those elitist Mac users I can only say, what problem? :)
OldEnglish on August 2, 2008 at 11:14 AM
Awwww, shaddup, will ya! :-)
[Shoulda kept my Mac...an antique now, I suppose. No. I had to buy a Dell.]
coldwarrior on August 2, 2008 at 11:41 AM
Thanks for this post Ed, even though everything is OK now, I was still wondering since I just finished reinstalling my hard drive due to a glitch in the latest Service pack 3 (SP3) from Microsoft. Then THIS happened, the Dell tech’s told me I would have to rewrite my hard drive again because the problem had to do with Media Center not being installed properly, So THIS is really GOOD NEWS to me. :)
abinitioadinfinitum on August 2, 2008 at 11:53 AM
This “specificclick” crap has been haunting me for months now. redirecting my pages to page not found. Thanks April. F*(# site meter!
abinitioadinfinitum on August 2, 2008 at 12:01 PM
I am having the problem on this PC. I just hit the stop button before the ads load and it works fine.
Micheal on August 2, 2008 at 12:03 PM
LOL. Still got my IIe.
OldEnglish on August 2, 2008 at 12:03 PM
Thank you for the note about Site Meter. I am not the greatest on the ol’ computer and I was able to figure it out. If you are on Blogger, all you have to do is get rid of the Site Meter icon. Of course that took me most of last night to figure out! So, this is VERY useful. Hope it is back soon.
righty64 on August 2, 2008 at 1:01 PM
Ed,
I was experiencing some of the same problems and I use IE6. I was still able to access this site and Michelle’s despite error messages which kept popping up claiming that both sites were inaccessible. However, I was blocked out of certain other blogs completely, like Urgent Agenda. (That problem appears to be resolved, apparently.)
DubiousD on August 2, 2008 at 1:10 PM
Why on God’s green Earth would anyone still be using IE?
That’s soooo 8 years ago.
JetBoy on August 2, 2008 at 1:13 PM
Because some people don’t think it’s worth wasting time downloading and installing a browser that sucks almost as much as IE.
Darth Executor on August 2, 2008 at 1:30 PM
I really don’t understand why the blogs continue to use SiteMeter. Google Analytics, which I see that HotAir already uses, should be quite enough. Although, HotAir should upgrade their Google Analytics code to the newer version.
Seixon on August 2, 2008 at 1:40 PM
IE6 is having the problem too… but today it’s not blocking.
Kaptain Amerika on August 2, 2008 at 1:55 PM
because more than 76% of users on the net still use it… we like going with what the masses do… you’ll understand since you believe in God.
Kaptain Amerika on August 2, 2008 at 1:56 PM
It’s working again. I am posting this with IE7.
{^_^}
herself on August 2, 2008 at 2:07 PM
And FireFox works as well.
{^_^}
herself on August 2, 2008 at 2:08 PM
You have now made me realize that Firefox is not some loony-tune leftist thing, but a piece of software conservatives can trust. Thank you.
HotAirJosef on August 2, 2008 at 3:20 PM
This is good news…ie… I thought I was banned from even reading the sites…lol!!!
jerrytbg on August 2, 2008 at 3:25 PM
firefox works less often then IE7 with visTa!!!
jerrytbg on August 2, 2008 at 3:28 PM
Yeah, I did the same thing. Figured it was something loading at the end, and that it would get corrected fairly soon. It was a bit annoying, for a few moments.
IrishEyes on August 2, 2008 at 3:33 PM
Alert the Internets!
Ortzinator on August 2, 2008 at 3:57 PM
Two better alternatives to IE:
http://www.opera.com/download/
http://www.mozilla.com/en-US/firefox/?from=getfirefox
thuja on August 2, 2008 at 4:09 PM
IE7 here. Did have a problem for about two hours yesterday but all better now.
“Windows cannot run script” CLOSE CANCEL.
Usually it happens like that when you have a funked up banner or some such capitalist pig ad on the page. ;)
Limerick on August 2, 2008 at 4:49 PM
Huh? I’ve never had problems on my Vista box … except for the fact that it’s a Vista box anyway…
TheUnrepentantGeek on August 2, 2008 at 5:24 PM
What the h#ll happened last night,I posted
around,7:30PM.,and then I couldn’t get back on
to Hot Air!
Microsoft internet glitch or something!
Every Republican website,OPFOR,Atlas Shrugs,Hot Air,
I couldn’t get in!
Then I tried,HuffPost,Dailey KOS,no problem at all,
in like Errol Flynn,problem free!
Me thinks it was no glitch,Me also thinks the liberal’s
are becoming desperado’s,fairness doctrine and all!ha
canopfor on August 2, 2008 at 5:25 PM
Ed,
You might want to investigate the use of the -no-remote switch to run multiple instances of Firefox with multiple profiles. It should enable you to use one profile for your main browsing/blogging and the other for monitoring your various news sources.
I would set up one shortcut for the news source profile with the -no-remote command line switch:
“C:\Program Files\Mozilla Firefox\firefox.exe” -no-remote -p your_news_profile
Then set up the other shortcut for your main profile:
“C:\Program Files\Mozilla Firefox\firefox.exe” -p your_main_profile
The -p instructs the shortcut to use the specific profile that follows it. Also, using “C:\Program Files\Mozilla Firefox\firefox.exe” -p alone will start the Firefox Profile Manager to create each profile.
Finally, once you are done setting up each profile, run the Profile Manager once more selecting your main profile at that time. This will set your main profile as the default profile to be run when you click a link in another when Firefox is not currently running.
This is a bit of work, but once done, it is much more convenient and much less cumbersome than trying to use the profile manager all the time. Also, use of the Profile Manager does not allow the use of the -no-remote switch for one instance of Firefox and not another instance that I am aware of.
Wildcatter1980 on August 2, 2008 at 5:31 PM
I just downloaded Firefox nice.
Dr Evil on August 2, 2008 at 6:18 PM
There is a fungus among us……..
Seven Percent Solution on August 2, 2008 at 6:52 PM
Comment pages: [1] 2 »