Archives
October 2006
10/31/06
10/30/06
10/30/06
10/27/06
10/26/06
10/24/06
AIM Pages Profiles... of Doom!
10/24/06
10/20/06
10/19/06
10/18/06
10/17/06
10/16/06
10/12/06
10/10/06
10/9/06
10/6/06
10/5/06
10/5/06
10/5/06
10/4/06
10/3/06
Tuesday, October 24, 2006
6:21:00 PM EDT
So since we're getting close to Halloween, here's a scary story for you:
There once was a cow-orker of mine named Chris. Like many folks, Chris had an AIM Pages profile. It was a very nice AIM Pages profile, and everyone liked it.
One day, as Chris was walking through the woods to his grandmother's house, he decided to remove a code snippet module from his profile because he was never able to get it to do exactly what he wanted.
This was about the time that there were some problems with the code snippet module, though no one knows if that's related to what happened next.
He deleted the module in the usual way, and hit publish.
From then on, anytime he or anyone else tried to view Chris's profile, their browser (including Internet Explorer, Firefox, Safari, Netscape, AOL Explorer and the AOL 9.0 software) would lock up.
Eventually, up to 5 minutes later, he would get a browser message saying that a script on the page was being unresponsive, so he could hit Stop Script (or Abort), and close out the browser window without crashing.
But he couldn't edit his profile.
He even tried viewing his page using dialup, so he could try hitting the edit button before the full page loaded, but as soon as the rest of the page rendered, it would lock up so he couldn't edit his page.
Finally, he went to delete his profile (in Edit mode, click the "Settings" button at the upper right corner of your page: You'll get the option to delete your entire AIM Pages Profile).
His profile wouldn't delete.
Try as he might, when he tried to delete his profile, he would get an error message saying that there was no profile to delete!
It was all too much for him -- when we went to his cubicle the next day, this was all that we found:
Fortunately, the comments in his Comments Module survived, and his photos were all still stored online, so he could re-select them for his Pictures Module, but the rest he had to recreate.
The odd thing is that there are plenty of code snippet modules in Chris's profile right now, and they all work fine.
As I said, no one is sure exactly why his profile blew up -- it may be related to module problems that were going on before.
This doesn't seem to be a widespread problem, though I'm working with the team to try to figure out why something similar is happening to another person (hi Charley).
If you have an intractable AIM Pages profile problem, let us know and we'll work on getting it fixed.
Thanks -- Joe
Written by aimpagesteam Blog about this entry |
Add to del.icio.us | 
digg this
6:21:00 PM EDT
AIM Pages Profiles... of Doom!
There once was a cow-orker of mine named Chris. Like many folks, Chris had an AIM Pages profile. It was a very nice AIM Pages profile, and everyone liked it.
One day, as Chris was walking through the woods to his grandmother's house, he decided to remove a code snippet module from his profile because he was never able to get it to do exactly what he wanted.
This was about the time that there were some problems with the code snippet module, though no one knows if that's related to what happened next.
He deleted the module in the usual way, and hit publish.
From then on, anytime he or anyone else tried to view Chris's profile, their browser (including Internet Explorer, Firefox, Safari, Netscape, AOL Explorer and the AOL 9.0 software) would lock up.
Eventually, up to 5 minutes later, he would get a browser message saying that a script on the page was being unresponsive, so he could hit Stop Script (or Abort), and close out the browser window without crashing.
But he couldn't edit his profile.
He even tried viewing his page using dialup, so he could try hitting the edit button before the full page loaded, but as soon as the rest of the page rendered, it would lock up so he couldn't edit his page.
Finally, he went to delete his profile (in Edit mode, click the "Settings" button at the upper right corner of your page: You'll get the option to delete your entire AIM Pages Profile).
His profile wouldn't delete.
Try as he might, when he tried to delete his profile, he would get an error message saying that there was no profile to delete!
It was all too much for him -- when we went to his cubicle the next day, this was all that we found:
THE END
OK, so that last bit was a little creative embellishment. What happened was that we finally had to ask the developers to delete Chris's profile, and then Chris had to recreate his profile from scratch.Fortunately, the comments in his Comments Module survived, and his photos were all still stored online, so he could re-select them for his Pictures Module, but the rest he had to recreate.
The odd thing is that there are plenty of code snippet modules in Chris's profile right now, and they all work fine.
As I said, no one is sure exactly why his profile blew up -- it may be related to module problems that were going on before.
This doesn't seem to be a widespread problem, though I'm working with the team to try to figure out why something similar is happening to another person (hi Charley).
If you have an intractable AIM Pages profile problem, let us know and we'll work on getting it fixed.
Thanks -- Joe
Written by aimpagesteam Blog about this entry |
Add to del.icio.us | digg this
This entry has 3 comments: (Add your own)
-
Actually I think the cause of Chris's profile getting into an irrecoverable hang because he put a SCRIPT in a code-snippet module that had a document.write within the script.
-
Hi Joe!
Please pass my thanks and appreciation on to the AIMPages team.
Charley
10/25/06 4:27 PM