Frontpage EOL and Termination of Support

[dvanburen]

Unix Frontpage Extensions reached EOL on June 30th, 2006 and Windows Frontpage Extensions are no longer actively developed. Because of these developments and the possible security risks they pose we have decided to remove Frontpage Extensions from our Unix and Windows servers on January 15th, 2008. We will terminate active support for Frontpage effective October 31st, 2007. We recommend that you and/or your client switch to an application that is not dependent on server side extension, such as Dreamweaver or Microsoft Expression Web by October 31st 2007 to avoid any interruptions in service.

We realize that a number of our clients rely on Frontpage and this will not be an easy transition. In an effort to ease the transition we have tried to give adequate lead time to allow you to prepare. We feel that January 15th, roughly 4 months off, is the right time to remove Frontpage Extensions. Feel free to ask questions in this thread though you may get faster responses from support via email. Just please remember that this is not a support thread, any Frontpage issues you have on or before October 31st, 2007 should be directed to our support staff.

Roadmap:

October 31st, 2007 - Support for Frontpage Extensions terminated, though it will remain enabled on our servers.

January 15th, 2008 - Frontpage Extensions will cease to work altogether when they are removed from both our Unix and Windows servers.

In case you are wondering why we chose January 15th... we didn't want anyone that left this to the last minute to have to try and rush to get it done over the holidays.

[SRW]

David,

I understand about not supporting Frontpage Extensions on Unix.....but not on Windows Server 2003 ???

Where exactly is Microsoft saying that support for Extensions on 2003 Server is being stopped?
AFAIK it will be supported until "End of Life" for Server 2003!

http://msmvps.com/blogs/spiderwebwom...08/405204.aspx

I can potentially lose half my customers....all using FrontPage for maintaining sites....
Especially since there are MANY hosting companies offering FP extensions on Windows.....

Please reconsider this policy for Windows.....

SRW

[dvanburen]

Originally Posted by SRW

Where exactly is Microsoft saying that support for Extensions on 2003 Server is being stopped?

I didn't say they had. I said they are no longer being actively developed. Frontpage as a whole has been replaced.

Edit: You can still use the FTP functionality of frontpage, but any component that depends on server side extensions will not function.

[SRW]

Originally Posted by dvanburen

I didn't say they had. I said they are no longer being actively developed. Frontpage as a whole has been replaced.

Edit: You can still use the FTP functionality of frontpage, but any component that depends on server side extensions will not function.

Thanks, I have been using Expression Web and Office SharePoint Designer 2007 for a while now as a Microsoft Partner..... But that does not mean all my customers are willing to stop using the FrontPage Extension Features!
They don't care about Microsoft no longer actively developing the Extensions.... They just want to continue using what the have!

No way I can justify to them NOT having FP extensions on 2003 Server anymore when Microsoft is very much still supporting it! I have a few large customers with MS Support contracts and that will be the 1st thing they ask MS if I tell hem we are no longer supporting it.....

What exactly would be the rational I give these customers for NOT having FP Extension available anymore?
Can't be EOF and "no security updates" because that is just NOT true...

Thanks,
SRW

[dvanburen]

Originally Posted by SRW

Can't be EOF and "no security updates" because that is just NOT true...

Stop putting words in my mouth. I did not say any of this. It's EOL, not EOF, btw.

[opt2004]

If Vortech is no longer going to be supporting it and you need it, then go somewhere else to find what you need.

[SRW]

Originally Posted by dvanburen

Stop putting words in my mouth. I did not say any of this. It's EOL, not EOF, btw.

Not trying to.... And sorry for the typo!

Just trying to understand the reason for not having it available on Server 2003.....
Customers do ask questions!

[torobravo]

I agree with SRW that the sudden unavailability of a feature widely used in the industry, should not be taken without a good reason. The fact that Windows Frontpage extensions are no longer actively developed is definitely NOT a good reason. Several features available on hsphere are no longer actively developed and I wonder what would remain if we removed all of them?

[kattouf]

Although i always hated FP, this will be a big problem for many users, especially the ones who sign up between now and January. I understand it has to be done. But turning of the Windows version is not justified yet but i assume it is a technical thing, i don't think hsphere can support having it only on one platform... anyway, my users have been notifed.

[levseltzer]

Originally Posted by dvanburen

You can still use the FTP functionality of frontpage...

Do you mean "FTP" in the true sense, or the web publishing feature called "FrontPage Server Extensions" that is part of MSFP and MS Expression Web? I make use of this feature every day - I find I can publish much faster using this, rather than using standard FTP. While I have already migrated away from most features that require FP Server extensions, I would not like to lose this particular feature.

[Joaquinest]

Without the extesiones FrontPage services for my clients will be lost.

Please reconsider this policy for Windows.

[mdwatkin]

Originally Posted by dvanburen

<snip>We recommend that you and/or your client switch to an application that is not dependent on server side extension, such as Dreamweaver or Microsoft Expression Web by October 31st 2007 to avoid any interruptions in service.<snip>

Dear Admin(s): Most of my customers that use FP to manage their content can cutover to MSEW (MS Expression Web) - it isn't that different. However I don't see on your roadmap when / where you plan to install the Sharepoint Services that the recommended MSEW requires to connect to the server. Can you update your plan to let us know when this will happen?

[dpyers]

I don't think MSEW requires Sharepoint Services. Been using it for a while now without them.

FP had code it it to support both web and sharepoint development. MS split that code into two different products - one for web, and one for Sharepoint.

Cutting over to MSEW from FP is not trivial for many users. MSEW requires understanding of web standards and conventions that FP did not. Many will not make the leap.

[soky]

The full version of MSEW (MS Expression Web) is much like the last version of FP. I haven't been using it because of laziness mostly but I think people who are familiar with FP should be able to use it.

Personally, I'll be happy to see the extensions go. I've built sites since Front Page Express and FP95 (Still have the disk) and I steered away from using the extensions long ago. Admittedly however, I have continued to use FP to access my sites because it was easy and what I was used to.

I was concerned when the announcement came that the extensions would be removed because of my use of FP not the features of the extensions. Someone explained above about the issues of no more security patches and the effect it could have on a shared host environment. From a security standpoint, I support the decision. From a customer retention and PR standpoint... well... I'm not so sure. It will cost some customers, the question Vortech now faces is do they let those customers go? Or do they find ways to keep them through effective communication and education? Or... would it be easier to spend money to attract new customers to replace those who can't (won't) live without FrontPage extensions?

[dpyers]

FP and MSEW look the same, but under the covers they're different. MSEW has a very CSS orientation and isn't as tightly integrated with MS Office - no Word"art", cnt-n-paste from Word/Excel doesn't produce the same look, etc.

I think the biggest impact will be on Personal and SOHO sites. I've been pushing Personal sites towards Portals and SOHO towards CMS for some time now. Some are very easy to use and contain a lot more functionality than they can get from FP.
The point though should be to treat this as an opportunity and sell it to clients as such (you can even blame MS).

When you announce to the clients the termination of FP, have an alternative for them at the same time. Sell them a Portal/CMS plan for $3-$5 a month more (money that they don't have to spend buying Dreamweaver). A lot easier for them to learn a Portal than learning web development would be. Your time/costs are mostly up front setting up the package and doing quick installs. Low maintenance for you on the back-end. You can offer Conversion services on a per-site Cost plus basis if the client has stuff worth converting.

Don't give them bad news - give them better news.

When all is said and done though, like Dave, I'll miss the FP admin stuff. There were a lot of reports in one place. Always turned on FP just for the reports. Love the link checker.