Losing sight of images directory

M

Mark

Hi,

Can anyone help? My FP2003 seems to not be able to
change back to the www.mysite.com/images directory. I am
stuck looking at the C:\ drive folders and files.

Is there a way to fix this, or do I need to re-install
FP2003? When I use my other PC with FP2000 it can see the
image directory on the web. What causes this to happen?

Thanks
Mark
 
J

Jens Peter Karlsen[FP MVP]

Open the Web in FP. After that you can see the images folder in the
folder view (Provided of course that the Web has a images folder).

Regards Jens Peter Karlsen. Microsoft MVP - Frontpage.
 
S

Steve Easton

It sounds as if you're linking to the images with just a page open, not your web and then a page.
You must open a web, then a page, then link to the images. This way FrontPage "adjusts" the links
to the images during the publishing process.

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
W

Wes

I've seen this answer many times, and even offered it myself. I've
discovered that if you open FP then file/open/, it will open the associated
web along with the page. This also occurs with _edit with FP_ (If it's your
site) and you can publish it immediately. I've also noticed that one does
not need to _import_ a file. Drag/drop, copy - cut/paste, even using
explorer, works just fine as long as it's sent to a folder within the web.
FP will recognize it's presence and adjust accordingly. I get email
attachments, (photos, .PDF) and I save them directly to a web folder (disk
based) without a publish problem. 1 more, you don't need to go to
file/publish. The icon on the toolbar works just fine, otherwise it
wouldn't be there. If you set up your publish destination correctly, there
is no reason to go through all the dialog again. (even if you have 50
websites) The destination is displayed so all ya gotta do is look at it.
I know I'll get feedback on this, but......IT DOES WORK. (Nice job FP)
 
T

Thomas A. Rowe

Wes,

Correct you can do those things in the ways you have mentioned, however they don't always work as
expected for everyone, that is why many of us will post ways to ensure that FP is able to function
correctly.

As you have seen in this newsgroup, many people have posted issues with the ways you have indicated,
and when they switch to the suggested method, it solved their problems.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
 
W

Wes

Respectfully submitted:

Why should a user take the long way around when FP has provided a shortcut?
Why then did they provide it?

Thomas, can you give a specific instance in which this doesn't work for
everybody? And why it wouldn't work on other machines!

Publish is publish! It makes no difference if you go to file/publish etc.,
you still end up in the same place. There are several ways to get there.
1. file/publish (takes you to remote properties hit OK, then publish)
2. remote site (you can select publish from here)
3. toolbar/publish (bypasses above and starts publish process immediately
to the site you have previously configured)
What's in your wallet?

With a number of websites, you should look to saving time and unnecessary
keystrokes and take advantage of the tools FP has provided.
Unless of course.......never mind not gonna go there.
 
T

Thomas A. Rowe

See inline below.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================


Wes said:
Respectfully submitted:

Why should a user take the long way around when FP has provided a shortcut?
Why then did they provide it?

Thomas, can you give a specific instance in which this doesn't work for
everybody? And why it wouldn't work on other machines!

Publish is publish! It makes no difference if you go to file/publish etc.,
you still end up in the same place. There are several ways to get there.
1. file/publish (takes you to remote properties hit OK, then publish)
2. remote site (you can select publish from here)
3. toolbar/publish (bypasses above and starts publish process immediately
to the site you have previously configured)
What's in your wallet?
Click to expand...

First, FP2003 does have some new publishing options over FP2000 and FP2002. However, if you are in a
hurry and use the Publish Button, it is possible to a make a mistake and publish a site to the wrong
location, and if you don't have backup of the site that you just overwrote, then you are up a
creek.. so much for saving time...

Better to be safe then sorry, plus using the File Menu | Publish Web / Site you can choose to change
your publishing options, which you can't do with the Publish Button.
 
W

Wes

inline


Thomas A. Rowe said:
See inline below.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================




First, FP2003 does have some new publishing options over FP2000 and
FP2002. However, if you are in a
hurry and use the Publish Button, it is possible to a make a mistake and
publish a site to the wrong
location, and if you don't have backup of the site that you just
overwrote, then you are up a
creek.. so much for saving time...
Click to expand...
All ya gotta do is look at the publish destination and see where it's going.
If by some mistake it's not the right place, merely stop the process and
reset the destination.
Better to be safe then sorry, plus using the File Menu | Publish Web /
Site you can choose to change
your publishing options, which you can't do with the Publish Button.
Click to expand...

Yes you can it's called STOP. Then you can use _remote site_ to change the
settings.
Besides, if you publish to the wrong site, what's stopping you from
republishing the right site?
It's still on your disk. Unless of course you do stuff live, in which case
this thread is moot.
 
T

Thomas A. Rowe

Please note, I am talking about FP2000 and FP2002, as well as FP2003.

If you publish to the wrong site, you will have to delete the site on the remote server and then
re-publish the correct one, which hopefully you have a local copy of.

In FP2000, when you click the publish button, it will immediately start to publish, if the remote
site happen to be open or has been open at any time during the current FP session. You are not
prompted for the location.

Clicking Stop can leave the extensions in a unstable state on the remote server.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
 
W

Wes

inline

Thomas A. Rowe said:
Please note, I am talking about FP2000 and FP2002, as well as FP2003.

If you publish to the wrong site, you will have to delete the site on the
remote server and then
re-publish the correct one, which hopefully you have a local copy of.
Click to expand...

Overwrite works
In FP2000, when you click the publish button, it will immediately start to
publish, if the remote
site happen to be open or has been open at any time during the current FP
session. You are not
Click to expand...

What does that mean "if the remote site happen to be open or has been open
at any time during the current FP session".

It's gotta be open if yer gonna publish.
prompted for the location.

Clicking Stop can leave the extensions in a unstable state on the remote
server.
Click to expand...

It's still in a temp directory, and FP will just stop the UL and delete the
temp files.
It doesn't continue the process or update anything. (of course you need to
stop it before it gets to the processing stage)
 
T

Thomas A. Rowe

Overwrite works, but doesn't delete content on the remote server, so if you upload the wrong site
with the content of another, then if you overwrite the correct content, you will still have content
from the wrong site in the site, unless all of your pages and images are named the same.

If the site already open in the current FP session, you are not prompted, and the publishing starts
immediately, if the site is has not been open in the current FP session your prompted to login,
giving you a change to change your mind.

The STOP button has a impact on the extensions on a remote server, even if no files have been
transferred.

--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle, MS KB Quick Links, etc.
==============================================
 
S

Steve Easton

It all depends upon how you have FrontPage set up.!!
If set to automatically open the "last" web, when you click File > Open you will be presented with a
list of files "inside" the web that automatically opened.

In my case with several webs in one directory, when I click File > Open, what opens is the directory
containing a list of web folders. I then select the web I want to work with and then open the
folder / page I want to edit.

As for the icon on the toolbar, you are correct, it works fine "if you have a web open."

If you are working with multiple webs / multiple instances of FrontPage running with one instance
for each web for example, it is best to use File > Open Site , File > Publish Site as it will save
you a "bunch" of headaches someday.

Even more so if you are running multiple versions of FrontPage with different webs open in different
versions.
(or even the same web open in 2 different FrontPage versions )
Yep, it can be done )

;-)

--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed............
........................with a computer
 
Top