Re: Parent Path issues

Tech-Archive recommends: Fix windows errors by optimizing your registry



I use FP code/html view to edit ASP code. Provided the code is well
written there should not be any problems. If you have doubts, make a
backup first.

Well written code does NOT do things like:

Open a table in HTML and close it in ASP code.
Open a table in ASP code and close it HTML

In both the above, and similar open-close tag scenarios, FP will
change the code to correct the HTML.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/

"JayPelham" <JayPelham@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:33B34B92-4CA8-42B7-A3DC-9D6B6A28B273@xxxxxxxxxxxxxxxx
Ron,

Thanks for your reply. These are asp pages. However, if I open
them in
Frontpage and select the HTML tab to fix the code, am I going to
mess
something up? Should I just edit them in Notepad instead?

Thanks!
Jay

"Ronx" wrote:

The parent paths issue normally only affects paths that are written
in
asp code or in asp/ssi includes
<!-- #include file="../inc/foo.asp" --> will have to be re-written
as
<!-- #include virtual="/inc/foo.asp" -->

and <% response.write("<img src=""../images/image.jpg"">) %>
will become <% response.write("<img src=""/images/image.jpg"">)
%>

but relative paths in HTML will not be affected:
<p><img src="../images/image.jpg"></p> should be OK as it is.

Note that all the FrontPage database wizards use relative paths -
which can be a pain in these circumstances.
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/

"JayPelham" <JayPelham@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3BCFABC3-089C-4810-A5F3-59AEF21863A6@xxxxxxxxxxxxxxxx
In regards to my last question, here is a more specific question.
Our
hosting company upgraded their servers from Windows Server 2000
to
2003. One
of the major effects it had on our site was we lost functionality
of
a search
engine that searched our product inventory. I have found out
that
the
problem is with the way FP wrote paths in the code, using
"../Images/image1.jpg" instead of "root/Images/image1/jpg". This
was fully
acceptable with Server 2000, but apparently not with 2003. Our
hosting
company will not enable the Parent Path option for us, so I am
left
to go in
and manually correct the code. My question is this... If the
Image
folder
being referenced is in the root directory (where the webpages are
saved), do
I need to have the root directory in the path, or can I just use
"/Images/image1.jpg" as the path? Or should I just use the exact
url of the
image? By the way, the website is www.greenchiponline.com.

Thanks
Jay Pelham





.



Relevant Pages

  • Re: Parent Path issues
    ... Open a table in HTML and close it in ASP code. ... FrontPage Support: http://www.frontpagemvps.com/ ... acceptable with Server 2000, ...
    (microsoft.public.frontpage.addins)
  • Re: FP_ASP component
    ... FP can work with pages that have ASP code just fine, it all depends on how the pages where coded. ... Avoid using the FP database component, if the code will need to be modified, as hand coding will ... FrontPage Resources, WebCircle, MS KB Quick Links, etc. ...
    (microsoft.public.frontpage.client)
  • Re: FP_ASP component
    ... as you really can only modified the FP generate ASP code that is in grey. ... FrontPage Resources, WebCircle, MS KB Quick Links, etc. ... > keep disappearing because he opens the page in FrontPage. ... > this FP code, but it moves it below, so it still does not execute. ...
    (microsoft.public.frontpage.client)
  • Re: Parent Path issues
    ... Ron Symonds - Microsoft MVP (FrontPage) ... FrontPage Support: http://www.frontpagemvps.com/ ... Open a table in HTML and close it in ASP code. ...
    (microsoft.public.frontpage.addins)
  • Re: DWT prevents proper database post?
    ... Mike -- FrontPage MVP '97-'02 ... > template, and then when the template is applied (placing ... >>- and the DWT editable regions (which you appear to have ... >>If your ASP code in the page was in a noneditable region ...
    (microsoft.public.frontpage.programming)