MS Pulisher 2003 Links

[Kristi61]

I'm extremely electronically challenged and I need some coaching. My website
http://www.lacyquarterhorses.com has problems with Mozilla browsers. The
navigation bars appartently work properly, but the links from the catagory
pages do not work on Mozilla browsers. Are you saying that I need to save a
copy of my website and, using the copy, ungroup all objects page by page, and
the resulting copy will display links properly on Mozilla? Will it eliminate
some of the heavy MS Publisher code that the search engines seem to dislike?

Thanks so much,
Kristi

 

[DavidF]

If you build navbars with the Publisher 2003 and 2007 wizard it will not
render when the page is viewed in IE8. If you ungroup that navbar it will
render, but you also uncouple the navbar from the wizard. This means if you
add a new page or section you will not be able to automatically add that to
the existing navbar and propagate it through out the site. That is why we
suggest that if you anticipate adding sections to your site and to the main
navbar that you ungroup the navbar from a copy of your main Publisher file.
This advice is mostly applicable to the person who is still building their
site in my opinion. If you don't anticipate adding sections and thus buttons
to your main navbar, then I would go ahead an ungroup the navbars on each
page and not worry about making a copy each time. If at some point in the
future you wanted to add a section to the main navbar, you could always go
to insert > navbar > existing navbar and just insert a new, wizard connected
version of your navbar on each page.

I realize this is bit confusing, but the bottom line is that you must
ungroup all design elements on each page of a Pub 2003 in order for those
elements to render in IE8. This includes not only the navbar but also any
other design elements on the page. For example on your Stallions page:
http://www.lacyquarterhorses.com/index_files/horsesforsale_stallions.htm
This page renders just fine in IE7, but in IE8 the navbars do not render nor
does the banner elements at the top of the page. It appears you have the
banner grouped and you should ungroup those elements and save that change
permanently. Just click on/select the group and then click the grouping icon
or go to Arrange > Ungroup if you prefer. Also on that page the heading:
'Quarter Horses for Sale: Stallions' also does not render in IE8, so I would
guess that it too is grouped with some other element.

Now as per FireFox, grouped elements are rendered as a combined image. For
example if you group a text box with an image box, you will get a combined
image of the two, and the text will be converted to an image and kill any
link that might be inserted. So it is important to ungroup all design
elements on each page of your publication for that reason too. You can see
your banner is one big image:
http://www.lacyquarterhorses.com/index_files/image9653.gif
If you ungroup those elements they will appear as individual elements.

Now if you look at the text under each horse picture that describes the
horse and provides links to more pictures and more information, that text
has been converted to an image in FF. If you left click and drag and try to
copy it you will be unable. This kills the links, and that is what I assume
you were talking about links not "displaying in Mozilla". Now this may be
caused by linking the text box to another element, but it can also be caused
by several other formatting issues. It is hard to tell from here and you
will have to test to see what is converting the text into an image. If it is
grouped, ungroup and see if the text is text and the links work. If it is
not grouping, it might be the border you have around it. Try removing the
border or using a simpler, thinner black border. It might also be the 'fill
color' if you are using a fill color in the text boxes. Some gradient fills
and other fills will convert text to an image in FF. In general experiment
with removing grouping, fill colors, borders until you find out what is
converting your text to an image. Once you find that you will functional
links.

If grouping, fill colors, or borders are not the reason for the text being
converted, post back with very specific description of how you are building
those text boxes with the images of the horses. Are you for example
inserting the images of the horses into a text box and formatting in-line?

DavidF

 

[Kristi61 via OfficeKB.com]

David,

Thank you for your detailed response! Of course the design checker doesn't
reveal this aspect. My design used a MS Publisher template that I modified
for design purposes and to make better use of page space...sounds like it may
have been a mistake. If I make the modifications that you describe, will the
website display properly on ALL browsers? Do you know if these modifications
will improve some of the text / code ratio?

Since I only update the website 2-3 times a year and may change navbar
elements, it sounds like I should make my modifications to the original and
make a copy to use for the ungrouping steps and publish the copy...is that
right?

When published to the web, do you know if there is a difference in the
browser compatibility or html code between an MS Pulisher file saved as a MS
Publisher file and one that was saved as an html document?

Many Thanks,
Kristi

If you build navbars with the Publisher 2003 and 2007 wizard it will not
render when the page is viewed in IE8. If you ungroup that navbar it will
render, but you also uncouple the navbar from the wizard. This means if you
add a new page or section you will not be able to automatically add that to
the existing navbar and propagate it through out the site. That is why we
suggest that if you anticipate adding sections to your site and to the main
navbar that you ungroup the navbar from a copy of your main Publisher file.
This advice is mostly applicable to the person who is still building their
site in my opinion. If you don't anticipate adding sections and thus buttons
to your main navbar, then I would go ahead an ungroup the navbars on each
page and not worry about making a copy each time. If at some point in the
future you wanted to add a section to the main navbar, you could always go
to insert > navbar > existing navbar and just insert a new, wizard connected
version of your navbar on each page.

I realize this is bit confusing, but the bottom line is that you must
ungroup all design elements on each page of a Pub 2003 in order for those
elements to render in IE8. This includes not only the navbar but also any
other design elements on the page. For example on your Stallions page:
http://www.lacyquarterhorses.com/index_files/horsesforsale_stallions.htm
This page renders just fine in IE7, but in IE8 the navbars do not render nor
does the banner elements at the top of the page. It appears you have the
banner grouped and you should ungroup those elements and save that change
permanently. Just click on/select the group and then click the grouping icon
or go to Arrange > Ungroup if you prefer. Also on that page the heading:
'Quarter Horses for Sale: Stallions' also does not render in IE8, so I would
guess that it too is grouped with some other element.

Now as per FireFox, grouped elements are rendered as a combined image. For
example if you group a text box with an image box, you will get a combined
image of the two, and the text will be converted to an image and kill any
link that might be inserted. So it is important to ungroup all design
elements on each page of your publication for that reason too. You can see
your banner is one big image:
http://www.lacyquarterhorses.com/index_files/image9653.gif
If you ungroup those elements they will appear as individual elements.

Now if you look at the text under each horse picture that describes the
horse and provides links to more pictures and more information, that text
has been converted to an image in FF. If you left click and drag and try to
copy it you will be unable. This kills the links, and that is what I assume
you were talking about links not "displaying in Mozilla". Now this may be
caused by linking the text box to another element, but it can also be caused
by several other formatting issues. It is hard to tell from here and you
will have to test to see what is converting the text into an image. If it is
grouped, ungroup and see if the text is text and the links work. If it is
not grouping, it might be the border you have around it. Try removing the
border or using a simpler, thinner black border. It might also be the 'fill
color' if you are using a fill color in the text boxes. Some gradient fills
and other fills will convert text to an image in FF. In general experiment
with removing grouping, fill colors, borders until you find out what is
converting your text to an image. Once you find that you will functional
links.

If grouping, fill colors, or borders are not the reason for the text being
converted, post back with very specific description of how you are building
those text boxes with the images of the horses. Are you for example
inserting the images of the horses into a text box and formatting in-line?

DavidF

I'm extremely electronically challenged and I need some coaching. My
website

[quoted text clipped - 11 lines]

Thanks so much,
Kristi

 

[DavidF]

Kristi,

There is no problem starting with a Publisher template but unfortunately
MSFT doesn't necessarily design their templates or the design checker for
cross browser compatibility. They have been late coming to that party, but
are making some headway with IE8 and Web Expression, both of which are
supposed to be more standards compliant, and they did improve Publisher 2007
a bit by taking away some of the VML options which create cross browser
issues.

But this does not mean that you can't tweak your Publisher web pages and
make them cross browser compatible. In my experience if you can make your
page work well and look good in both IE and FireFox then they will also work
ok in the other major browsers. Try to discover what it is about your design
that converts the text to an image, and thus kills the links in FireFox, and
when you do that you will probably find your pages very cross browser
compatible. Just test in both IE and FF. And if you can't figure it out,
post back and we will help you.

As to the text/code ratio I am not totally sure what you are talking about,
but Publisher html code has always been a bit bloated. In my view that is
not a big issue if your pages still load fairly quickly, as most viewers
don't give a hoot about how much code there is...they will never look at the
code. The only people that seem to care are web design experts and coders,
and it seems to be more a theoretical and aesthetic argument than a
practical one. But that aside, if you want to minimize the code produced by
Publisher 2003, be sure produce your web files by File > Publish to the web
and produce 'filtered code'. Do not File > Save as a web page as that
produces 'rich' 'roundtripable' code that is much more bloated with Office
tags, and is part of the reason Publisher earned the reputation of producing
bloated code. And as I suggested the most important issue to the viewer is
that the pages load quickly, so be aware that the more images, the slower
the page loads, so use images judiciously and compress them:

Reference: Compress graphics file sizes to create smaller Publisher Web
pages (2003):
http://office.microsoft.com/en-us/publisher/HA011266301033.aspx

Reference: Compress Pictures dialog box (2007):
http://office.microsoft.com/en-us/help/HA100363901033.aspx?pid=CL100605171033

To ungroup permanently or not is the question with Pub 2003. Which is more
efficient is hard to say.

As per your last question, I have no idea what you are asking. Sorry. Please
rephrase.

DavidF

David,

Thank you for your detailed response! Of course the design checker
doesn't
reveal this aspect. My design used a MS Publisher template that I
modified
for design purposes and to make better use of page space...sounds like it
may
have been a mistake. If I make the modifications that you describe, will
the
website display properly on ALL browsers? Do you know if these
modifications
will improve some of the text / code ratio?

Since I only update the website 2-3 times a year and may change navbar
elements, it sounds like I should make my modifications to the original
and
make a copy to use for the ungrouping steps and publish the copy...is that
right?

When published to the web, do you know if there is a difference in the
browser compatibility or html code between an MS Pulisher file saved as a
MS
Publisher file and one that was saved as an html document?

Many Thanks,
Kristi

If you build navbars with the Publisher 2003 and 2007 wizard it will not
render when the page is viewed in IE8. If you ungroup that navbar it will
render, but you also uncouple the navbar from the wizard. This means if
you
add a new page or section you will not be able to automatically add that
to
the existing navbar and propagate it through out the site. That is why we
suggest that if you anticipate adding sections to your site and to the
main
navbar that you ungroup the navbar from a copy of your main Publisher
file.
This advice is mostly applicable to the person who is still building their
site in my opinion. If you don't anticipate adding sections and thus
buttons
to your main navbar, then I would go ahead an ungroup the navbars on each
page and not worry about making a copy each time. If at some point in the
future you wanted to add a section to the main navbar, you could always go
to insert > navbar > existing navbar and just insert a new, wizard
connected
version of your navbar on each page.

I realize this is bit confusing, but the bottom line is that you must
ungroup all design elements on each page of a Pub 2003 in order for those
elements to render in IE8. This includes not only the navbar but also any
other design elements on the page. For example on your Stallions page:
http://www.lacyquarterhorses.com/index_files/horsesforsale_stallions.htm
This page renders just fine in IE7, but in IE8 the navbars do not render
nor
does the banner elements at the top of the page. It appears you have the
banner grouped and you should ungroup those elements and save that change
permanently. Just click on/select the group and then click the grouping
icon
or go to Arrange > Ungroup if you prefer. Also on that page the heading:
'Quarter Horses for Sale: Stallions' also does not render in IE8, so I
would
guess that it too is grouped with some other element.

Now as per FireFox, grouped elements are rendered as a combined image. For
example if you group a text box with an image box, you will get a combined
image of the two, and the text will be converted to an image and kill any
link that might be inserted. So it is important to ungroup all design
elements on each page of your publication for that reason too. You can see
your banner is one big image:
http://www.lacyquarterhorses.com/index_files/image9653.gif
If you ungroup those elements they will appear as individual elements.

Now if you look at the text under each horse picture that describes the
horse and provides links to more pictures and more information, that text
has been converted to an image in FF. If you left click and drag and try
to
copy it you will be unable. This kills the links, and that is what I
assume
you were talking about links not "displaying in Mozilla". Now this may be
caused by linking the text box to another element, but it can also be
caused
by several other formatting issues. It is hard to tell from here and you
will have to test to see what is converting the text into an image. If it
is
grouped, ungroup and see if the text is text and the links work. If it is
not grouping, it might be the border you have around it. Try removing the
border or using a simpler, thinner black border. It might also be the
'fill
color' if you are using a fill color in the text boxes. Some gradient
fills
and other fills will convert text to an image in FF. In general experiment
with removing grouping, fill colors, borders until you find out what is
converting your text to an image. Once you find that you will functional
links.

If grouping, fill colors, or borders are not the reason for the text being
converted, post back with very specific description of how you are
building
those text boxes with the images of the horses. Are you for example
inserting the images of the horses into a text box and formatting in-line?

DavidF

I'm extremely electronically challenged and I need some coaching. My
website

[quoted text clipped - 11 lines]

Thanks so much,
Kristi

 

[Kristi61 via OfficeKB.com]

David,

Again, thanks so much for your detailed response! I still have lots to learn,
and I've been examining my site http://www.lacyquarterhorses.com on Googles
Search Tool page - thus the text/code ratio issue - Google doesn't like too
much code to text content. Since I have no alternative but MS Publisher 2003
I need to find ways to reduce the bloated code to improve Google PR.

The amount of photos are an issue I'm still debating. Most have been
compressed for web pages but the feature photos are compressed for documents
for better resolution - horse people want to see lots of good photos of good
horses and interested buyers want to examine the horse from multiple angles.
I'm still conflicted - faster loading or more photos.

Regarding my last question: My site is published to the web by a third party -
my dial-up won't let me - so I save a copy to CD. My third party no longer
has Publisher on their computer so I have to create a file that they can
upload: File > Publish to the web > Save In: My Documents > copy the
resulting file to CD to enable third party to upload to the web.
The resulting file is described differently: "HTML Document, Document size:
164 KB " instead of the original version "MSO Publisher Document, Document
size: 23.1 MB"
Is that what you were referring to when you said:

"But that aside, if you want to minimize the code produced by Publisher 2003,
be sure produce your web files by File > Publish to the web and produce
'filtered code'. Do not File > Save as a web page as that produces 'rich'
'roundtripable' code that is much more bloated with Office
tags, and is part of the reason Publisher earned the reputation of producing
bloated code."

I don't fully understand what you mean. In my Save as type: the only option
offered is Web Page: Filtered. Could you clarify in Kindergarten terms for
me?

Kristi,

There is no problem starting with a Publisher template but unfortunately
MSFT doesn't necessarily design their templates or the design checker for
cross browser compatibility. They have been late coming to that party, but
are making some headway with IE8 and Web Expression, both of which are
supposed to be more standards compliant, and they did improve Publisher 2007
a bit by taking away some of the VML options which create cross browser
issues.

But this does not mean that you can't tweak your Publisher web pages and
make them cross browser compatible. In my experience if you can make your
page work well and look good in both IE and FireFox then they will also work
ok in the other major browsers. Try to discover what it is about your design
that converts the text to an image, and thus kills the links in FireFox, and
when you do that you will probably find your pages very cross browser
compatible. Just test in both IE and FF. And if you can't figure it out,
post back and we will help you.

As to the text/code ratio I am not totally sure what you are talking about,
but Publisher html code has always been a bit bloated. In my view that is
not a big issue if your pages still load fairly quickly, as most viewers
don't give a hoot about how much code there is...they will never look at the
code. The only people that seem to care are web design experts and coders,
and it seems to be more a theoretical and aesthetic argument than a
practical one. But that aside, if you want to minimize the code produced by
Publisher 2003, be sure produce your web files by File > Publish to the web
and produce 'filtered code'. Do not File > Save as a web page as that
produces 'rich' 'roundtripable' code that is much more bloated with Office
tags, and is part of the reason Publisher earned the reputation of producing
bloated code. And as I suggested the most important issue to the viewer is
that the pages load quickly, so be aware that the more images, the slower
the page loads, so use images judiciously and compress them:

Reference: Compress graphics file sizes to create smaller Publisher Web
pages (2003):
http://office.microsoft.com/en-us/publisher/HA011266301033.aspx

Reference: Compress Pictures dialog box (2007):
http://office.microsoft.com/en-us/help/HA100363901033.aspx?pid=CL100605171033

To ungroup permanently or not is the question with Pub 2003. Which is more
efficient is hard to say.

As per your last question, I have no idea what you are asking. Sorry. Please
rephrase.

DavidF

David,

[quoted text clipped - 106 lines]

 

[DavidF]

Kristi,

Google the subject of text/code ratio and you will find a lot of
information. Here is just one article that rings true to me:
http://www.affilorama.com/blog/text-to-code-ratio And as you will notice a
quote from a Google rep...it does not make any difference. Bottom line is
Publisher code is what it is, and as long as you are producing filtered
code, that is as lean as you can get it. If you want leaner code, then
switch to a different program...

You won't get better pictures by going with "print" compression rather than
"web" when you view them on line. You will just get a slower loading picture
in IE. Compress all images for the web.

Of course you need lots of pictures for a site such as yours, and you are
approaching it correctly. One picture of each horse on the page with links
to more pictures. I was only saying that it is your pictures that slow the
loading of your pages...not the text. So keep that in mind.

I really see no reason why you cannot upload your own files to your host. I
have a dial-up connection I use occasionally and yes it takes a few more
minutes but it is not really a problem. When you Publish to the Web and
produce your web files, you are producing filtered code and doing it
appropriately. As long as you are not doing a Save as a Web page, you are
fine. You should be getting both an index.htm file and an index_files folder
that contains your other pages and all your graphics. The web files are what
you upload...not your .pub file. And I would expect that even your
index_files folder is not that large. Right click it and look at properties
to get the size. Once again I see absolutely no reason why you shouldn't be
able to upload your own files. Have the third party show you how to upload
from your own computer...or follow some of the links we have provided about
ftp uploading etc.

By the way, though I don't want to overload you with too much feedback, I
would suggest that you consider using a larger font for your text. Unless
you have young eyes, a font size of 8 is just too small...which is what I
think you are using on your home page. I prefer 12 personally, but then my
eyes are much olderererer. <g> You can get away with using smaller fonts on
menus and such, but if there is a lot of text I would suggest that you use
at least 10 pt and consider 12.

DavidF

David,

Again, thanks so much for your detailed response! I still have lots to
learn,
and I've been examining my site http://www.lacyquarterhorses.com on
Googles
Search Tool page - thus the text/code ratio issue - Google doesn't like
too
much code to text content. Since I have no alternative but MS Publisher
2003
I need to find ways to reduce the bloated code to improve Google PR.

The amount of photos are an issue I'm still debating. Most have been
compressed for web pages but the feature photos are compressed for
documents
for better resolution - horse people want to see lots of good photos of
good
horses and interested buyers want to examine the horse from multiple
angles.
I'm still conflicted - faster loading or more photos.

Regarding my last question: My site is published to the web by a third
party -
my dial-up won't let me - so I save a copy to CD. My third party no longer
has Publisher on their computer so I have to create a file that they can
upload: File > Publish to the web > Save In: My Documents > copy the
resulting file to CD to enable third party to upload to the web.
The resulting file is described differently: "HTML Document, Document
size:
164 KB " instead of the original version "MSO Publisher Document, Document
size: 23.1 MB"
Is that what you were referring to when you said:

"But that aside, if you want to minimize the code produced by Publisher
2003,
be sure produce your web files by File > Publish to the web and produce
'filtered code'. Do not File > Save as a web page as that produces 'rich'
'roundtripable' code that is much more bloated with Office
tags, and is part of the reason Publisher earned the reputation of
producing
bloated code."

I don't fully understand what you mean. In my Save as type: the only
option
offered is Web Page: Filtered. Could you clarify in Kindergarten terms
for
me?

Kristi,

There is no problem starting with a Publisher template but unfortunately
MSFT doesn't necessarily design their templates or the design checker for
cross browser compatibility. They have been late coming to that party, but
are making some headway with IE8 and Web Expression, both of which are
supposed to be more standards compliant, and they did improve Publisher
2007
a bit by taking away some of the VML options which create cross browser
issues.

But this does not mean that you can't tweak your Publisher web pages and
make them cross browser compatible. In my experience if you can make your
page work well and look good in both IE and FireFox then they will also
work
ok in the other major browsers. Try to discover what it is about your
design
that converts the text to an image, and thus kills the links in FireFox,
and
when you do that you will probably find your pages very cross browser
compatible. Just test in both IE and FF. And if you can't figure it out,
post back and we will help you.

As to the text/code ratio I am not totally sure what you are talking
about,
but Publisher html code has always been a bit bloated. In my view that is
not a big issue if your pages still load fairly quickly, as most viewers
don't give a hoot about how much code there is...they will never look at
the
code. The only people that seem to care are web design experts and coders,
and it seems to be more a theoretical and aesthetic argument than a
practical one. But that aside, if you want to minimize the code produced
by
Publisher 2003, be sure produce your web files by File > Publish to the
web
and produce 'filtered code'. Do not File > Save as a web page as that
produces 'rich' 'roundtripable' code that is much more bloated with Office
tags, and is part of the reason Publisher earned the reputation of
producing
bloated code. And as I suggested the most important issue to the viewer is
that the pages load quickly, so be aware that the more images, the slower
the page loads, so use images judiciously and compress them:

Reference: Compress graphics file sizes to create smaller Publisher Web
pages (2003):
http://office.microsoft.com/en-us/publisher/HA011266301033.aspx

Reference: Compress Pictures dialog box (2007):
http://office.microsoft.com/en-us/help/HA100363901033.aspx?pid=CL100605171033

To ungroup permanently or not is the question with Pub 2003. Which is more
efficient is hard to say.

As per your last question, I have no idea what you are asking. Sorry.
Please
rephrase.

DavidF

David,

[quoted text clipped - 106 lines]

Thanks so much,
Kristi

 

[Kristi61 via OfficeKB.com]

David,

OMG! I'm more confused than ever now about what steps, which files and how
to publish to the web with MS Publisher. I'm on Netzero "Hi-Speed" (faux Hi-
Speed using cached files) dial-up and use Go Daddy to host and when I tried
it before, after 15-20 minutes, it would give me a "servor error" and
sometimes load just enough to mess up my site. Of course Netzero sent
several pages of indecipherable instructions about changing settings to try
to correct the problem. I'm just not smart enough to figure it out and I
know it should be easy! I'm so discouraged about my inability to accomplish
a task that you describe as being no problem. My third party is 1,500 miles
away so that is not an option. I'm doing the best I can with limited self-
taught computer skills and any free coaching I can get from generous people
like you. Unfortunately, I'm not well versed in computer language and too
much of the coaching terminology is beyond my understanding. Can you give it
to me step-by-step in laymans terms? Can I do a run through without going
online?

Where do I find the "links provided for ftp uploading"?

When I compress my photos as documents it shows a reduction in the file size.
Is that a misrepresentation?

Thank you,
Kristi

Kristi,

Google the subject of text/code ratio and you will find a lot of
information. Here is just one article that rings true to me:
http://www.affilorama.com/blog/text-to-code-ratio And as you will notice a
quote from a Google rep...it does not make any difference. Bottom line is
Publisher code is what it is, and as long as you are producing filtered
code, that is as lean as you can get it. If you want leaner code, then
switch to a different program...

You won't get better pictures by going with "print" compression rather than
"web" when you view them on line. You will just get a slower loading picture
in IE. Compress all images for the web.

Of course you need lots of pictures for a site such as yours, and you are
approaching it correctly. One picture of each horse on the page with links
to more pictures. I was only saying that it is your pictures that slow the
loading of your pages...not the text. So keep that in mind.

I really see no reason why you cannot upload your own files to your host. I
have a dial-up connection I use occasionally and yes it takes a few more
minutes but it is not really a problem. When you Publish to the Web and
produce your web files, you are producing filtered code and doing it
appropriately. As long as you are not doing a Save as a Web page, you are
fine. You should be getting both an index.htm file and an index_files folder
that contains your other pages and all your graphics. The web files are what
you upload...not your .pub file. And I would expect that even your
index_files folder is not that large. Right click it and look at properties
to get the size. Once again I see absolutely no reason why you shouldn't be
able to upload your own files. Have the third party show you how to upload
from your own computer...or follow some of the links we have provided about
ftp uploading etc.

By the way, though I don't want to overload you with too much feedback, I
would suggest that you consider using a larger font for your text. Unless
you have young eyes, a font size of 8 is just too small...which is what I
think you are using on your home page. I prefer 12 personally, but then my
eyes are much olderererer. <g> You can get away with using smaller fonts on
menus and such, but if there is a lot of text I would suggest that you use
at least 10 pt and consider 12.

DavidF

David,

[quoted text clipped - 108 lines]

 

[DavidF]

Kristi,

Sorry to confuse you. Uploading a website can be a bit confusing at first,
but once you figure it out you should be able to handle it yourself. My
point was that the fact that you use dial-up should not make any difference
other than the uploading might take a bit longer.

You can learn the basics here:
Prepare, publish, and maintain your Publisher Web site:
http://office.microsoft.com/en-us/publisher/HA100947601033.aspx

And GoDaddy has very good support articles. Here are a couple:

Reference: GoDaddy: Using Windows XP to Upload Your Site:
http://help.godaddy.com/article/106

Reference: GoDaddy: Using Windows Vista to Upload Your Site:
http://help.godaddy.com/article/4191

I am sure that GoDaddy also provided you links to how to ftp your web files
to your host.

However, I would suggest that since it does not appear that you are using a
form on your page that you consider downloading and installing the free FTP
client FileZilla:
http://filezilla-project.org/ It is likely to be easier for you in the long
run. Also peruse this page...in other words, read the instructions:
http://filezilla.sourceforge.net/documentation/

Reference: Aplus.net: How do I upload with Filezilla:
http://www.apluskb.com/scripts/How_do_I_upload_with_answer3668.html
This article has some good screenshots that may help you understand how to
use FileZilla.

Now, as to netzero I can't help you much. Are you using the paid service or
the free service? Assuming that you are paying, I would suggest that you
contact the support department and ask them for instructions on how to ftp
your web files to your godaddy host account. Perhaps tell them you want to
use FileZilla and ask them if that is ok. Or ask the Godaddy support people
how to use netzero to upload to your host? Both support departments should
be able to give you the additional information you need to get your site
files uploaded.

If you compress your photos, then yes the file size should be less. That is
the whole reason for compressing your files. Did you read the articles about
compressing your photos? Perhaps read them again?

Look, raising horses is beyond most people's abilities but you learned how
to do that. You can learn the steps you need to take to upload your web
files to your web host. Just read and reread the instructions until they
sink in. Once you get it, it will be easy to ftp your site files to your
host. You designed a pretty complicated website...you can learn the other
too.

DavidF

David,

OMG! I'm more confused than ever now about what steps, which files and
how
to publish to the web with MS Publisher. I'm on Netzero "Hi-Speed" (faux
Hi-
Speed using cached files) dial-up and use Go Daddy to host and when I
tried
it before, after 15-20 minutes, it would give me a "servor error" and
sometimes load just enough to mess up my site. Of course Netzero sent
several pages of indecipherable instructions about changing settings to
try
to correct the problem. I'm just not smart enough to figure it out and I
know it should be easy! I'm so discouraged about my inability to
accomplish
a task that you describe as being no problem. My third party is 1,500
miles
away so that is not an option. I'm doing the best I can with limited
self-
taught computer skills and any free coaching I can get from generous
people
like you. Unfortunately, I'm not well versed in computer language and too
much of the coaching terminology is beyond my understanding. Can you give
it
to me step-by-step in laymans terms? Can I do a run through without going
online?

Where do I find the "links provided for ftp uploading"?

When I compress my photos as documents it shows a reduction in the file
size.
Is that a misrepresentation?

Thank you,
Kristi

Kristi,

Google the subject of text/code ratio and you will find a lot of
information. Here is just one article that rings true to me:
http://www.affilorama.com/blog/text-to-code-ratio And as you will notice
a
quote from a Google rep...it does not make any difference. Bottom line is
Publisher code is what it is, and as long as you are producing filtered
code, that is as lean as you can get it. If you want leaner code, then
switch to a different program...

You won't get better pictures by going with "print" compression rather
than
"web" when you view them on line. You will just get a slower loading
picture
in IE. Compress all images for the web.

Of course you need lots of pictures for a site such as yours, and you are
approaching it correctly. One picture of each horse on the page with links
to more pictures. I was only saying that it is your pictures that slow the
loading of your pages...not the text. So keep that in mind.

I really see no reason why you cannot upload your own files to your host.
I
have a dial-up connection I use occasionally and yes it takes a few more
minutes but it is not really a problem. When you Publish to the Web and
produce your web files, you are producing filtered code and doing it
appropriately. As long as you are not doing a Save as a Web page, you are
fine. You should be getting both an index.htm file and an index_files
folder
that contains your other pages and all your graphics. The web files are
what
you upload...not your .pub file. And I would expect that even your
index_files folder is not that large. Right click it and look at
properties
to get the size. Once again I see absolutely no reason why you shouldn't
be
able to upload your own files. Have the third party show you how to upload
from your own computer...or follow some of the links we have provided
about
ftp uploading etc.

By the way, though I don't want to overload you with too much feedback, I
would suggest that you consider using a larger font for your text. Unless
you have young eyes, a font size of 8 is just too small...which is what I
think you are using on your home page. I prefer 12 personally, but then my
eyes are much olderererer. <g> You can get away with using smaller fonts
on
menus and such, but if there is a lot of text I would suggest that you use
at least 10 pt and consider 12.

DavidF

David,

[quoted text clipped - 108 lines]

Thanks so much,
Kristi

 

[Kristi61 via OfficeKB.com]

David,

I'm working up my courage to give uploading another try - Thanks.
What file size is appropriate for photos? Web page Compression loses so much
resolution which is why I use the "Compress for Documents" only on my feature
photos and "Compress for web pages" on all of the other photos. My version
is MSOP 2003 so I can't further reduce leftover code for cropping ect. as in
MSOP 2007.

If TV can do HD then why can't the Internet?


Thanks,
Krisit

Kristi,

Sorry to confuse you. Uploading a website can be a bit confusing at first,
but once you figure it out you should be able to handle it yourself. My
point was that the fact that you use dial-up should not make any difference
other than the uploading might take a bit longer.

You can learn the basics here:
Prepare, publish, and maintain your Publisher Web site:
http://office.microsoft.com/en-us/publisher/HA100947601033.aspx

And GoDaddy has very good support articles. Here are a couple:

Reference: GoDaddy: Using Windows XP to Upload Your Site:
http://help.godaddy.com/article/106

Reference: GoDaddy: Using Windows Vista to Upload Your Site:
http://help.godaddy.com/article/4191

I am sure that GoDaddy also provided you links to how to ftp your web files
to your host.

However, I would suggest that since it does not appear that you are using a
form on your page that you consider downloading and installing the free FTP
client FileZilla:
http://filezilla-project.org/ It is likely to be easier for you in the long
run. Also peruse this page...in other words, read the instructions:
http://filezilla.sourceforge.net/documentation/

Reference: Aplus.net: How do I upload with Filezilla:
http://www.apluskb.com/scripts/How_do_I_upload_with_answer3668.html
This article has some good screenshots that may help you understand how to
use FileZilla.

Now, as to netzero I can't help you much. Are you using the paid service or
the free service? Assuming that you are paying, I would suggest that you
contact the support department and ask them for instructions on how to ftp
your web files to your godaddy host account. Perhaps tell them you want to
use FileZilla and ask them if that is ok. Or ask the Godaddy support people
how to use netzero to upload to your host? Both support departments should
be able to give you the additional information you need to get your site
files uploaded.

If you compress your photos, then yes the file size should be less. That is
the whole reason for compressing your files. Did you read the articles about
compressing your photos? Perhaps read them again?

Look, raising horses is beyond most people's abilities but you learned how
to do that. You can learn the steps you need to take to upload your web
files to your web host. Just read and reread the instructions until they
sink in. Once you get it, it will be easy to ftp your site files to your
host. You designed a pretty complicated website...you can learn the other
too.

DavidF

David,

[quoted text clipped - 90 lines]

 

[DavidF]

Kristi,

You don't have to actually upload new files to learn how to use ftp. If you
download and install FileZilla, read the instructions, and set up a ftp
connection to your site, then you should be able to see all the files and
folder on your host server including the index.htm file and the index_files
folder. Then once you successfully make the ftp connection, and you are
ready, updating your site is much the same as dragging your web files to the
CD drive on your local computer...you just drag them, or copy and paste them
to the web host. Focus on getting FileZilla set up and understand the
directions and it should be less intimidating.

Publisher outputs its web files at 96 ppi. Compressing your graphics for
print will *not* make for a better image online...just a slower loading
picture in IE. Furthermore it will result many times with an inferior copy
of that image that is rendered for FireFox and other browsers.

DavidF

David,

I'm working up my courage to give uploading another try - Thanks.
What file size is appropriate for photos? Web page Compression loses so
much
resolution which is why I use the "Compress for Documents" only on my
feature
photos and "Compress for web pages" on all of the other photos. My
version
is MSOP 2003 so I can't further reduce leftover code for cropping ect. as
in
MSOP 2007.

If TV can do HD then why can't the Internet?


Thanks,
Krisit

Kristi,

Sorry to confuse you. Uploading a website can be a bit confusing at first,
but once you figure it out you should be able to handle it yourself. My
point was that the fact that you use dial-up should not make any
difference
other than the uploading might take a bit longer.

You can learn the basics here:
Prepare, publish, and maintain your Publisher Web site:
http://office.microsoft.com/en-us/publisher/HA100947601033.aspx

And GoDaddy has very good support articles. Here are a couple:

Reference: GoDaddy: Using Windows XP to Upload Your Site:
http://help.godaddy.com/article/106

Reference: GoDaddy: Using Windows Vista to Upload Your Site:
http://help.godaddy.com/article/4191

I am sure that GoDaddy also provided you links to how to ftp your web
files
to your host.

However, I would suggest that since it does not appear that you are using
a
form on your page that you consider downloading and installing the free
FTP
client FileZilla:
http://filezilla-project.org/ It is likely to be easier for you in the
long
run. Also peruse this page...in other words, read the instructions:
http://filezilla.sourceforge.net/documentation/

Reference: Aplus.net: How do I upload with Filezilla:
http://www.apluskb.com/scripts/How_do_I_upload_with_answer3668.html
This article has some good screenshots that may help you understand how to
use FileZilla.

Now, as to netzero I can't help you much. Are you using the paid service
or
the free service? Assuming that you are paying, I would suggest that you
contact the support department and ask them for instructions on how to ftp
your web files to your godaddy host account. Perhaps tell them you want to
use FileZilla and ask them if that is ok. Or ask the Godaddy support
people
how to use netzero to upload to your host? Both support departments should
be able to give you the additional information you need to get your site
files uploaded.

If you compress your photos, then yes the file size should be less. That
is
the whole reason for compressing your files. Did you read the articles
about
compressing your photos? Perhaps read them again?

Look, raising horses is beyond most people's abilities but you learned how
to do that. You can learn the steps you need to take to upload your web
files to your web host. Just read and reread the instructions until they
sink in. Once you get it, it will be easy to ftp your site files to your
host. You designed a pretty complicated website...you can learn the other
too.

DavidF

David,

[quoted text clipped - 90 lines]

Thanks so much,
Kristi

 

[Kristi61 via OfficeKB.com]

David,

OK,OK... I'll compress all photos for web pages!

I'm nearly done with all the corrections and am reviewing the material posted
here to prepare for an upload attempt...

I'm still not fully understanding you when you say don't Save as a Web Page.
When I File>Publish to the web>Save in (either the original or the copy)>
Save as> the only option is Web Page Filtered. Are there supposed to be any
other options?

The current file uploaded to the web was created by: File > Publish to the
web > Save In: My Documents > copy the resulting file to CD to enable third
party to upload to the web.
The resulting file is described differently: "HTML Document, Document size:
164 KB " instead of the original version "MSO Publisher Document, Document
size: 23.1 MB"

Again: The resulting file is described differently: "HTML Document, Document
size:
164 KB " instead of the original version "MSO Publisher Document, Document
size: 23.1 MB" Why? Which file should I use?

Thanks,

Kristi,

You don't have to actually upload new files to learn how to use ftp. If you
download and install FileZilla, read the instructions, and set up a ftp
connection to your site, then you should be able to see all the files and
folder on your host server including the index.htm file and the index_files
folder. Then once you successfully make the ftp connection, and you are
ready, updating your site is much the same as dragging your web files to the
CD drive on your local computer...you just drag them, or copy and paste them
to the web host. Focus on getting FileZilla set up and understand the
directions and it should be less intimidating.

Publisher outputs its web files at 96 ppi. Compressing your graphics for
print will *not* make for a better image online...just a slower loading
picture in IE. Furthermore it will result many times with an inferior copy
of that image that is rendered for FireFox and other browsers.

DavidF

David,

[quoted text clipped - 84 lines]

 

[Kristi61 via OfficeKB.com]

David,

Another thing: Since MSOP 2003 must now be published with a "Ungrouped"
design for browser compatibility; wouldn't it be more expedient to simply
make a copy and Select All > Ungroup each page of the copy > publish the copy,
rather than first searching for and ungrouping all of the grouped elements on
the original then making a copy and then Select All > Ungroup each page of
the copy > publish the copy? It would save a very tedious step since the
original cannot be used for anything but design purposes anyway unless you
don't ever intend to change nav bars. Just looking for a quicker solution.

Thanks Again,

David,

OK,OK... I'll compress all photos for web pages!

I'm nearly done with all the corrections and am reviewing the material posted
here to prepare for an upload attempt...

I'm still not fully understanding you when you say don't Save as a Web Page.
When I File>Publish to the web>Save in (either the original or the copy)>
Save as> the only option is Web Page Filtered. Are there supposed to be any
other options?

The current file uploaded to the web was created by: File > Publish to the
web > Save In: My Documents > copy the resulting file to CD to enable third
party to upload to the web.
The resulting file is described differently: "HTML Document, Document size:
164 KB " instead of the original version "MSO Publisher Document, Document
size: 23.1 MB"

Again: The resulting file is described differently: "HTML Document, Document
size:
164 KB " instead of the original version "MSO Publisher Document, Document
size: 23.1 MB" Why? Which file should I use?

Thanks,
Kristi

Kristi,

[quoted text clipped - 20 lines]

 

[DavidF]

Hi again,

I am sorry I confused you about the filtered and rich htm code. You are
doing it correctly when you File > Publish to the Web....this will produce
filtered code. It will produce an 'index.htm' file and an 'index_files'
folder which contains your other *.htm files and image files. You upload the
index.htm file and the index_files folder...the web files, not the *.pub
file. When you log on to your server you should be able to see copies of
those, and those are what will be replaced or overwritten when you upload
the new ones.

If you don't already have your computer set up to show file extensions, do
so and this might make things easier for you to see the difference. Go to
Control Panel > Folder Options > View tab and uncheck the option 'Hide
extensions for known file types". Now when you view your web files in
Windows Explorer or My Computer you will see the .htm extensions and the
image extensions such as .jpg, .png and .gif and your original Pub
file...the 23.1 MB file will have a .pub extension.

DavidF

David,

OK,OK... I'll compress all photos for web pages!

I'm nearly done with all the corrections and am reviewing the material
posted
here to prepare for an upload attempt...

I'm still not fully understanding you when you say don't Save as a Web
Page.
When I File>Publish to the web>Save in (either the original or the copy)>
Save as> the only option is Web Page Filtered. Are there supposed to be
any
other options?

The current file uploaded to the web was created by: File > Publish to
the
web > Save In: My Documents > copy the resulting file to CD to enable
third
party to upload to the web.
The resulting file is described differently: "HTML Document, Document
size:
164 KB " instead of the original version "MSO Publisher Document, Document
size: 23.1 MB"

Again: The resulting file is described differently: "HTML Document,
Document
size:
164 KB " instead of the original version "MSO Publisher Document, Document
size: 23.1 MB" Why? Which file should I use?

Thanks,

Kristi,

You don't have to actually upload new files to learn how to use ftp. If
you
download and install FileZilla, read the instructions, and set up a ftp
connection to your site, then you should be able to see all the files and
folder on your host server including the index.htm file and the
index_files
folder. Then once you successfully make the ftp connection, and you are
ready, updating your site is much the same as dragging your web files to
the
CD drive on your local computer...you just drag them, or copy and paste
them
to the web host. Focus on getting FileZilla set up and understand the
directions and it should be less intimidating.

Publisher outputs its web files at 96 ppi. Compressing your graphics for
print will *not* make for a better image online...just a slower loading
picture in IE. Furthermore it will result many times with an inferior copy
of that image that is rendered for FireFox and other browsers.

DavidF

David,

[quoted text clipped - 84 lines]

Thanks so much,
Kristi

 

[DavidF]

Yeah...I have been trying to tweak that boilerplate answer about the
grouping issue, and you are correct...it is confusing as I have written it.
I was trying to say that the ungrouping of other elements besides the
navbars could be saved permanently, but it does not make any difference.
Just go to each page on the copy and ungroup everything on the page in one
step as you suggested. Thanks...I will change my boilerplate.

DavidF

David,

Another thing: Since MSOP 2003 must now be published with a "Ungrouped"
design for browser compatibility; wouldn't it be more expedient to simply
make a copy and Select All > Ungroup each page of the copy > publish the
copy,
rather than first searching for and ungrouping all of the grouped elements
on
the original then making a copy and then Select All > Ungroup each page of
the copy > publish the copy? It would save a very tedious step since the
original cannot be used for anything but design purposes anyway unless you
don't ever intend to change nav bars. Just looking for a quicker
solution.

Thanks Again,

David,

OK,OK... I'll compress all photos for web pages!

I'm nearly done with all the corrections and am reviewing the material
posted
here to prepare for an upload attempt...

I'm still not fully understanding you when you say don't Save as a Web
Page.
When I File>Publish to the web>Save in (either the original or the copy)>
Save as> the only option is Web Page Filtered. Are there supposed to be
any
other options?

The current file uploaded to the web was created by: File > Publish to
the
web > Save In: My Documents > copy the resulting file to CD to enable
third
party to upload to the web.
The resulting file is described differently: "HTML Document, Document
size:
164 KB " instead of the original version "MSO Publisher Document, Document
size: 23.1 MB"

Again: The resulting file is described differently: "HTML Document,
Document
size:
164 KB " instead of the original version "MSO Publisher Document, Document
size: 23.1 MB" Why? Which file should I use?

Thanks,
Kristi

Kristi,

[quoted text clipped - 20 lines]

Thanks so much,
Kristi

 

[Kristi61 via OfficeKB.com]

David,

Well...It's 3AM and I've spent the last FOUR HOURS uploading
www.lacyquarterhorses.com using Filezilla and I don't think it worked. I
probably did something wrong. I browsed to my folder and clicked it thinking
I would have to select the 'index.htm file and the 'index_files' seperately
but it started working immediately. There were 13 files that failed to
transfer after requeing and reprocessing them twice. They would repeatedly
get "connection interrupted" and and kicked back into the "Failed Transfers"
bin. Once they had all returned to Failed Transfers it stuck on connection
interrupted so I exited. I looked at the site and can't see any changes...

I got a warning window saying something to the effect that some kind of
memory was going to do something > OK. I clicked OK and the Filezilla
process continued but my computer got glitchy later when I closed my internet
connection.

By the way, at the very end of the Filezilla upload instruction it says,

"Remember that in order for files to be seen on your site, they must be
placed into the proper hosting folder on the remote site. For Unix-based
plans, this folder is named "html" and for Windows-based plans this is called
"WWWROOT". In either case, remember to rename your home page "Index.html"
and leave it in the html or wwwroot folder.

What does that mean? Am I just stupid or what? I looked at the 'index_files'
folder and can't find my home page there.

Very discouraged,
Kristi

Yeah...I have been trying to tweak that boilerplate answer about the
grouping issue, and you are correct...it is confusing as I have written it.
I was trying to say that the ungrouping of other elements besides the
navbars could be saved permanently, but it does not make any difference.
Just go to each page on the copy and ungroup everything on the page in one
step as you suggested. Thanks...I will change my boilerplate.

DavidF

David,

[quoted text clipped - 49 lines]

 

[DavidF]

Kristi,

As per the last part. It is talking about putting your webfiles into the
root folder on the host server. If you logged onto your host server with
FileZilla you should be able to see where your index.htm file and your
index_files folder is located in the directory on your host. That is where
you upload the new files. That is your root directory. The links about
uploading with XP and Vista also talked about where the root folder is on
GoDaddy.

Go back and read the instructions again and I have added some other links
this time. Perhaps one set of instructions will make more sense to you than
another.

Look at that link to Aplus.net: How do I upload with Filezilla:
http://www.apluskb.com/scripts/How_do_I_upload_with_answer3668.html
It is not exactly the same for GoDaddy, but it should help.

Here are instructions from GoDaddy. Using FileZilla to Upload Your Site:
http://help.godaddy.com/topic/430/article/104

And some more: Connect To Your Web Server Through FTP With FileZilla:
http://jarretcade.net/connect-to-your-web-server-through-ftp-with-filezilla

How to set up ftp filezilla for GoDaddy hosting account:
http://www.ehow.com/how_4887995_ftp-filezilla-godaddy-hosting-account.html

And of course you can read the FileZilla instructions again. Hopefully one
of these sets of instructions will help you figure it out.

How big is your index_files folder? Are you sure you were not trying to
upload the .pub file?

One thing you can do as a safety precaution as you learn to upload is to add
the extension '.old' to the index.htm file and your index_files folder on
the server before you try to upload your new files. In other words log on
using the filezilla and rename index.htm file on the web server to
'index.htm.old' and index_files to 'index_files.old'. Now your old files
will not be overwritten when you upload your new files. And just in case if
you have problems uploading the new ones, you can always remove the .old
from the original files and folder and your site will work again.

Try uploading just the index.htm file first. Then try uploading the
index_files folder. It being bigger will take longer, but perhaps if you can
find success with the index.htm file, then at least you will know the
process works.

Good luck. Seriously, after you get this figured out and do it a few times
it is no more difficult than copying files to a CD...you are just copying
files to another computer. Good luck.

DavidF

David,

Well...It's 3AM and I've spent the last FOUR HOURS uploading
www.lacyquarterhorses.com using Filezilla and I don't think it worked. I
probably did something wrong. I browsed to my folder and clicked it
thinking
I would have to select the 'index.htm file and the 'index_files'
seperately
but it started working immediately. There were 13 files that failed to
transfer after requeing and reprocessing them twice. They would
repeatedly
get "connection interrupted" and and kicked back into the "Failed
Transfers"
bin. Once they had all returned to Failed Transfers it stuck on
connection
interrupted so I exited. I looked at the site and can't see any
changes...

I got a warning window saying something to the effect that some kind of
memory was going to do something > OK. I clicked OK and the Filezilla
process continued but my computer got glitchy later when I closed my
internet
connection.

By the way, at the very end of the Filezilla upload instruction it says,

"Remember that in order for files to be seen on your site, they must be
placed into the proper hosting folder on the remote site. For Unix-based
plans, this folder is named "html" and for Windows-based plans this is
called
"WWWROOT". In either case, remember to rename your home page "Index.html"
and leave it in the html or wwwroot folder.

What does that mean? Am I just stupid or what? I looked at the
'index_files'
folder and can't find my home page there.

Very discouraged,
Kristi

Yeah...I have been trying to tweak that boilerplate answer about the
grouping issue, and you are correct...it is confusing as I have written
it.
I was trying to say that the ungrouping of other elements besides the
navbars could be saved permanently, but it does not make any difference.
Just go to each page on the copy and ungroup everything on the page in one
step as you suggested. Thanks...I will change my boilerplate.

DavidF

David,

[quoted text clipped - 49 lines]

Thanks so much,
Kristi

 

[Kristi61 via OfficeKB.com]

David,

Well Geez!...I guess I'm just retarded. I thought I WAS following the
directions! You all make it sound so easy and I feel soooo STUPID!!!!!!!! I
don't know exactly how drag and drop works (drag from where & drop to where?
They didn't say int the instructions!) but I do know how to right-click a
folder and choose "upload". When I did that a bunch of files started
scrolling in the top pane and it lasted for FOUR HOURS and wasn't successful.
Should I have stopped it before it completed. No I did not try to upload a .
pub file!

The file folder, www.lacyquarterhorses.com, is present in the remote site
pane of Filzilla along with a bunch of other unfamiliar folders and files
with old dates, but the website doesn't show any changes here on my computer.
What should I do with it?

I'm not enough of a glutton for punishment to want to do this again unless I
know what I did wrong (assuming the problem was caused by something I did
wrong) and how to correct it so that it can be completed in a reasonable
amount of time!

Yes, I read the articles which, in some cases, describe different methods ...
suprise suprise. At any rate they didn't give me any answers.

I think it is just as likely that my Netzero dial-up so slow.

Sorry I'm such a poor student,

Kristi,

As per the last part. It is talking about putting your webfiles into the
root folder on the host server. If you logged onto your host server with
FileZilla you should be able to see where your index.htm file and your
index_files folder is located in the directory on your host. That is where
you upload the new files. That is your root directory. The links about
uploading with XP and Vista also talked about where the root folder is on
GoDaddy.

Go back and read the instructions again and I have added some other links
this time. Perhaps one set of instructions will make more sense to you than
another.

Look at that link to Aplus.net: How do I upload with Filezilla:
http://www.apluskb.com/scripts/How_do_I_upload_with_answer3668.html
It is not exactly the same for GoDaddy, but it should help.

Here are instructions from GoDaddy. Using FileZilla to Upload Your Site:
http://help.godaddy.com/topic/430/article/104

And some more: Connect To Your Web Server Through FTP With FileZilla:
http://jarretcade.net/connect-to-your-web-server-through-ftp-with-filezilla

How to set up ftp filezilla for GoDaddy hosting account:
http://www.ehow.com/how_4887995_ftp-filezilla-godaddy-hosting-account.html

And of course you can read the FileZilla instructions again. Hopefully one
of these sets of instructions will help you figure it out.

How big is your index_files folder? Are you sure you were not trying to
upload the .pub file?

One thing you can do as a safety precaution as you learn to upload is to add
the extension '.old' to the index.htm file and your index_files folder on
the server before you try to upload your new files. In other words log on
using the filezilla and rename index.htm file on the web server to
'index.htm.old' and index_files to 'index_files.old'. Now your old files
will not be overwritten when you upload your new files. And just in case if
you have problems uploading the new ones, you can always remove the .old
from the original files and folder and your site will work again.

Try uploading just the index.htm file first. Then try uploading the
index_files folder. It being bigger will take longer, but perhaps if you can
find success with the index.htm file, then at least you will know the
process works.

Good luck. Seriously, after you get this figured out and do it a few times
it is no more difficult than copying files to a CD...you are just copying
files to another computer. Good luck.

DavidF

David,

[quoted text clipped - 51 lines]

 

[Kristi61 via OfficeKB.com]

David,

I just got off the phone with Go Daddy (my host) and was told the the folder
"www.lacyquarterhorses.com_files" was uploaded but the "index.htm" file was
not present and that was why the website cannot change. I reopened Filezilla
and selected the CD drive where I have them on disc and it only displays the
"www.lacyquarterhorses.com_files" and does not display the "
www.lacyquarterhorses.com." HTML document, thus, Filezilla only loaded "
www.lacyquarterhorses.com_files". When I view the contents of the CD I have
both the www.lacyquarterhorses.com_files and the www.lacyquarterhorses.com
HTML Document present on the CD. Why doesn't Filezilla show them both?

Do I need to rename the www.lacyquarterhorses.com HTML Document as "index.
html"? Will it then display in Filezilla? Can I select it exclusively and
upload it?

By the way...Go Daddy says that 4 hours is not at all uncommon for uploading
a website the size of mine (could it be all that excessive code?) on a dial-
up connection and that the Failed transfers due to "connection interrupted"
are quite common on a lengthy dial-up connection and difficult to
successfully reprocess once they have been interrupted. I certainly don't
have the patience to devote that much time to an activity that will likely
produce a defective outcome.

I think, in the future, I would be better off to rely on my third party or
possibly try the library for a faster, more reliable connection to upload
from.

It's been a learning experience anyway.

Thanks,
Kristi

David,

Well Geez!...I guess I'm just retarded. I thought I WAS following the
directions! You all make it sound so easy and I feel soooo STUPID!!!!!!!! I
don't know exactly how drag and drop works (drag from where & drop to where?
They didn't say int the instructions!) but I do know how to right-click a
folder and choose "upload". When I did that a bunch of files started
scrolling in the top pane and it lasted for FOUR HOURS and wasn't successful.
Should I have stopped it before it completed. No I did not try to upload a .
pub file!

The file folder, www.lacyquarterhorses.com, is present in the remote site
pane of Filzilla along with a bunch of other unfamiliar folders and files
with old dates, but the website doesn't show any changes here on my computer.
What should I do with it?

I'm not enough of a glutton for punishment to want to do this again unless I
know what I did wrong (assuming the problem was caused by something I did
wrong) and how to correct it so that it can be completed in a reasonable
amount of time!

Yes, I read the articles which, in some cases, describe different methods ...
suprise suprise. At any rate they didn't give me any answers.

I think it is just as likely that my Netzero dial-up so slow.

Sorry I'm such a poor student,
Kristi

Kristi,

[quoted text clipped - 54 lines]

 

[DavidF]

You have said that when you are ready to produce your web files you go to
"File > Publish to the web > Save In: My Documents". I would suggest that
you create a folder in my documents called 'web files'. Then after you
Publish to the web > and get to the "save in:" click the downward pointing
arrow and find the new folder you just created "web files". Direct your
files to that folder so you can easily find them instead of just dumping
them into My Documents. Or, publish your files to your desktop if you
want...just pick a spot where you can find them.

Now one other big change...you apparently typed www.lacyquarterhorse.com in
the File name: field. This results in Publisher producing a home page called
www.lacequarterhorse.com.htm and a supporting files folder called
www.lacyquarterhorse.com_files . This is not what you want to do. Instead
type in "index" in the File name box/field. Now if you look inside the new
'web files' folder you should find an 'index.htm' file and a 'index_files'
folder. You want to upload the index.htm file and the index_files
folder...not the 'web files' folder.

As far as not understanding drag and drop, then google the subject if you
don't understand. It is a matter of left clicking a file, holding down the
mouse button and dragging the file over to another folder and dropping it
into another folder by letting go of the file. If you can't figure that out
then try clicking the file or folder > Edit > copy and then going to the
folder where you want to move it and clicking on that folder > Edit > paste.
If you must go to Help and read the directions on drag and drop, or as I
said, google the subject. How do you move files around without dragging and
dropping or copy and pasting?

I guess given your problems thus far I would highly recommend that you take
my advice about renaming the original index.htm file on your server
index.htm.old before you even try to upload new files, so that if you make
mistake you can go back to a workable copy of your site. Then if you get the
index.htm file uploaded ok, do the same with the index_files folder.

Sorry I can't be of more help. You have many sets of directions written by
experts at Godaddy, filezillla and other places...I can't do better than
those. Perhaps someone else following this thread will jump in and be better
able to help you. good luck

DavidF

David,

I just got off the phone with Go Daddy (my host) and was told the the
folder
"www.lacyquarterhorses.com_files" was uploaded but the "index.htm" file
was
not present and that was why the website cannot change. I reopened
Filezilla
and selected the CD drive where I have them on disc and it only displays
the
"www.lacyquarterhorses.com_files" and does not display the "
www.lacyquarterhorses.com." HTML document, thus, Filezilla only loaded "
www.lacyquarterhorses.com_files". When I view the contents of the CD I
have
both the www.lacyquarterhorses.com_files and the www.lacyquarterhorses.com
HTML Document present on the CD. Why doesn't Filezilla show them both?

Do I need to rename the www.lacyquarterhorses.com HTML Document as "index.
html"? Will it then display in Filezilla? Can I select it exclusively and
upload it?

By the way...Go Daddy says that 4 hours is not at all uncommon for
uploading
a website the size of mine (could it be all that excessive code?) on a
dial-
up connection and that the Failed transfers due to "connection
interrupted"
are quite common on a lengthy dial-up connection and difficult to
successfully reprocess once they have been interrupted. I certainly don't
have the patience to devote that much time to an activity that will likely
produce a defective outcome.

I think, in the future, I would be better off to rely on my third party or
possibly try the library for a faster, more reliable connection to upload
from.

It's been a learning experience anyway.

Thanks,
Kristi

David,

Well Geez!...I guess I'm just retarded. I thought I WAS following the
directions! You all make it sound so easy and I feel soooo STUPID!!!!!!!!
I
don't know exactly how drag and drop works (drag from where & drop to
where?
They didn't say int the instructions!) but I do know how to right-click a
folder and choose "upload". When I did that a bunch of files started
scrolling in the top pane and it lasted for FOUR HOURS and wasn't
successful.
Should I have stopped it before it completed. No I did not try to upload
a .
pub file!

The file folder, www.lacyquarterhorses.com, is present in the remote site
pane of Filzilla along with a bunch of other unfamiliar folders and files
with old dates, but the website doesn't show any changes here on my
computer.
What should I do with it?

I'm not enough of a glutton for punishment to want to do this again unless
I
know what I did wrong (assuming the problem was caused by something I did
wrong) and how to correct it so that it can be completed in a reasonable
amount of time!

Yes, I read the articles which, in some cases, describe different methods
...
suprise suprise. At any rate they didn't give me any answers.

I think it is just as likely that my Netzero dial-up so slow.

Sorry I'm such a poor student,
Kristi

Kristi,

[quoted text clipped - 54 lines]

Thanks so much,
Kristi