Why won't Nav. Bar appear when I Publish my custom site?

[Gttrgrl2005]

Self teaching in Pub.03..Building a 7 page website..No Template. Got it
Published to Web, but the Navigation bar won't appear and only the 1st page
does..Any suggetions?? Thank you

 

[DavidF]

The only compatibility issues with Publisher 2003 and 2007 and IE8 RTW
reported thus far are problems associated with 'grouping'. Any design
elements that are 'grouped' together, which includes the Publisher wizard
built navbars, do not render when you view the web page in IE8 . The fix in
general is to ungroup the elements. There is both a manual fix to these
issues and a Service Patch that has been issued to fix it for Pub 2007.

Reference: Navigation bars and other content is missing from Publisher HTML
output in Internet Explorer 8: http://support.microsoft.com/kb/969705

A manual method of fixing this grouping issue:

Go to each page > Edit > Select All (or Ctrl+A) > Arrange > Ungroup. This
will ungroup the Publisher built navbar and disconnect it from the wizard,
and the navbars will render correctly in IE8.

Publisher 2007 can be fixed manually or with the Office 2007 SP2:

Reference: Description of 2007 Microsoft Office Suite Service Pack 2 (SP2)
and of Microsoft Office Language Pack 2007 SP2:
http://support.microsoft.com/?kbid=953195

Some users have found SP2 breaks Publisher, and makes it impossible to open
existing Pub files...you know, break one thing to fix another, so there is a
hotfix for that:

Description of the Publisher 2007 hotfix package (Publisher.msp): June 30,
2009
http://support.microsoft.com/kb/972566/

DavidF

 

[Spike]

David

You might consider adding to you comments the need to save a copy of the pub
file before ungrouping for future work as the wizards will be broken in the
ungrouped version.

Spike's two cents

 

[DavidF]

Ok.

DavidF

David

You might consider adding to you comments the need to save a copy of the
pub file before ungrouping for future work as the wizards will be broken
in the ungrouped version.

Spike's two cents

 

[ARHall]

I have multiple web sites I've created using Publisher 2003, one of which has
nearly 50 pages! Having to ungroup all the navbar objects each time I want to
Publish to Web (while remembering NOT to save the .pub file after having done
that), is unaccepable. It is incomprehensible to me that the IE8 team did not
communicate with all the Microsoft teams whose products create web pages in
order to make sure that IE8 was fully compatible with the products Microsoft
itself ships. Microsoft, get a clue. In this day and age, overlooking such a
basic thing as that is financially foolish, if not incompetent. I love
Publisher and have been using it to create my multiple web sites since 2001.
I don't want to be forced to buy and learn another product (from a different
company, I assure you).

 

[Spike]

ARHall

MS advice is to upgrade to Publisher 2007
As of yet there is no patch for 2003
http://support.microsoft.com/kb/969705

Spike

 

[Gttrgrl2005]

Thank you very much..I will try that!

The only compatibility issues with Publisher 2003 and 2007 and IE8 RTW
reported thus far are problems associated with 'grouping'. Any design
elements that are 'grouped' together, which includes the Publisher wizard
built navbars, do not render when you view the web page in IE8 . The fix in
general is to ungroup the elements. There is both a manual fix to these
issues and a Service Patch that has been issued to fix it for Pub 2007.

Reference: Navigation bars and other content is missing from Publisher HTML
output in Internet Explorer 8: http://support.microsoft.com/kb/969705

A manual method of fixing this grouping issue:

Go to each page > Edit > Select All (or Ctrl+A) > Arrange > Ungroup. This
will ungroup the Publisher built navbar and disconnect it from the wizard,
and the navbars will render correctly in IE8.

Publisher 2007 can be fixed manually or with the Office 2007 SP2:

Reference: Description of 2007 Microsoft Office Suite Service Pack 2 (SP2)
and of Microsoft Office Language Pack 2007 SP2:
http://support.microsoft.com/?kbid=953195

Some users have found SP2 breaks Publisher, and makes it impossible to open
existing Pub files...you know, break one thing to fix another, so there is a
hotfix for that:

Description of the Publisher 2007 hotfix package (Publisher.msp): June 30,
2009
http://support.microsoft.com/kb/972566/

DavidF

 

[DavidF]

I can appreciate your frustration and share it. I suspect that there are
marketing forces within MSFT that result in products being rushed to the
market before they are as fully developed and debugged as they should be, or
before other product groups have had time to test and fix their product
compatibility. Perhaps that was the case with IE8, with MSFT fast loosing
market share to FireFox, Chrome and other browsers, I am sure there was a
lot of pressure to get the new version out there. But in their defense I
would also say that at least they seem to be moving in a good direction away
from nonstandards compliant html code. IE8 is designed to render webpages in
a more 'standards code compliant' mode than any previous version, and that
is probably a good thing in the long run. In general, many websites built by
many different programs including Publisher do not produce 'standards
compliant code' and have 'compatibility' issues in IE8. If you care to read
more about the details of these general statements here are two articles:

Reference: Release Notes for Internet Explorer 8: Compatibility issues with
websites:
http://msdn.microsoft.com/en-us/dd441788.aspx

Reference: MSDN IEBlog:Just The Facts: Recap of Compatibility View:
http://blogs.msdn.com/ie/archive/2009/02/16/just-the-facts-recap-of-compatibility-view.aspx

Unfortunately this is probably the price of progress, but luckily the only
compatibility issues with Publisher 2003 and 2007 and IE8 RTW reported thus
far are problems associated with 'grouping'. As Spike suggested you could
upgrade to Pub 2007 and install the Office 2007 SP2, which fixes this in
most cases, but there are trade offs with 'upgrading' from Pub 2003.

Since it sounds like most of your site(s) are probably fairly evolved and
static, I would suggest that you look at the possibility of ungrouping the
wizard built navbars permanently. How often do you add pages or new sections
that you want to add to the navbar on every page of the site? Don't forget
that you can insert the existing navbar again anytime in the future and it
would be connected to a 'new wizard' if you need to do this. (go to insert >
navbar > existing) So think about ungrouping those pages that will not
likely be updated in the near future or linked to new sections of your site
and leave the navbars ungrouped.

Perhaps you could work faster from the keyboard only? Go to your first page

CTRL + A (select all) > CTRL + Shift + G (ungroup). Then CTRL + G (go to

page) > key the next page number > Enter, and repeat CTRL + A > CTRL + CTRL
+ G. You might be able to move through your publication pretty fast without
using the mouse at all.

Another idea to consider is building your site with multiple Publisher
files? This is used by many Publisher users as their sites get larger as it
makes it easier to manage. You would build the static part of your site with
one Publisher file, ungroup the navbars, upload it, and be done with it.
Then build the other pages or sections that change periodically with other
Publisher files. This way you only need make the needed changes for IE8 in
most of your site just once, and you also save the time involved in
uploading the whole site each time. I went this direction when my Publisher
sites started getting too big and cumbersome to upload them each time I made
even a small change. I organize my host directory into subfolders and put
each set of Publisher web files in the subfolders and cross link the files,
but there are a number or ways to organize this. Here is an article that
describes one way: Building a web site with multiple Publisher web
publication files : http://msmvps.com/blogs/dbartosik/pages/81264.aspx

Once again, I do appreciate your frustration, but the silver lining in all
of this was that the only compatibility problem with IE8 was the grouping
issue...it could have been worse.

DavidF