Publishes "do not publish" htm files & makes new content folders

[Guest]

Migrating to new server, and having a strange problem...
Publishing copies the content (images, xml filelists) of html pages which
are marked "Do not publish" and puts them in newly-created content folders on
the remote server. These content folders fo not exist on the local server.
Ex. test.htm contains links to several images and is marked "do not Publish"
on the local server. When I publish, Frontpage creates a new content folder
named test_files and places the images there. Most curious....
Any clues? I'm wondering if someone saved the file as "web page complete" in
MSIE and renamed it .htm? What code in the page relates to the web page
complete options?
Thanks for any help you can provide.

 

[David Berry]

There would be a comment at the top of the page that says "saved from URL
........ " Also, if you look in Code View you'll see the paths to your images
etc as <page name>_files/

What you need to do is fix all the links to your images etc so that they
point to files in your web. Then publish.

 

[Guest]

I think I have a clue now from the author. She used CTRL-ALT-PRNTSCRN to
capture an image and pasted it into FrontPage without editing. The Windows
Metafile is a strange format that I do not claim to understand. Is it
maintaining the separate components of the screen capture?
Conducting a test now - I'll edit the screencap in photoshop and save before
placing in the html page.

Interesting though, that even when the html page is marked "do not publish"
Frontpage published the linked content in this case.

Thanks,

 

[Ronx]

Do the pages contain any VML graphics (Text boxes, Word Art, Shape Art,
or other objects from the drawing toolbar)? Or has Word, Publisher, or
Powerpoint been used to edit the page?
Downlevel images from these are stored in thicket folders named
pagename_files, where pagename is the name of the related page. Thicket
folders are always hidden in FrontPage. However, when you publish,
unless you mark the files in the thicket folder as "Do not Publish" (not
easy since they cannot be seen), they will be published with the rest of
the web, and since the associated page is not published they become
visible on the server - the thicket on the server is broken.

--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.

http://www.rxs-enterprises.org/fp

FrontPage Support: http://www.frontpagemvps.com/