Using IE7 on Win XP Pro SP3 here. I've noticed that most of the PM tabs I open never stop loading -- there's always one more item remaining according to the status bar. It seems like it may be tied to the amount of data being displayed, as e.g. replying to a node, looking at my settings, etc. do not exhibit this behavior. But long threads, Newest Nodes, The Monastery Gate, SoPW, etc. almost always do. So I was wondering if anyone else has seen something similar? One theory is is could be my JavaScript and CSS settings (listed below wrapped in a readmore tag). Another theory is it has something to do with the ISA servers (Microsoft's Firewall and Proxy server product) or the Firewall Client we are using here. Anyway, I thought I would ask as I am really getting tired of that Vista-like spinning circular busy indicator (though I suppose an hourglass really would look worse, still....). Thanks in advance!

SOLVED: As tye indicates in Re: Forever Loading (Community Ads), removing the Community Ads nodelet solved the problem. You can remove it in your Nodelet Settings.

Display Settings: 

/* Not sure why I added this. */
.code { overflow: auto; }


/* Ignore these users */
tr.pmnote-xxxxxx { display: none; } /* xxx  */
tr.pmnote-xxxxxx { display: none; } /* xxx  */
tr.pmnote-xxxxxx { display: none; } /* xxx  */
tr.pmnote-xxxxxx { display: none; } /* xxx  */


/* Increase size of text input areas. */
textarea { width: 100%; height: 25em; }
table.user-settings, 
.user-settings textarea { width: 100%; }


/* Ignore xxxx that works with Firefox */
/*
tr.pmnote-xxxxxx td.reply-body:first-child:before { content: string("I
+gnoring Cop"); }
tr.pmnote-xxxxx td.reply-body * { display: none !important; }
*/

[download]

And for my freenodelet: 

<script type="text/javascript">
// Move nodelets to the left side.
function move_nodelets_to_left() {
   var td = document.getElementById('nodelet_container').parentNode;
   var tr = td.parentNode;
   tr.insertBefore(td, tr.firstChild);
   }

// Execute our snippets after the page is parsed.
var old_onload = window.onload;
window.onload = function() {
   if (old_onload != null)
      old_onload();

   move_nodelets_to_left();

   // Add other free nodelet functions here.
   };
</script>
!-- TABLE FOLLOWS -->

[download]

Elda Taluta; Sarks Sark; Ark Arks

Replies are listed 'Best First'.
Re: Forever Loading (Community Ads)
by tye (Sage) on Jan 15, 2010 at 07:08 UTC

    I recently deselected the "Community Ads" nodelet because it appeared to be misbehaving (their ad server, not the nodelet).

    In my experience, ad servers often end up misbehaving. If the misbehavior becomes annoying, then I configure those ads away. As I recall, InternetExplorer seemed to make ad server failures more annoying than FireFox.

    Before the "Community Ads" nodelet started acting up, I noticed that they had so few ads to serve that the small list of ads being shown was full of duplicates (so it seemed that they were down to perhaps an inventory of 3 total ads at that time).

    If it is indeed acting up for an extended period of time, it might be time to just disable the nodelet. But if it is not doomed, then it might be best to let people decide for themselves.

    In the mean time, I visited anonymously and found the Community Ads nodelet empty so I've now removed it from the default list of nodelets. Those who haven't customized their list of nodelets will no longer see it (including anonymous visitors, of course).

    Does removing the nodelet eliminate the problem you reported?

    - tye        

[reply]
      Yep, removing Community Ads solved the problem. Thanks tye!!

      Elda Taluta; Sarks Sark; Ark Arks
[reply]

Back to Perl Monks Discussion