Re: My browser shuts down when attempting to view my website

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Lori,

I'll dance a bit of jig myself. I appreciate you taking the time to work
through this, and the experiments I suggested. You helped solve an issue
with Publisher websites that has frustrated us for some time. So, you are
very welcome.

Another tip. Open your index_files folder in Windows Explorer on your
computer. Then you can look through the file sizes of all the images to spot
the ones that are very large. One example is a map in jpg format that is 1.5
megs! Do you realize that this picture alone takes about 6 to 7 minutes to
load with a dial-up connection? Convert it to a 72 dpi, gif at around 30%
compression, and it will look better, and you will probably reduce the size
down to less than 115 kb, as just one example. Also be sure to size the
image in the third party program to the size you want to see on your
page...and then scale it to 100%, and you will get the best quality image.

Good luck.

DavidF

"LBorchert" <LBorchert@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:643F5952-C62A-4671-B128-E4185A072148@xxxxxxxxxxxxxxxx
THANK YOU, THANK YOU, THANK YOU! I made sure all my images were in jpeg
or
gifs and guess what! NO MORE CRASHES in IE6. I never knew before your
post
that I could view how my images were saved (Graphic Manager). I made sure
I
rated your response, David. I am smilin' right now and dancing a happy
little jig. ~ Lori

BTW-Next on the agenda is resizing. I did on a few and it makes a lot of
difference. : )

"LBorchert" wrote:

David,

I will work on the suggestions today and get back with you on the
results.
I thought I had my images compressed, apparently I messed up. Thanks
again.

Lori


"DavidF" wrote:

Lori,

I did some follow-up this morning. While studying the HTML output from
your
file, I saw that the wmf files were converted to wmz files during the
Publish to the Web process of producing the html files. I then found a
reference where wmz files could crash IE. I also found that the .bmp
file
was converted to emz file, though no reference about it crashing IE.

With this information in hand, I reviewed another file, another poster
sent
me back in August, who was having the same problem. I had also posted
his
site on my windows platform host, and once again it loaded ok, but
moving
his site to a windows host wasn't practical...not that it is for you.
This
time when I looked at his file I noticed he too had used wmf files
extensively.

I would suggest that you convert the wmf files to gif formats, reinsert
them
into your document, produce new html, and upload it. At some point you
really should reduce the size of all your images as per my past post,
but I
would be curious if the conversion of wmf to gif in your Pub file will
solve
the crashing problem.

DavidF

"DavidF" <Nope@xxxxxxxxxx> wrote in message
news:u2KyVupOHHA.2140@xxxxxxxxxxxxxxxxxxxxxxx
Lori,

I published the three pages to my webhost which has a windows
platform,
and it does not crash IE6.

I did find two things on the home page and the Calendar page, that
might
be contributing to, or even cause the pages to crash. One your home
page,
page 1 or your Pub file, you have a Mapquest map image. Go to tools >
Graphics Manager, and that file is called worldmap.wmf. You should
only be
using .jpg, .gif, or .png formatted image files in a web site. You
also
have the bookcover of Lynchings...as lynchingw.bmp...convert it too.

One the third page, the Calendar page, you have another .wmf
image...the
judges gavel.

I am hoping you have an image editing program. You should convert all
three of these images to either a .jpg or .gif file. I would
recommend
.gif files for maps, icons, etc where there are few colors. I get
smaller
file sizes and faster loading images, and they are more clear than
jpgs.
Use .jpg for more images with lots of details and colors...

While you are at it, you also have two "images" without any
extensions on
page two...the compasses "symbol" on the maps. One is hidden behind
the
smaller map...use the arrange tool to bring that one to the front. It
appears that these are .emf files, and they too should be converted
to
.gifs. And for that matter while you are in the graphics manager,
look for
other images throughout your site that are incorrectly formatted.

As I said, the one thing in common with the home page and the
calendar
page is your use of .wmf images. Change these to .gifs, along with
the
other images I spotted, and see if that makes any difference.

But before you republish, you also need to reduce the size of those
images. The html output for just those three pages was close to 3
megs...it should be FAR less than that. You can compress them through
Publisher. Read this reference: Compress graphics file sizes to
create
smaller Publisher Web pages:
http://office.microsoft.com/en-us/publisher/HA011266301033.aspx

Though compressing them via Publisher will help, if you want your
images
to look the best they can, then you should size them, and optimize
them
before you insert them, and then scale them at 100%. If you select
the
image > Right click > Format picture and look under the Size tab, you
will
see the scale. If you don't have an image editor such as Adobe
Photoshop...or Photoshop Elements, you can get a freebie here that
works
well:
http://www.irfanview.com/

Let me know if changing out the pictures to the proper gif or jpg
format
helps with the crashing problem. If not I will keep looking, but at
least
it does appear that for some reason if you use a windows platform,
the
site will not crash.

DavidF

"LBorchert" <LBorchert@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:E8FDFD50-E32C-4A11-9DB2-636E41D06E8B@xxxxxxxxxxxxxxxx
David, I sent the files per your request on 1/17/07 11:51AM MST.
Lori

"LBorchert" wrote:

David,
I will try the "experiment" tomorrow (1/17). I have been busy at
work
doing
other things and that is as soon as I can get to it. I do
appreciate
the
time you are taking to help me out. If all goes well, I will send
it to
you
tomorrow also. It is mind boggeling!

"DavidF" wrote:

I am running IE6 SP2 on this computer, and it crashes, albeit not
so
quickly?? I did notice that you have some large images on the
home
page that
did not load. Though a complete stab in the dark, if you have a
third
party
image editing program, resize and optimize the images before you
insert
them, or compress them from within Publisher: Compress graphics
file
sizes
to create smaller Publisher Web pages:
http://office.microsoft.com/en-us/publisher/HA011266301033.aspx
I doubt that it will make any difference, but it will speed up
the
loading
page...if we can ever get it to load without crashing.

If you are open to it, and before you change anything about your
Publisher
file, do a Save As of your Publisher file, and save it as
sidneytest.pub.
Delete all the pages except for the home page, the calendar page
and
one
page that works ok, and save the changes. Then send it to me by
way of
http://www.yousendit.com/ Send it to publisherhelp at no spam
gmail
dot com
.. Remove the obvious, and please don't post the address without
munging it
up. I really get enough spam already.

I'll then give it a look, and also test it on my web host which
uses a
Windows platform. In the meantime, check with your ISP and see if
they
have
Windows servers in addition to Unix, and if it is possible to
switch
you if
my experiment works.

DavidF

"LBorchert" <LBorchert@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:1D269ECA-B171-416B-9D60-095B8FB98877@xxxxxxxxxxxxxxxx
I took your advice David and reconstructed my website starting
with
my home
page. I noticed that I inadvertantly linked my home page to
itself
on an
object that I had inserted. When checking the website through
other
co-workers computers - that still use IE6, the "crashing" was
"fixed" on
one
and still crashes on two others. The computers that still
crash are
new
computers - could this have anything to do with SP2? I thought
I
had the
"fix" that I needed but I still need to work on it.

"LBorchert" wrote:

Thanks DavidF. I guess I just wanted a starting point. I
just
don't
understand why the website worked with no problems with one
ISP and
I am
having problems with the new ISP. In a nutshell: gov
website was
started
with one ISP and switched to a new ISP. No crashing with
first ISP
and
IE6.
Crashing began immediately with new ISP and IE6. After
upgrading
to IE7
with
new ISP - no crashes. Second website started with new ISP in
IE6 -
still
no
crashes. Doesn't make sense to me. I was told that the
website
only
crashes in IE6 on the Home Page and the Calendar page. Could
this
mean
it is
a coding issue? I did the detect/repair and review issues. I
will
take
your
advice and "basically" rebuild my home page to see if it is
the
problem.
I
appreciate all the time you each have spent giving me tips.
Thanks
to
all.

"DavidF" wrote:

Excuse me for jumping in here, but BlueEsq and I have
already had
this
conversation.

The Unix server vs. a Windows server issue is just a guess
solution.
This
issue was investigated by David Bartosik with MS, and though
no
absolute
solution was determined, MS felt it might be because of the
Unix
server.
Don't ask me why. The fact that you did not have a problem
before
changing
to a Unix server led me to ask you if the server was Unix,
and
according to
Rob, it is. One POSSIBLE solution for you is to see if your
ISP
could
switch
the site over to a Windows server...many ISPs offer both.
This
would be
your
temporary solution, as you will not find MS patching Pub
2003 to
fix
this
problem...for a lot of reason, the least of which that using
IE7
apparently
fixes the problem.

I can see why you are getting static for recommending IE7.
It is
having
its
own set of problems. And as per BlueEsq's solution to
suggest
using FF,
many
Publisher sites don't work well in FF, so that isn't too
viable
either.
I
would suggest that since your one site works well and the
other
doesn't,
then figure out what you are doing different...and don't do
that.
That
may
sound a bit facetious, but if it were me, I would take the
Publisher
file
that is crashing IE, and start "deconstructing" it. Study
it, and
look
at
what techniques you used that are different, and look for
the one
that
is
crashing the site. You might need to drag most of the design
elements
off
the page, and then add them back, one at a time to determine
what
the
problem is.

Ultimately since this is a government site, you should
probably
work
towards
moving to Dreamweaver or another program that is
specifically
designed
for
building websites. Publisher is a DTP with limited web
building
capability,
and even if you solve this problem, ultimately you will come
up
against
something else. It is fine for a basic, simple, static
website,
but you
should probably be using Dreamweaver...or something else.
Frontpage is
being
replaced by two new programs, neither of which is easier
than
FrontPage.
http://www.nvu.com/index.php has been recommended, and is
free.
And
also
Serif WebPlus 10 sounds like it will be easy to use, and
work
better
than
Publisher. I guess what I am saying is that I think that
your
time
would be
better spent learning new software that won't limit you as
much
as
Publisher. Good luck.

DavidF

"LBorchert" <LBorchert@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:C532FF26-D88F-43E0-82D3-C568B25B3F43@xxxxxxxxxxxxxxxx
Hi Blue~

I, too, have Dreamweaver. I attended a class and it blew
my
mind.
Publisher does seem to be so much easier. I may have to
just
bite
the
bullet and do the switch. My boss has been getting
numerous
calls
saying
our
site is not user friendly and I must do "something" soon.
I
put in


.

Relevant Pages

  • Re: Attention David F
    ... resampling and resizing images to 96 dpi in Publisher. ... I'm glad my pages load decently. ... Web Plus does seem to offer a lot of features that you ...
    (microsoft.public.publisher.webdesign)
  • Re: My browser shuts down when attempting to view my website
    ... three of these images to either a .jpg or .gif file. ... smaller Publisher Web pages: ... check with your ISP and see if they ... When checking the website through other ...
    (microsoft.public.publisher.webdesign)
  • Re: Wrong position of animations in ie8
    ... code produced by publisher I don't get that to work. ... preset at 96 dpi, and thus the Publisher web pages rendered correctly at 96 ... As you noted images can be increased or decreased ... also means that if you want to use these swf file animations, ...
    (microsoft.public.publisher.webdesign)
  • Re: My browser shuts down when attempting to view my website
    ... and faster loading images, and they are more clear than jpgs. ... You can compress them through Publisher. ... does appear that for some reason if you use a windows platform, ... check with your ISP and see if they ...
    (microsoft.public.publisher.webdesign)
  • Re: Image size publisher 2003
    ... Then go to one or more of the images, ... Publisher file, and producing it with a second Publisher file, and ... When I pre view as a webpage it works great, but when I upload to server ...
    (microsoft.public.publisher.webdesign)