Re: Sites After Upgrade to WSS 2.0
From: Troy Starr [MSFT] (troys_at_online.microsoft.com)
Date: 03/25/04
- Next message: Erik Johnson: "Picture"
- Previous message: Erik Johnson: "Picture"
- In reply to: Warren: "Re: Sites After Upgrade to WSS 2.0"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 25 Mar 2004 15:12:19 -0800
Hi Warren -
It's still unclear to me what types of links they are... if they're links in
a list, if they're links in a document, if they're navigation structure
links, etc. Generally, links in links lists will be fixed up the following
way:
original site: http://foo.bar/abc
link in original site: http://foo.bar/abc/def.ghi
new site: http://foo.baz/xyz
link in new site: http://foo.baz/xyz/def.ghi
Note that if the name "def.ghi" changes as a result of migration, we will
not fix that link up to take that into account. Also, if the link
originally pointed to a sibling web or a parent web, we will not fix that up
as well. If you need to fix up a link in a links list, then you should
click on the "Documents and Lists" navigation link at the top of the page,
then select your list, and then edit the list item in question.
In documents, we generally only fix up page-relative links. (For example,
if you had a page-relative link to the AllItems.htm view in your v1 web,
then we'll fix it up to point to the AllItems1.aspx view in your v2 site.)
We don't fix up absolute or server-relative links. Note that we won't
fix-up page-relative links that originally pointed outside of you v1 web
either. Those would have to be fixed up by editing the document manually.
To sum up, there will probably be some places where you will need to perform
link fixup yourself.
- Troy Starr [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
"Warren" <anonymous@discussions.microsoft.com> wrote in message
news:108ed01c41285$94eb1080$a601280a@phx.gbl...
> Thanks again for the response, Troy. I'm going to use my
> servers' real names. The old STS 1.0 server is
> http://noles and the new WSS 2.0 server with site name is
> http://project/mx.
>
> On the home page, I have the following links: Product
> Management, IS Department, Development. They ALL point
> to the correct spot (http://project/mx). However, if I
> click on Product Management, only the topmost links have
> the correct spot linked; the two other links and their
> sites beneath them have the old server (http://noles)
> connected.
>
> I've gone to Modify Shared Page and its options, but I
> can't find where to change those links.
>
> Thanks for your help!
>
>
> >-----Original Message-----
> >Hi Warren -
> >
> >Smigrate can fix some links as a result of migration,
> but it depends on what
> >types of links they are (absolute, server-relative, or
> page-relative), where
> >they're pointing to (a file within that site, a list
> within that site,
> >content within a subweb below that site, content in a
> sibling or parent
> >web), as well as if they're URL fields in lists, links
> in documents, or
> >something else. If you give me details on what types of
> links you're having
> >problems with, I can let you know if that's expected.
> >
> >- Troy Starr [MSFT]
> >This posting is provided "AS IS" with no warranties, and
> confers no rights.
> >
> >
> >"Warren" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:12a6401c411b9$5877ba80$a301280a@phx.gbl...
> >> I recently ran the smigrate utility to move from STS
> 1.0
> >> to WSS 2.0. My STS 1.0 server was a Windows 2000
> Server
> >> (server1); WSS 2.0 is running on Windows Server 2003
> >> Standard Edition (server2). On the STS 1.0 server, I
> did
> >> the following:
> >>
> >> smigrate -w http://server1 -f c:\upgrade\backup -y
> >>
> >> It seemed to work fine and created several files:
> >> backup.fwp, backup1.fwp, backup2.fwp, etc. I then
> typed
> >> the following on server2 after installing IIS6, the
> >> indexing service, ASP.NET and WSS 2.0 and creating a
> site
> >> named http://server2/mx:
> >>
> >> smigrate -r -w http://server2/mx -f \\server1
> >> \upgrade\backup.fwp -u -pw
> >>
> >> However, now most, but not all, of my links on my new
> >> http://server2/mx site point back to http://server1.
> >> What am I missing? Do I restore backup1.fwp,
> >> backup2.fwp, etc. as well or should it do it all at
> once?
- Next message: Erik Johnson: "Picture"
- Previous message: Erik Johnson: "Picture"
- In reply to: Warren: "Re: Sites After Upgrade to WSS 2.0"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
