SD14.2 not responding

[PabloTech]

I'm sure this is an old one, but SD has become almost unworkable on my machine because it continually hangs (for minutes at a time) when trying to navigate from one tab or product to another. I've tried all the usuals - deinstalling and reinstalling, compacting databases etc etc. Nothing makes any difference.
I've sent snapshots to SD who say it works fine on their machines, but I have both 32 and 64 machines here which display the same behaviour. The dummy site that comes with SD seems OK. So it seems to be something about my sites. But what?

Any clues gratefully received.

[NormanRouxel]

This is often caused by code being loaded from external sites. Post an URL of a slow page so we can see what you are using.

[mediamole]

Looking at your site I believe it's the tracking script in your page header that might be the issue.

Try putting a block if statement around the code with IsPreviewMode == "False"

[PabloTech]

Thank chaps, but the issue is not the site behaviour online, there aren't any slow pages or similar. The issue is operating the desktop version of SD14 - particularly navigating between products or between tabs within products. The worst is probably going into the extended info tab, then hitting Page Preview. It can hang for minutes, while I can hear the hard disc grinding away. Something is taking it forever to read up new data.

[NormanRouxel]

None of the expert replies above were talking about your sites online behaviour. They were correctly addressing your backoffice PC's problems.

A quick search for src="http on your site ( http://www.calarecords.com/index.html ) shows:

<script src="http://www.google-analytics.com/urchin.js" type="text/javascript">
_uacct = "UA-1779343-1";
	urchinTracker('acatalog/Brochure.html');
</script>

<img src="http://www.adobe.com/images/shared/download_buttons/get_flash_player.gif" alt="Get Adobe Flash player" width="112" height="33" />

<img src="http://www.calarecords.com/acatalog/CACD0122.jpg" height="80" width="80">

<img src="http://www.calarecords.com/acatalog/CACD0123.jpg" height="80" width="80">

<img src="http://www.calarecords.com/acatalog/CACD77019.jpg" width="80" height="80" align="right" />

<img src="http://www.calarecords.com/acatalog/more.gif" border=0>

<img src="http://www.calarecords.com/acatalog/HP_flower.jpg" width="80" height="80" align="right" />

<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>

If these lines are the same within your Layouts, then every time you Preview, switch between products, etc, your desktop PC is going to try loading those 6 external image and 2 external scripts.

Listen to the advice given above and put BlockIf's containing IsNotPreviewMode around such code.

You can also fix the images you are loading by removing http://www.calarecords.com/acatalog/ from their URL's.

P.S. You're loading http://www.google-analytics.com/urchin.js twice.

Undoubtedly a similar thing is happening on your Extended Info pages so you'll need to apply a fix there too. As well as the lines mentiond above you have:

<script type="text/javascript" src="http://www.google.com/recaptcha/api/challenge?k=6LdkM8ASAAAAAHOnU-7XevJkGUcQMGsPOFCN9pdB"></script>

<iframe src="http://www.google.com/recaptcha/api/noscript?k=6LdkM8ASAAAAAHOnU-7XevJkGUcQMGsPOFCN9pdB" height="300" width="500" frameborder="0"></iframe>

[PabloTech]

Ahhhh OK - thanks to all for all this script and advice. I'm not a programmer, and am learning SD as I go, and all this stuff to me is deep engineering that I have not come across before. I'm still learning when I can use relative addressing for images and when I have to use absolutes, for instance. I daresay my code looks crap to you experts, but unfortunately the original developers we used abandoned Actinic in the V8 days and their chief coder disappeared to Hong Kong! I'm on my own in this, so many thanks for the help.

[PabloTech]

Just to reiterate the thanks to all above from one who needs hand-holding in this stuff. For the benefit of anyone else with the same problem, the big game-changer turned out to be putting the Block If around the entire code in the Recaptcha Layout page. Instant fix - but it's good to be pointed to the other sources of potential trouble.