My navigation bar dissappeared

[kihouse]

I dont think I changed anything. On the web there is now longer a nav bar.
There is on freinds mac (I have pc). Also, the nav bar is now gone in web
page preview mode. I'm using office (front page) 2003. Two sites are
involved. The same happened to both. bandkhouse.com and studiowoodworks.net

 

[Ronx]

The page displays in Firefox without serious problems - one or two links do
not work, but that's to be expected when VML graphics are used. In Internet
Explorer, all the navigation and some of the content is lost in the VML
mire. It cannot be diagnosed by sight - the only solution is to edit the
page in the same program as it was created.

This is the first time I have ever seen Internet Explorer defeated by VML,
while FireFox displays reasonably - it is usually the other way round.

See http://www.rxs-enterprises.org/tests/vml-graphics/
for reasons why VML should be avoided on the web.
--
Ron Symonds
Microsoft MVP (Expression Web)
http://www.rxs-enterprises.org/fp

Reply only to group - emails will be deleted unread.

 

[kihouse]

Hi Ronx, I made the sites with MS Office Publisher and use publisher to
edit. Any suggestions.

 

[Ronx]

Scrap the sites and start again with FrontPage or Expression Web.
Seriously. Publisher is the worst ever program to choose for creating or
editing web pages. Publisher is very good for the purpose it was designed:
Printed documents, but for the web? notepad is better.

Have you looked at your pages in View Source in a browser? Do you understand
any of it?
Look at any other web page (not made in Publisher, Word Excel or PowerPoint)
and a lot more of it can be understood by anyone - I am not saying
*everything* will be clear, but most of the markup will be readable.
--
Ron Symonds
Microsoft MVP (Expression Web)
http://www.rxs-enterprises.org/fp

Reply only to group - emails will be deleted unread.

 

[kihouse]

Thank you Ronx, I have looked at the source and dont understand much. I've
heard before that publisher isn't the best choice for this but was the paht
of least resistance at the time. Now that I've struggled through (others
I've asked can still see the sites on their computers) I'm hoping there is a
quick fix for this. maybe someone out there has an idea. Thanks again

 

[kihouse]

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/

If you have other questions about Publisher webs, I would suggest you post
in the Publisher web design group and we will try to help you there:

http://www.microsoft.com/office/com...soft.public.publisher.webdesign&lang=en&cr=US

DavidF

 

[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/

If you have other questions about Publisher webs, I would suggest you post
in the Publisher web design group and we will try to help you there:

http://www.microsoft.com/office/com...soft.public.publisher.webdesign&lang=en&cr=US

DavidF

 

[kihouse]

Thank you David, The fix worked, as I'm sure you knew it would, and just
before my head popped.

Light, Brian

 

[DavidF]

Glad to hear you avoided a head popping .

I noticed that your images are loading slowly. You might want to consider
compressing 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

DavidF

 

[kihouse]

Thanks David, I already compressed once. Some people (maybe with huge
monitors) have said some pics have lost res. I haven't yet figured out how
to easily track which are compressed and how many times.

Brian

 

[Ronx]

Compression is a not a lossless process, so you should only compress an
image once. Save the original image, and make copies for working on. If the
compression on an image is not sufficient, then discard that image and start
over with a new copy.
I use the free Irfanview (http://irfanview.net) for optimising .jpg images.
--
Ron Symonds
Microsoft MVP (Expression Web)
http://www.rxs-enterprises.org/fp

Reply only to group - emails will be deleted unread.

 

[kihouse]

Hi Ron, If compression isn't sufficient the first time, why would it be
from a fresh copy the second?

 

[Ronx]

You would apply more compression the second time than you did before. A
decent graphics editor lets you specify the amount of compression that is
applied - I generally use about 20%, but some images I have used 60% without
any visible loss of image quality (we are working with web pages here - not
printed publications). And "decent" does not mean expensive - for image
optimisation Irfanview is very good, and free.

Applying more compression to an already compressed image will lose quality,
too often visibly.

You can see the effects of different degrees of compression in the examples
at
http://www.rxs-enterprises.org/fp/?fl=1030205063
--
Ron Symonds
Microsoft MVP (Expression Web)
http://www.rxs-enterprises.org/fp

Reply only to group - emails will be deleted unread.

 

[DavidF]

As per Ron's comments, the ideal is to 'optimize' your images for the web
using a third party image editor such as irfanview before you insert them
into your Publisher publication. In that process you can change the
dimensions, the resolution and the compression. The Publisher 2003
'Compress Pictures' feature does these things in one step but does not allow
you to adjust the actual compression or give you the same level of control
as Ron describes. I think you get a default of 30% compression if memory
serves, and the web resolution is at 96 ppi.

One way you can tell if you have 'compressed' an inserted JPG files using in
Publisher 2003 is by looking at the web files that are produced when you
'Publish'. If you aren't doing so already when you File > Publish to the Web
direct your html output to a folder on your local drive where you can easily
find them. Unless you have changed the default settings Publisher will
produce an index.htm file (your home page) and an 'index_files' folder that
contains all the other pages in your web plus your supporting graphics. Open
the index_files folder and look at the image files in thumbnail view. If you
have inserted a jpg, resized the image box to less than 100% scale, and NOT
compressed the image, Publisher 2003 will make two copies of that image. One
will be the original dimension and file size, and the other will be a copy
that is smaller. Usually they will be named image###.jpg and image###1.jpg.
The original will be served up when your site is viewed with IE in the
dimensions you specified in your picture box but without reducing the actual
file size, thus the long loading time; and the copy will be rendered by
FireFox and other non-IE browsers. If you use the 'compress graphics'
feature on an inserted jpg you will not get the two copies. You will get one
resampled, resized 'compressed' image at 96 ppi that will be rendered by all
browsers.

This is all getting a bit off topic for this newsgroup. If you want to
pursue this issue or have other questions about Publisher webs, please post
your questions in the Publisher web design group and we will try to help you
there.

DavidF

 

[Jennifer Carr]

Hi
I had axactly the same problem with Publisher and tried everything, including several rebuilds. Eventually found a site (didnt keep the address though) and talked about this being a problem for 2003 and it was related to the groups and that they needed to be ungrouped. I then checked Help and the solution was simply in your 'Master Copy' highlight your overall navigation box, right click and select 'UNGROUP', Select 'YES' on the pop up warning to continue. Do this for each page on your website, then 'Publish to the Web. It published straight away and I have no further problems.
Hope this helps. Jennifer



kihouse wrote:

My navigation bar dissappeared
28-Jul-09

I dont think I changed anything. On the web there is now longer a nav bar.
There is on freinds mac (I have pc). Also, the nav bar is now gone in web
page preview mode. I'm using office (front page) 2003. Two sites are
involved. The same happened to both. bandkhouse.com and studiowoodworks.net

EggHeadCafe - Software Developer Portal of Choice
WPF DataGrid Custom Paging and Sorting
http://www.eggheadcafe.com/tutorial...f-32b2d802ae17/wpf-datagrid-custom-pagin.aspx

 

[Jennifer Carr]

Hi
I had axactly the same problem with Publisher and tried everything, including several rebuilds. Eventually found a site (didnt keep the address though) and talked about this being a problem for 2003 and it was related to the groups and that they needed to be ungrouped. I then checked Help and the solution was simply in your 'Master Copy' highlight your overall navigation box, right click and select 'UNGROUP', Select 'YES' on the pop up warning to continue. Do this for each page on your website, then 'Publish to the Web. It published straight away and I have no further problems.
Hope this helps. Jennifer



kihouse wrote:

My navigation bar dissappeared
28-Jul-09

I dont think I changed anything. On the web there is now longer a nav bar.
There is on freinds mac (I have pc). Also, the nav bar is now gone in web
page preview mode. I'm using office (front page) 2003. Two sites are
involved. The same happened to both. bandkhouse.com and studiowoodworks.net

EggHeadCafe - Software Developer Portal of Choice
WPF DataGrid Custom Paging and Sorting
http://www.eggheadcafe.com/tutorial...f-32b2d802ae17/wpf-datagrid-custom-pagin.aspx