Expression Crash Tricks

When Expression Web or SharePoint Designer 2007 crashes there are a few simple things you can do to mitigate the event:

Preventive crash applications

First of all download the free applications for your versions of Expression Web or Sharepoint Designer 2007
These drastically reduces crashes.
Open the version of fpcleaner for the version of Ew or SPD07 you are using. Do not open ew from your icons/start menu etc etc,  this way you know EW is ‘clean’ to start off. Then I click both
‘Clear the Hidden “Temporary” Files’
‘Clear the Hidden Cache (*.web) Files’
Each time,  so I recommend  using these, and any time you have a crash even if ew (or sharepoint designer 2007) then goes from a ‘whiteout’ and appears stable again or reopens, close it down and open with the fpcleaner for your version.

Tips and Tricks for Expression Web crashes

Another point to note, sometimes but not always if I take away the ‘focus’ from the application by clicking on another open application or even opening one , and wait a minute. Sometimes it will steady so that I don’t lose the work I was working on. Another trick is to do Control Alt Delete – start Task Manager which opens the Windows Task Manager .. sometimes that ‘steady’s’ ew/spd07 as well but not always.
If you have a crash aversion tips let me know

301 Redirect with FPSE

Tina Clarke
My main Expression Web Help site had not been spidered since the 10th August. Though I added content and changed small bits on the homepage. So I decided to check what I’d not done that I thought I had done. This was twofold.

Getting Google to spider your site

I want to talk about the first part in this quest which was to do with redirecting the www of my domain to the one without as is the link I use and the link I want others to use. So to correct the dilution of my homepage link I needed to do a 301 redirection from one to the other. This domain happens to use a Unix plan with FPSE (FrontPage Server Extensions) installed. So I needed not only to redirect correctly using a 301 header but to make sure I did not break my FPSE.

First I needed to know what code I needed to redirect from one to the other. So I headed off to my favourite SEO Guru Blog to learn more about Basic 301 Permanent Redirect Here I found out I needed to add the following for my particular purposes

To Redirect to

Options +FollowSymLinks
RewriteEngine On
RewriteCond %{HTTP_HOST} ^www.domain\.com$ [NC]
RewriteRule ^(.*)$$1 [R=301,L]

Now I had the code I wanted, the next bit of research was in finding out how NOT to break my FPSE. Fortunately for me Pat Geary had already checked out how to do this and her .htaccess file with FrontPage Server Extensions Tutorial outlined the directions clearly. There was more to come however.

Ernie Secrest of Sea Crest Hosting
goes into detail where FPSE is concerned and explains the three OTHER .htaccess locations in the _vti_bin that also needed modifying if I was ever able to publish again. Sure enough I could not publish after adding the 301 redirect code to the main .htaccess, so I proceeded to do this. A quick check afterwards and I was able to publish once more. I then checked my site was redirecting from the version to version I preferred. Finally I did a header check

The correct version of returned the header code of HTTP/1.1 200 OK => which means Successfully Found. The www version returned the header code of HTTP/1.1 301 Moved Permanently => which is exactly the result I wanted of Moved permanently.

I will continue write about other methods I employed and the resources I used in my quest to have Google spider my domain once more.

Tina Clarke Signiture

Tina Clarke. Microsoft MVP – FrontPage © Copyright 2007. All Rights Reserved