? End-of-Life for FrontPage 2002 Server Extensions for UNIX ?

[DSG]

I'm a common user, but am trying to confirm what I have written here.

To Clarify End-of-Life for Microsoft FrontPage 2002 Server Extensions for
UNIX. As Microsoft says, effective June 30, 2006, UNIX servers have removed
FrontPage 2002 Server Extensions, as this material is the property of
Microsoft.

Then I suppose we who are not commercial, e.g., personal home pages, and who
are publishing to UNIX servers, should go to Tools, Page Options,
Compatibility tab and UNcheck "Enabled with Microsoft FrontPage Server
Extensions."

I have been told recently, by a our local technician and also by a customer
care person at the head office, because of a certain problem I was having,
that since I am a residential customer (personal home page on UNIX), that I
do not have FrontPage Extensions. In 2001, it was a prerequisite to state
upon application for a personal home page whether I wanted to "Enable
FrontPage" which I did.

Questions:
(1) Local ISP customers haven't been notified about this. So is it
understood that *no* UNIX servers offer FrontPage Extensions?

(2) Do we have anyone on the forum who is familiar with these changes who
can state, "Yes, you need to uncheck 'Enabled with Microsoft FrontPage
Extensions" in Tools, Page Options, Compatibility? (FP2000)

(3) If that is so, then under the "Technologies" list in the same dialog,
which of the technologies do we need to uncheck?

(4) Should it make a difference in Publishing? The reason I ask is because I
have heard that for a UNIX server, the only functions of FrontPage
Extensions was for the purpose of using the Publish function (as opposed to
FTP), and for copying back the FrontPage permissions to publish. Since
about June, I have been getting a wecerr error that says, "You are not
authorized to perform the current operation." Would this be the proper
error report that would occur because of FrontPage Extensions support no
longer occurring on a UNIX server?

DSG

 

[Ronx]

FrontPage extensions for Unix are no longer supported by Microsoft or RTR
(who actually build and maintain them). Hosts that deploy the extensions
have the choice to continue to deploy the extensions, or remove them - they
have always had this choice, the difference now is that they get no help
from the manufacturers when/if things go wrong. This applies to all Unix
servers, and all websites on Unix servers, whether they are personal or
commercial web sites or servers.

See inline below for further comments
--
Ron Symonds - Microsoft MVP (FrontPage)
Reply only to group - emails will be deleted unread.
FrontPage Support: http://www.frontpagemvps.com/

I'm a common user, but am trying to confirm what I have written here.

To Clarify End-of-Life for Microsoft FrontPage 2002 Server Extensions
for
UNIX. As Microsoft says, effective June 30, 2006, UNIX servers have
removed
FrontPage 2002 Server Extensions, as this material is the property of
Microsoft.

Then I suppose we who are not commercial, e.g., personal home pages, and
who
are publishing to UNIX servers, should go to Tools, Page Options,
Compatibility tab and UNcheck "Enabled with Microsoft FrontPage Server
Extensions."

Only if your host removes the extensions. It is their choice. I would
leave that checked, since it affects availability of form templates, even
if extensions are not being used.

I have been told recently, by a our local technician and also by a
customer
care person at the head office, because of a certain problem I was
having,
that since I am a residential customer (personal home page on UNIX), that
I
do not have FrontPage Extensions. In 2001, it was a prerequisite to state
upon application for a personal home page whether I wanted to "Enable
FrontPage" which I did.

Questions:
(1) Local ISP customers haven't been notified about this. So is it
understood that *no* UNIX servers offer FrontPage Extensions?

No. Tripod are Unix, and still offer extensions for new customers, most
(if not all) are for personal websites.

(2) Do we have anyone on the forum who is familiar with these changes
who
can state, "Yes, you need to uncheck 'Enabled with Microsoft FrontPage
Extensions" in Tools, Page Options, Compatibility? (FP2000)

You do not need to uncheck that (see above), but if extensions are not
available, make sure you don't use anything that requires them.

(3) If that is so, then under the "Technologies" list in the same
dialog,
which of the technologies do we need to uncheck?

(4) Should it make a difference in Publishing? The reason I ask is
because I
have heard that for a UNIX server, the only functions of FrontPage
Extensions was for the purpose of using the Publish function (as opposed
to
FTP), and for copying back the FrontPage permissions to publish. Since
about June, I have been getting a wecerr error that says, "You are not
authorized to perform the current operation." Would this be the proper
error report that would occur because of FrontPage Extensions support no
longer occurring on a UNIX server?

The extensions allow more than just publishing - form processing, hit
counters, custom link bars, custom backgrounds in shared borders are all
items available in 2002 extensions (some of these require FP2002 or later).
All these are available on Unix and Windows servers.

Removing the extensions will affect publishing. The alternative is FTP.
With FTP publishing it is possible that every page in your may have to be
uploaded, wheras with HTTP publishing (with extensions) only one changed
page will be uploaded. This scenario will occur if a page that is included
in every page is edited. Also (obviously) components that require the
extensions will fail.

FrontPage FTP is somewhat less reliable than 3rd party FTP clients.

 

[DSG]

Thanks, Ronx, for getting involved in the details. I just find it difficult
to find the right person at our ISP who actually seems to know what's going
on. You've given me a lot of information.
DSG

: FrontPage extensions for Unix are no longer supported by Microsoft or RTR
: (who actually build and maintain them). Hosts that deploy the extensions
: have the choice to continue to deploy the extensions, or remove them -
they
: have always had this choice, the difference now is that they get no help
: from the manufacturers when/if things go wrong. This applies to all Unix
: servers, and all websites on Unix servers, whether they are personal or
: commercial web sites or servers.
:
: See inline below for further comments
: --
: Ron Symonds - Microsoft MVP (FrontPage)
: Reply only to group - emails will be deleted unread.
: FrontPage Support: http://www.frontpagemvps.com/
:
: : > I'm a common user, but am trying to confirm what I have written here.
: >
: > To Clarify End-of-Life for Microsoft FrontPage 2002 Server Extensions
: > for
: > UNIX. As Microsoft says, effective June 30, 2006, UNIX servers have
: > removed
: > FrontPage 2002 Server Extensions, as this material is the property of
: > Microsoft.
: >
: > Then I suppose we who are not commercial, e.g., personal home pages, and
: > who
: > are publishing to UNIX servers, should go to Tools, Page Options,
: > Compatibility tab and UNcheck "Enabled with Microsoft FrontPage Server
: > Extensions."
:
: Only if your host removes the extensions. It is their choice. I would
: leave that checked, since it affects availability of form templates, even
: if extensions are not being used.
:
: >
: > I have been told recently, by a our local technician and also by a
: > customer
: > care person at the head office, because of a certain problem I was
: > having,
: > that since I am a residential customer (personal home page on UNIX),
that
: > I
: > do not have FrontPage Extensions. In 2001, it was a prerequisite to
state
: > upon application for a personal home page whether I wanted to "Enable
: > FrontPage" which I did.
: >
: > Questions:
: > (1) Local ISP customers haven't been notified about this. So is it
: > understood that *no* UNIX servers offer FrontPage Extensions?
:
: No. Tripod are Unix, and still offer extensions for new customers, most
: (if not all) are for personal websites.
:
: >
: > (2) Do we have anyone on the forum who is familiar with these changes
: > who
: > can state, "Yes, you need to uncheck 'Enabled with Microsoft FrontPage
: > Extensions" in Tools, Page Options, Compatibility? (FP2000)
:
: You do not need to uncheck that (see above), but if extensions are not
: available, make sure you don't use anything that requires them.
:
:
: >
: > (3) If that is so, then under the "Technologies" list in the same
: > dialog,
: > which of the technologies do we need to uncheck?
: >
: > (4) Should it make a difference in Publishing? The reason I ask is
: > because I
: > have heard that for a UNIX server, the only functions of FrontPage
: > Extensions was for the purpose of using the Publish function (as opposed
: > to
: > FTP), and for copying back the FrontPage permissions to publish. Since
: > about June, I have been getting a wecerr error that says, "You are not
: > authorized to perform the current operation." Would this be the proper
: > error report that would occur because of FrontPage Extensions support no
: > longer occurring on a UNIX server?
:
: The extensions allow more than just publishing - form processing, hit
: counters, custom link bars, custom backgrounds in shared borders are all
: items available in 2002 extensions (some of these require FP2002 or
later).
: All these are available on Unix and Windows servers.
:
: Removing the extensions will affect publishing. The alternative is FTP.
: With FTP publishing it is possible that every page in your may have to be
: uploaded, wheras with HTTP publishing (with extensions) only one changed
: page will be uploaded. This scenario will occur if a page that is
included
: in every page is edited. Also (obviously) components that require the
: extensions will fail.
:
: FrontPage FTP is somewhat less reliable than 3rd party FTP clients.
: >
:
: > DSG
: >
: >
:
: