G
Guest
I am trying to redirect a webpage but cannot access the "Add" button under
Page Properties -- Custom (tab).
Page Properties -- Custom (tab).
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
D
David Berry
Some options that are not cross-browser compatible may not be available
unless you go to Tools, Page Options, Authoring and make sure the drop downs
are set to Custom and check all the boxes.
unless you go to Tools, Page Options, Authoring and make sure the drop downs
are set to Custom and check all the boxes.
G
Guest
All are set to Custom and boxes are all checked. I am trying to re-direct a
web page. Is this function somehow affected by the use of a Dynamic Web
Template?
web page. Is this function somehow affected by the use of a Dynamic Web
Template?
T
Thomas A. Rowe
Just switch to HTML/Code view and add whatever tag you want to the head section of the page.
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
--
==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
==============================================
If you feel your current issue is a results of installing
a Service Pack or security update, please contact
Microsoft Product Support Services:
http://support.microsoft.com
If the problem can be shown to have been caused by a
security update, then there is usually no charge for the call.
==============================================
R
Ronx
If you have a DWT attached to the page, the change must be in an editable
area - there should be an editable region surrounding the <title>...</title>
tags, but it would be better to add a region on the DWT and update all
pages.
area - there should be an editable region surrounding the <title>...</title>
tags, but it would be better to add a region on the DWT and update all
pages.
G
Guest
Since I'm looking at re-directing individual pages, it wouldn't make sense
for me to update the DWT, which would in effect redirect ALL of the pages the
DWT was attached to correct?
As for the editable vs. non-editable regions, since I'm doing a "Page
Property" action, I would think that editable and non-editable regions
wouldn't come in the picture since the re-direct affects the entire page, not
just a region of a page.
for me to update the DWT, which would in effect redirect ALL of the pages the
DWT was attached to correct?
As for the editable vs. non-editable regions, since I'm doing a "Page
Property" action, I would think that editable and non-editable regions
wouldn't come in the picture since the re-direct affects the entire page, not
just a region of a page.
Ronx said:If you have a DWT attached to the page, the change must be in an editable
area - there should be an editable region surrounding the <title>...</title>
tags, but it would be better to add a region on the DWT and update all
pages.
R
Ronx
The Page properties will not attempt to write anywhere in a page that is
protected by a DWT, except to overwrite existing code in an editable region.
This is by design - if the <head> section of a page is protected by the DWT,
you cannot change it whichever method you use to edit, except by manually
changing the code and then fighting FrontPage to retain the change, and it
will revert the next time you update the DWT. Hence the need for an
editable region, and manually adding the code to that region either in the
DWT for new pages only, or in the actual page in Code view. (You can then
use Page Properties to *change* that code.)
protected by a DWT, except to overwrite existing code in an editable region.
This is by design - if the <head> section of a page is protected by the DWT,
you cannot change it whichever method you use to edit, except by manually
changing the code and then fighting FrontPage to retain the change, and it
will revert the next time you update the DWT. Hence the need for an
editable region, and manually adding the code to that region either in the
DWT for new pages only, or in the actual page in Code view. (You can then
use Page Properties to *change* that code.)
G
Guest
There is an editable region on the page but I am befuddled as to what "code"
I should be writing in that area to allow the page to be re-directed. When
I've attempted to right click and use the Page Properties function, it has
always been from the editable region of the page and not the header sections
which is locked by the DWT.
I am still not clear about making changes directly to the DWT as well. The
properties thru the re-direct function appears to show that you have to put
in a re-direct URL. If I made a change to the DWT, that change would
technically affect all of the pages tied to the DWT would it not? Isn't that
the whole point of the DWT, to make a change in one specific area to affect
ALL attached pages rather than having to update each page individually?
If there is a simple code that simply allows the usage of the Page
Properties re-direct function without having to specify a re-direct URL via
the DWT, that would be extremely helpful.
I should be writing in that area to allow the page to be re-directed. When
I've attempted to right click and use the Page Properties function, it has
always been from the editable region of the page and not the header sections
which is locked by the DWT.
I am still not clear about making changes directly to the DWT as well. The
properties thru the re-direct function appears to show that you have to put
in a re-direct URL. If I made a change to the DWT, that change would
technically affect all of the pages tied to the DWT would it not? Isn't that
the whole point of the DWT, to make a change in one specific area to affect
ALL attached pages rather than having to update each page individually?
If there is a simple code that simply allows the usage of the Page
Properties re-direct function without having to specify a re-direct URL via
the DWT, that would be extremely helpful.
R
Ronx
Anything written in an editable region in a DWT is used as a default for
*new* pages. Existing pages are not updated, unless they do not have this
editable region. For these, you would have to edit each page and delete the
redirection tag - easily done since it is in an editable region.
The Page Properties writes meta tags into the <head> section, no matter
where you are on the page. With a DWT attached, only if there is an
editable region in the <head> section. So, to use Page Properties to write
your redirection tag, there must already be an editable region. This is the
default for a DWT - the page <title> is placed in an editable region.
[Note - this works on my page, but this may be because I already have other
meta tags in the same region as the page <title>]
To place your redirection tag in a page, there must be an editable region in
the <head> section of the page - requires editing the DWT and updating the
page - and using code view to actually insert the redirection tag.
So, in the DWT you would add
<head>
<title>...</title>
more meta tags
<!-- #BeginEditable "customtags" -->
<!--Place custon meta tags here -->
<!-- #EndEditable -->
more meta tags
</head>
In the page, after attaching the DWT, you can edit in code view to give:
<head>
<title>...</title>
more meta tags
<!-- #BeginEditable "customtags" -->
<!--Place custon meta tags here -->
<meta http-equiv name=refresh" content="10;url=http://example.com/page.htm">
<!-- #EndEditable -->
more meta tags
</head>
--
Ron Symonds
Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
*new* pages. Existing pages are not updated, unless they do not have this
editable region. For these, you would have to edit each page and delete the
redirection tag - easily done since it is in an editable region.
The Page Properties writes meta tags into the <head> section, no matter
where you are on the page. With a DWT attached, only if there is an
editable region in the <head> section. So, to use Page Properties to write
your redirection tag, there must already be an editable region. This is the
default for a DWT - the page <title> is placed in an editable region.
[Note - this works on my page, but this may be because I already have other
meta tags in the same region as the page <title>]
To place your redirection tag in a page, there must be an editable region in
the <head> section of the page - requires editing the DWT and updating the
page - and using code view to actually insert the redirection tag.
So, in the DWT you would add
<head>
<title>...</title>
more meta tags
<!-- #BeginEditable "customtags" -->
<!--Place custon meta tags here -->
<!-- #EndEditable -->
more meta tags
</head>
In the page, after attaching the DWT, you can edit in code view to give:
<head>
<title>...</title>
more meta tags
<!-- #BeginEditable "customtags" -->
<!--Place custon meta tags here -->
<meta http-equiv name=refresh" content="10;url=http://example.com/page.htm">
<!-- #EndEditable -->
more meta tags
</head>
--
Ron Symonds
Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
[/QUOTE]tw_webex said:There is an editable region on the page but I am befuddled as to what "code"
I should be writing in that area to allow the page to be re-directed. When
I've attempted to right click and use the Page Properties function, it has
always been from the editable region of the page and not the header sections
which is locked by the DWT.
I am still not clear about making changes directly to the DWT as well. The
properties thru the re-direct function appears to show that you have to put
in a re-direct URL. If I made a change to the DWT, that change would
technically affect all of the pages tied to the DWT would it not? Isn't that
the whole point of the DWT, to make a change in one specific area to affect
ALL attached pages rather than having to update each page individually?
If there is a simple code that simply allows the usage of the Page
Properties re-direct function without having to specify a re-direct URL via
the DWT, that would be extremely helpful.