Hyperlink does not display new page

[Guest]

I have hyperlinked Acrobat (pdf) files to pages within my website. The first
version is "A" and I might need to replace it with version "B" etc. I save
the newest version over the older one using the same file name. However, when
I save the webpage and check the links before and after publishing, it keeps
brining up the older version of the Acrobat file. The only way I've been able
to correct this is by re-linking, which is just what I was hoping to avoid.
Has anyone else experienced this?

Also, I've tried "Recalculate Hyperlinks" and that doesn't do anything. Anne
W.

 

[David Berry]

When you say version A & B, are the file names the same? If not then you'll
have to change the link each time.

 

[Guest]

You must be pulling up cached versions of the old docs. If you truly
replaced Version "A" with Version "B", your hyperlinks can't bring up the
older ("A") version because it doesn't exist anymore! Hit Ctrl-Refresh on
your Web page and see what document the hyperlink brings up.

 

[Guest]

I'm answering two questions here: When I said version A and B, I only meant
that I was making changes to the same document and the file name remains the
same. (We use A, B, C, etc., to show the lastest revision.)

I agree with you about the cached versions and I'll try refreshing. The
problem is this is an intracompany website and it appears that others within
the company are running into the same problem. In fact, I didn't even know
this was happening until I was contacted by another employee. I have actually
gone to the file where the "new" page was saved and opened it in Acrobat and
it shows the newest version, just not when I'm trying to look at it on the
company website.

I'm wondering if this has anything to do with the way we are publishing?
What's frustrating is the company was using Microsoft Publisher for their
website and I talked them into using FrontPage. They didn't seem to have this
problem with Publisher.

Thanks. Anne W.

 

[David Berry]

All you should have to do is import the new version into your web (overwrite
the old one) and then publish. You shouldn't have to change the hyperlink
if the name stays the same.

What are the steps you use?

BTW, Publisher is NOT a web site design tool. It's primary use is for
desktop publishing (creating layouts for newsletters, brochures etc) even
though you can save pages as HTML that's not what it's designed for.
FrontPage is a web development tool.

 

[Guest]

Thanks, David, for responding because this is very frustrating. I'm at home
and don't have FrontPage on this computer, so bare with me. These are pages
that are updated in Microsoft Word and then saved as "pdf" files. The updated
file is exactly the same name as the one that is hyperlinked. However, when
everything is saved and published, we are still seeing the "old" file. But,
if we actually relink (which is what we're trying to avoid to save time),
then the correct "new" file is displayed.

Maybe it's not Publisher they were using; it was part of a Microsoft
"package" and it was horrible. But, now these people are complaining because
the way they were doing it before appears to have worked better, at least
when it came to updating hyperlinked files.

I've used other web publishing software and haven't had this problem, so I'm
sure it has to be something we're doing wrong. When I preview the page with
the new file, it should show up correctly.

And here's another weird kink that I just remembered. We have a lot of
technical drawings that are also hyperlinks and also "pdf" format. We
discovered that a number of them were incorrect and so we had to go to
another company website that had copies of the correct drawings and replace
those pages. (We were able to open an Acrobat file from their website and
save it to ours--don't worry, it was legal.) The only difference was these
replacements had been named differently. So, when I saved them over the
incorrect "older" hyperlinked document, I either changed the name to the
"older" document by typing it, or selected that document in the file list so
its name appeared in the "Save" file name. When it asked me if I wanted to
replace it, I selected "OK." THAT worked fine.

We do a lot of updates and I'm trying to find ways to keep things simple and
avoid having to a) relink and b) search for files that need to be deleted
(because the "old" file would now be obsolete and a different name if I
cannot overwrite it). I didn't have to worry about that with the technical
drawings because the ones we copied were not on our site to begin with.

Anne W.

 

[Thomas A. Rowe]

How are you upload these replacement documents?

Have you try deleting the current document, then uploading the new document?

If the live/remote server has the FP extensions, then you should always maintain the site content
via FP.

--
==============================================
Thomas A. Rowe
Microsoft MVP - FrontPage
==============================================
Agents Real Estate Listing Network
http://www.NReal.com
==============================================

 

[Guest]

I'm publishing to local files (I think that's it). We don't have a dedicated
server, so the files that we use to create and update or website in FrontPage
are published to another folder on the same server. But, shouldn't I be able
to see my updates when I preview, even before publishing?

Also, we aren't using extensions, but most things seem to work anyway. I had
used an older version of FrontPage and I remember that I created a "server"
on my computer for testing and I had to add the extensions, but it seems like
this latest version doesn't require that. Besides, I'm working for a company
that doesn't have a clue about any of this stuff. It's very frustrating! I'm
certainly no expert on this sort of thing and when I've done websites for
others in the past, I've published to a web server. (Sorry, if my technical
knowledge is lacking.)

 

[Guest]

I think it's working. I've gone back and made several tests now and I seem to
be getting the correct pages. I'm running into problems in that I'm working
with a company where NO ONE knows much about creating websites, let alone
using FrontPage. I had used it in the past without problems. Now I'm trying
to help a department update their website and teach them how to do it
themselves. I hadn't been having a problem updating files, but they did and I
couldn't track the problem. Thank you everyone for responding. Anne W.