Top link bar and Publishing Infrastructure

[Paulius M]

Hello experts,

I'd really really appreciate any help with this annoying problem:

We have two site collections: one is for our main intranet site
(intranet.lan) and another one is for Project Server (intranet.lan/
PWA). When we enable Publishing Infrastructure, our top link bar is
messed up - in both site collections first tab from left now links to
the root site. Example:

Before Publishing Infrastructure enabled:

Top link bar in intranet.lan site collection: | Intranet Main Site |
PWA | etc
Top link bar in intranet.lan/pwa site collection: | Intranet Main Site
| PWA | etc

After Publishing Infrastructure enabled:

Top link bar in intranet.lan site collection: | Intranet Main Site |
PWA | etc
Top link bar in intranet.lan/pwa site collection: | PWA | Intranet
Main Site | etc

If we go to Site Settings > Modify Navigation we see all links from
top link bar except root site.. So it looks like you cannot reorder
top link bar in pwa site collection from user interface. How can we
reorder top link bar in PWA to look like this: | Intranet Main Site |
PWA | etc ?

We use MOSS 2007 and Project Server 2007. And if it helps - our MOSS
version is 12.0.4518.1016.

 

[Gary L. Chefetz]

Paulius:

I'm not sure what you're problem is. It is normal SharePoint behavior that
the selected site tab is always displayed furthest to the left. The tabs
shift as you click from site to site.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com

 

[Paulius M]

So you are saying, that it is normal that site tabs change places,
according to the site collection you are in?

But I haven't ever seen such behavior - nor in any web sites, nor in
any program's interface. Is there some hidden logic in this, cause I
don’t see it..

Also, if we don't have Publishing Infrastructure enabled - top link
tabs do not switch places. So users are used to the same top link bar
where ever they are in the site. From the point of usability - this
change is really bad, since you always knew that if you click the
first tab from left - you go to the main (intranet) site. And this
seems intuitive. After enabling Publishing Infrastructure this
changes..

Also selected site tab is usually highlighted, not displayed furthest
to the left. Of course in this case they do shift - but only if you
change site collection, not site.

I don’t say that it is a critical problem, but this change is annoying
for sure

Paulius

 

[Gary L. Chefetz]

Paulius:

Yet, I've never seen it work any other way when switching between two site
collections.

--
----------
Gary L. Chefetz, MVP
MSProjectExperts
Project Server Consulting: http://www.msprojectexperts.com
Project Server Training: http://www.projectservertraining.com
Project Server FAQS: http://www.projectserverexperts.com
Project Server Help Blog: http://www.projectserverhelp.com


So you are saying, that it is normal that site tabs change places,
according to the site collection you are in?

But I haven't ever seen such behavior - nor in any web sites, nor in
any program's interface. Is there some hidden logic in this, cause I
don’t see it..

Also, if we don't have Publishing Infrastructure enabled - top link
tabs do not switch places. So users are used to the same top link bar
where ever they are in the site. From the point of usability - this
change is really bad, since you always knew that if you click the
first tab from left - you go to the main (intranet) site. And this
seems intuitive. After enabling Publishing Infrastructure this
changes..

Also selected site tab is usually highlighted, not displayed furthest
to the left. Of course in this case they do shift - but only if you
change site collection, not site.

I don’t say that it is a critical problem, but this change is annoying
for sure

Paulius

 

[Paulius M]

OK, i give up - thats not a bug, that's a feature
thanks for your time to answer.