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

Got em. Will report back when I have some time to test.

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
the
plug
to upgrade to IE7 at the top of my web page so viewers can read
it as
it
crashes in IE6. Now I have computer techs criticizing me for
advertising
IE7 as it has some bugs. I can't seem to win here. I guess I
still
don't
understand why my website worked in IE6 before I made the ISP
switch
to
another provider. Also, my second website works fine on either
IE6
or
IE7.
My current provider doesn't think that it a problem caused by
them.
They
think it is in the coding, causing the crashes. I just need a
temporary
fix
until I have time to recreate the website in Dreamweaver (which
will
not
be a
quick task). I also have some people recommending Front Page
vs
Dreamweaver. What ever I do next, I don't want to be sorry.
Any
words of
advice?

"BlueEsq" wrote:

Hi,

As you'll all recall, I was having trouble with this as well
some
weeks
back. Everything IEv6 or lower was crashing the browser. I
upgraded
one
of
the PCs that was experiencing problems with IE7, and the
problem was
solved.
This isn't really a solution, as you'll still have many people
hitting
the
site with v6 or lower. What I've done to combat this issue is
list
that
the
site's best viewed with Firefox or Netscape in my advertisement
for
the
business (the Publisher site works flawlessly with those two
other
browsers).
I just don't have time to switch over to an Windows platform on
my
server,
and see if the switch from unix to windows solves the problem I
was
seeing on
IEv.6. I'm just going to hang in there until more PCs are
ugraded to
IE7...and sit it out.

It seems that Publisher sites are very hit-and-miss with IEv6
and
lower,
once you've installed 7 on your machine (specifically, the
machine
that
you
use to build and upload the site).

It's a frustration. However, although I do have Dreamweaver...I
can't
seem
to leave Publisher! (even though I should) Grrrrr....

"DavidF" wrote:

This is a rarely occurring problem that no one has solved
definitively.
Your
comment about IE7 fixing the issue is contrary to another
poster a
few
weeks
back.

One of the potential reasons for this is hosting the site on
a
unix
server
vs. a windows platform. Did you switch to unix?

DavidF

"LBorchert" <LBorchert@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message
news:D441E450-6BEF-4479-A721-A554C5DB2EFE@xxxxxxxxxxxxxxxx
IE explorer shuts down every time I attempt to view my
website
www.cityofsidney.org I installed the IE 7.0 as per our
current ISP
which
fixed my problem and I now can view the website, although
it
does not
help
other viewers if they are still using the older version.
I
recently
switched ISP's and had no problems with the previous ISP
when
using
the
older version of IE. Please advise.











.

Relevant Pages

  • Re: My browser shuts down when attempting to view my website
    ... or compress them from within Publisher: ... check with your ISP and see if they have ... Windows servers in addition to Unix, and if it is possible to switch you if ... When checking the website through other ...
    (microsoft.public.publisher.webdesign)
  • Re: My browser shuts down when attempting to view my website
    ... I am running IE6 SP2 on this computer, and it crashes, albeit not so ... or compress them from within Publisher: ... check with your ISP and see if they have ... When checking the website through other ...
    (microsoft.public.publisher.webdesign)
  • Re: My browser shuts down when attempting to view my website
    ... or compress them from within Publisher: ... check with your ISP and see if they have ... Windows servers in addition to Unix, and if it is possible to switch you if ... When checking the website through other ...
    (microsoft.public.publisher.webdesign)
  • Re: My browser shuts down when attempting to view my website
    ... having problems with the new ISP. ... In a nutshell: gov website was started ... the least of which that using IE7 apparently ... Publisher sites don't work well in FF, so that isn't too viable either. ...
    (microsoft.public.publisher.webdesign)
  • Re: whats the difference ?
    ... If you are building a website that has 90+ pages, you should probably switch ... the more difficulty you will have managing it with Publisher. ... Bottom line is no serious web designer would choose Publisher to build ...
    (microsoft.public.publisher.webdesign)