What do you lose without FP Extensions on the server?

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

Guest

I've been publishing without an issue with FP extensions on the server, but
have noticed my images showing up on other sites (using my bandwidth). I put
in protection to prevent that, but it broke my FP extensions (.htaccess mods
conflict).

Since I want the protection, I was wondering what I give up if I don't have
the extensions. Can I publish with ftp and still have the site work exactly
as it would the other way?

Thanks in advance,
 
No, to have the Frontpage functionality of the features using the server
ext. you need to publish by http mode. FTP mode breaks the extensions, so
apparently, does using the .htaccess file.

The server extensions control features such as the ability to publish via
http mode in Frontpage; the html form handler; the search function, the
database features and a number of other things (shared borders for one,
although these can be used without the FPSE, with limitations).

I'm not sure of a way to use both the FPSE and the .htaccess file for the
'hotlinking' protection.
 
What you need to do is place all of the images in one location such as the images folder,
and then add the .htacess file to the images folder.

Leave the main .htaccess file alone.


--
Steve Easton
Microsoft MVP FrontPage
95isalive
This site is best viewed..................
...............................with a computer
 
Thanks... I'll do that.

Turns out there was an issue on the server that caused a problem in addition
to the .htaccess issue. Here is the error I received when trying to re-enable
FPSE:

Attempting to install FrontPage extensions...
Error: 'www.mydomain.com:80' server is not a valid virtual server.
Setting Password
Frontpage passthough auth enabled!

From the hosting company, here is what they did to fix it:

Frontpage gets quirky when it sees your SSL entry and your HTTP entry, so I
had to comment out the SSL entry to get the extensions installed, then
re-enable the SSL. All should be well now with the extensions for your domain.

All is well now and this is the first time I have had this problem hit me
(obviously not the first time it has surfaced on my host's systems though.
 
Back
Top