index page to be changed

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I created a classical static website.
Now, I also made a flash introduction page to be put on top. But when I try
to change the structure (make of the "flash" html the new index page, and
range the website underneath), fp warns me that all links will be broken. Is
this really so ? How can I restructure the whole thing without danger ?
 
Create a new folder and convert it to a subweb (right click on the
folder, and choose convert to web).
Publish the existing web, without subwebs, to this new subweb.
Delete the pages and files in the root web and replace with the splash
page. Make sure the splash page has links to the real home page.

Your host must support FP extensions and subwebs.
 
That is really the long way around a simple fix.

Before you setup the Flash as the index file do this.

1.Rename your index file to something else and it does not matter what it
is.

Example - rename it to indexenter.htm

It will then prompt you to rename all links to this page. Say yes.

2. Then rename your Flash file to index.htm

Now when your site is pulled up, your Flash page will appear. Edit you Flash
page to redirect to your new "indexenter.htm" page to bring everyone into
your site..

Hope this helps...
 
If the site uses FrontPage navigation components, then all links to
the Home page will go to the Flash splashpage. IMO, not a good idea.
With a subweb, the navigation will work without going back to the
flash page for Home links.
 
Sure a subweb can address this, but it is not neccessary and it would add
another layer of Frontapage extensions on the server.

If you rename the index page to say indexenter (or whatever) the navigation
structure will be realigned to match the change.
The Frontpage navigation does not need a index page assigned to it. That is
why there is a check box to enable or disable the Home Page. This is for
tweaking your site to fit your needs. If you want the navigation to say
"Home Page", you simple change the name in the proprties of - indexenter -
in the Navigation area to say what you want on the navigation component. The
new page name - indexenter - properties in the Navigation can then renamed
to Home Page and that is how it will be displayed even though it is not the
actual Home Page.

This is where you would rename All of the Navigation Buttons displayed to
fit your site.

Piece of cake.
 
How do you figure it will add another layer of FP extensions on the server? You only need to apply
the extensions to the root web, and then you can create a unlimited number of subwebs.

--
==============================================
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.
==============================================
 
Every time you create a subweb, it creates another set of server extension
for that web.
Server extensions are setup and assign to specific webs, not domain names.
If you create a sub web, then a set of server extensions are created for
that particular web.

When you open up the subweb, you will then see another set of folders which
include _private, images and the other hidden _vtf folders created for
forms and such. These hiddens folders and files are the separate set of
server extensions. They function independently from the root web because
they are of a different set. That is why things like the Frontapge
navigation and searches are not able to crossed over from root web to
subweb. It is considered a separate site. This is a good thing.

This makes a subweb a full fledge site all to it's own.
If it would not be a seperate set of extensions, then setting up the index
page the way Ron (below) refers to Would Not work. The way that it can work
the way Ron wants it to work is because of a different set of server
extensions on a different website.

If someone has a limit on hard drive space because of the type of package
that was setup from their ISP, this would be unnecessay wasted disk space
used up for nothing because a folder was converted to a subweb.

Mike ...
 
Not technically correct (and does not affect

Each web/ subweb (on a server) does not create a new version or set of the FP SE w/i the FP web/subweb

Each web / subweb adds a virtual folder
(_vti_bin - containing the only copy of the FP SE on the server),
- which points to the physical location of the single instance of the installed SE,
- thus allowing each web/subweb access to the FP SE independently

Since it is a virtual folder location it adds nothing to the physical "size" of your web when you use subwebs

The other folders you mention (_vti_* ) are all only the FP meta data unique to each site used by the server based FP SE files
- the size of them would be essentially the same whether the pages were in the root or in the subweb, because the content of them
(file size) is based on the site page content
(only difference would be an extra ~ 50 KB for some of the _vti_pvt that are unique to each web/subweb)

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| Every time you create a subweb, it creates another set of server extension
| for that web.
| Server extensions are setup and assign to specific webs, not domain names.
| If you create a sub web, then a set of server extensions are created for
| that particular web.
|
| When you open up the subweb, you will then see another set of folders which
| include _private, images and the other hidden _vtf folders created for
| forms and such. These hiddens folders and files are the separate set of
| server extensions. They function independently from the root web because
| they are of a different set. That is why things like the Frontapge
| navigation and searches are not able to crossed over from root web to
| subweb. It is considered a separate site. This is a good thing.
|
| This makes a subweb a full fledge site all to it's own.
| If it would not be a seperate set of extensions, then setting up the index
| page the way Ron (below) refers to Would Not work. The way that it can work
| the way Ron wants it to work is because of a different set of server
| extensions on a different website.
|
| If someone has a limit on hard drive space because of the type of package
| that was setup from their ISP, this would be unnecessay wasted disk space
| used up for nothing because a folder was converted to a subweb.
|
| Mike ...
|
|
|
|
|
| | > How do you figure it will add another layer of FP extensions on the
| > server? You only need to apply the extensions to the root web, and then
| > you can create a unlimited number of subwebs.
| >
| > --
| > ==============================================
| > 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.
| > ==============================================
| >
| > | >>
| >> Sure a subweb can address this, but it is not neccessary and it would add
| >> another layer of Frontapage extensions on the server.
| >>
| >> If you rename the index page to say indexenter (or whatever) the
| >> navigation structure will be realigned to match the change.
| >> The Frontpage navigation does not need a index page assigned to it. That
| >> is why there is a check box to enable or disable the Home Page. This is
| >> for tweaking your site to fit your needs. If you want the navigation to
| >> say "Home Page", you simple change the name in the proprties of -
| >> indexenter - in the Navigation area to say what you want on the
| >> navigation component. The new page name - indexenter - properties in the
| >> Navigation can then renamed to Home Page and that is how it will be
| >> displayed even though it is not the actual Home Page.
| >>
| >> This is where you would rename All of the Navigation Buttons displayed to
| >> fit your site.
| >>
| >> Piece of cake.
| >>
| >>
| >> | >>> If the site uses FrontPage navigation components, then all links to the
| >>> Home page will go to the Flash splashpage. IMO, not a good idea. With a
| >>> subweb, the navigation will work without going back to the flash page
| >>> for Home links.
| >>> --
| >>> Ron Symonds - Microsoft MVP (FrontPage)
| >>> Reply only to group - emails will be deleted unread.
| >>> FrontPage Support: http://www.frontpagemvps.com/
| >>>
| >>> | >>>> That is really the long way around a simple fix.
| >>>>
| >>>> Before you setup the Flash as the index file do this.
| >>>>
| >>>> 1.Rename your index file to something else and it does not matter what
| >>>> it is.
| >>>>
| >>>> Example - rename it to indexenter.htm
| >>>>
| >>>> It will then prompt you to rename all links to this page. Say yes.
| >>>>
| >>>> 2. Then rename your Flash file to index.htm
| >>>>
| >>>> Now when your site is pulled up, your Flash page will appear. Edit you
| >>>> Flash page to redirect to your new "indexenter.htm" page to bring
| >>>> everyone into your site..
| >>>>
| >>>> Hope this helps...
| >>>>
| >>>>
| >>>>
| >>>>
| >>>> | >>>>> Create a new folder and convert it to a subweb (right click on the
| >>>>> folder, and choose convert to web).
| >>>>> Publish the existing web, without subwebs, to this new subweb.
| >>>>> Delete the pages and files in the root web and replace with the splash
| >>>>> page. Make sure the splash page has links to the real home page.
| >>>>>
| >>>>> Your host must support FP extensions and subwebs.
| >>>>> --
| >>>>> Ron Symonds - Microsoft MVP (FrontPage)
| >>>>> Reply only to group - emails will be deleted unread.
| >>>>> FrontPage Support: http://www.frontpagemvps.com/
| >>>>>
| >>>>> | >>>>>>I created a classical static website.
| >>>>>> Now, I also made a flash introduction page to be put on top. But when
| >>>>>> I try
| >>>>>> to change the structure (make of the "flash" html the new index page,
| >>>>>> and
| >>>>>> range the website underneath), fp warns me that all links will be
| >>>>>> broken. Is
| >>>>>> this really so ? How can I restructure the whole thing without danger
| >>>>>> ?
| >>>>>
| >>>>>
| >>>>
| >>>>
| >>>
| >>>
| >>
| >>
| >
| >
|
|
 
Stefan said:
Each web / subweb adds a virtual folder
Click to expand...

Since it is a virtual folder it is the same as a virtual host.

You can uninstall FP ext on a virtual host and then re-install it and it
does not have any effect on the root site or root folder at all.
The reason that it can install and un-install on virtual is that FP
extensions can become corrupt due to other reasons.

If they are corrupt, then the manner in which you ae pointing to would also
apply to the root and also across all virtuals which is not the case because
it is a seperate instance. It would also apply to every web site on the
server and therfore bring down the server.


(_vti_bin - containing the only copy of the FP SE on the server),
Click to expand...

There is only one copy FP SE on the server as a master copy for the runtime
routine to copy a subset to the virtual host or folder _vti_bin and so on.
The master FP SE are broken down into 2 subsets of SE. One subset is set for
the server and the other set is for the virtual host or folder. So when a
subweb is created, then another (sub) set of server extensions are also
created. Even the basic of websites that are Frontpage sites are twice the
size of a basic site running on a Linux box. It is because of the SE located
on the FP site.


- which points to the physical location of the single instance of the
installed SE,
Click to expand...
This is where the 2nd subset of server extensions that are location on the
virtual host or folders to point to. This is a good thing.


- thus allowing each web/subweb access to the FP SE independently
Click to expand...
This is the end results.









Stefan B Rusynko said:
Not technically correct (and does not affect

Each web/ subweb (on a server) does not create a new version or set of the
FP SE w/i the FP web/subweb

Each web / subweb adds a virtual folder
(_vti_bin - containing the only copy of the FP SE on the server),
- which points to the physical location of the single instance of the
installed SE,
- thus allowing each web/subweb access to the FP SE independently

Since it is a virtual folder location it adds nothing to the physical
"size" of your web when you use subwebs

The other folders you mention (_vti_* ) are all only the FP meta data
unique to each site used by the server based FP SE files
- the size of them would be essentially the same whether the pages were in
the root or in the subweb, because the content of them
(file size) is based on the site page content
(only difference would be an extra ~ 50 KB for some of the _vti_pvt that
are unique to each web/subweb)

--

_____________________________________________
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.frontpagemvps.com/FrontPageNewsGroups/tabid/53/Default.aspx
_____________________________________________


| Every time you create a subweb, it creates another set of server
extension
| for that web.
| Server extensions are setup and assign to specific webs, not domain
names.
| If you create a sub web, then a set of server extensions are created for
| that particular web.
|
| When you open up the subweb, you will then see another set of folders
which
| include _private, images and the other hidden _vtf folders created
for
| forms and such. These hiddens folders and files are the separate set of
| server extensions. They function independently from the root web because
| they are of a different set. That is why things like the Frontapge
| navigation and searches are not able to crossed over from root web to
| subweb. It is considered a separate site. This is a good thing.
|
| This makes a subweb a full fledge site all to it's own.
| If it would not be a seperate set of extensions, then setting up the
index
| page the way Ron (below) refers to Would Not work. The way that it can
work
| the way Ron wants it to work is because of a different set of server
| extensions on a different website.
|
| If someone has a limit on hard drive space because of the type of
package
| that was setup from their ISP, this would be unnecessay wasted disk
space
| used up for nothing because a folder was converted to a subweb.
|
| Mike ...
|
|
|
|
|
| | > How do you figure it will add another layer of FP extensions on the
| > server? You only need to apply the extensions to the root web, and
then
| > you can create a unlimited number of subwebs.
| >
| > --
| > ==============================================
| > 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.
| > ==============================================
| >
| > | >>
| >> Sure a subweb can address this, but it is not neccessary and it would
add
| >> another layer of Frontapage extensions on the server.
| >>
| >> If you rename the index page to say indexenter (or whatever) the
| >> navigation structure will be realigned to match the change.
| >> The Frontpage navigation does not need a index page assigned to it.
That
| >> is why there is a check box to enable or disable the Home Page. This
is
| >> for tweaking your site to fit your needs. If you want the navigation
to
| >> say "Home Page", you simple change the name in the proprties of -
| >> indexenter - in the Navigation area to say what you want on the
| >> navigation component. The new page name - indexenter - properties in
the
| >> Navigation can then renamed to Home Page and that is how it will be
| >> displayed even though it is not the actual Home Page.
| >>
| >> This is where you would rename All of the Navigation Buttons
displayed to
| >> fit your site.
| >>
| >> Piece of cake.
| >>
| >>
| >> | >>> If the site uses FrontPage navigation components, then all links to
the
| >>> Home page will go to the Flash splashpage. IMO, not a good idea.
With a
| >>> subweb, the navigation will work without going back to the flash
page
| >>> for Home links.
| >>> --
| >>> Ron Symonds - Microsoft MVP (FrontPage)
| >>> Reply only to group - emails will be deleted unread.
| >>> FrontPage Support: http://www.frontpagemvps.com/
| >>>
| >>> | >>>> That is really the long way around a simple fix.
| >>>>
| >>>> Before you setup the Flash as the index file do this.
| >>>>
| >>>> 1.Rename your index file to something else and it does not matter
what
| >>>> it is.
| >>>>
| >>>> Example - rename it to indexenter.htm
| >>>>
| >>>> It will then prompt you to rename all links to this page. Say yes.
| >>>>
| >>>> 2. Then rename your Flash file to index.htm
| >>>>
| >>>> Now when your site is pulled up, your Flash page will appear. Edit
you
| >>>> Flash page to redirect to your new "indexenter.htm" page to bring
| >>>> everyone into your site..
| >>>>
| >>>> Hope this helps...
| >>>>
| >>>>
| >>>>
| >>>>
| >>>> | >>>>> Create a new folder and convert it to a subweb (right click on the
| >>>>> folder, and choose convert to web).
| >>>>> Publish the existing web, without subwebs, to this new subweb.
| >>>>> Delete the pages and files in the root web and replace with the
splash
| >>>>> page. Make sure the splash page has links to the real home page.
| >>>>>
| >>>>> Your host must support FP extensions and subwebs.
| >>>>> --
| >>>>> Ron Symonds - Microsoft MVP (FrontPage)
| >>>>> Reply only to group - emails will be deleted unread.
| >>>>> FrontPage Support: http://www.frontpagemvps.com/
| >>>>>
message
| >>>>> | >>>>>>I created a classical static website.
| >>>>>> Now, I also made a flash introduction page to be put on top. But
when
| >>>>>> I try
| >>>>>> to change the structure (make of the "flash" html the new index
page,
| >>>>>> and
| >>>>>> range the website underneath), fp warns me that all links will be
| >>>>>> broken. Is
| >>>>>> this really so ? How can I restructure the whole thing without
danger
| >>>>>> ?
| >>>>>
| >>>>>
| >>>>
| >>>>
| >>>
| >>>
| >>
| >>
| >
| >
|
|
Click to expand...
 
Back
Top