Phasing Out Frontpage Extensions - FTP Publishing

Unfortunately Microsoft in its Wisdom has decided to phase out FrontPage Extensions. . They have already discontinued new releases, bug fixes or security patches for UNIX/LINUX web servers and will soon discontinue support for Windows Server platforms. For this reason many hosting companies have already completely phased out FrontPage Extensions.

Reference:

http://office.microsoft.com/en-us/assistance/HA101205221033.aspx
http://www.microsoft.com/presspass/features/2006/feb06/02-15Designer.mspx
http://www.microsoft.com/products/expression/en/web_designer/default.mspx
http://www.microsoft.com/office/preview/programs/designer/highlights.mspx

Although Frontpage is still a very easy to use web design application it is highly recommended that you DO NOT use frontpage extensions due to this decision by Microsoft and they can cause problems which will be harder to fix now that support has been withdrawn by Microsoft

1stChoiceWebHost are in the process of migrating from FrontPage extensions. You may have found you cannot publish your website using the Microsoft FrontPage extensions. If this is the case please consider publishing via FTP below.

Note: As long as you are not using webbots (Insert -> Web Component), forms, counters, etc., you can generally publish your FrontPage designed site using FrontPage FTP with no apparent difference.

We have taken precautions to keep sites reliant upon FrontPage extensions on FrontPage enabled servers for the time-being. However, this dependency is not always readily ascertained or within our control due to security patches and updates and in some rare cases you may need to be moved to a FrontPage enabled server while you transition your website to non-dependency. If your need more time before making this transition, please create a support ticket to be moved to a server that still contains FrontPage extensions. This can be accessed from the support desk

Publishing Via FTP

FTP or File Transfer Protocol, is what all other web development software uses to publish content. As long as you are not using webbots (Insert -> Web Component), forms, counters, etc., you can generally publish your FrontPage designed site using FrontPage FTP with no apparent difference.

Note, however, we cannot guarantee a perfect transition of the website away from FrontPage extension dependency. The implementation of this transition ultimately lies on the webdesigner or website owner. We can often point you in the right direction, however, and in some cases a semi-routine fix can be applied for a nominal one-time fee.

1. Open the local copy of your website in FrontPage
2. Click File >> Publish Site
3. Choose FTP
4. Remote Website Location: ftp://ftp.webhero.com
5. FTP Directory: /public_html

Note: Use /public_html/www.domain.com/ if publishing to a Hosting Club subdirectory)

6. Use Passive FTP: Leave unchecked

Note: If having problems publishing, e.g., you connect, but cannot move files try using Passive FTP you get around your Firewall.

7. Click ok
8. Enter username and password.

Note: Your FTP username may not be the same as your FrontPage username. Please contact support for your FTP username.

9. Confirm directory you are publishing to and click Publish Website.


Additional Notes:

Forms and counters can generally be replaced.

Use the search feature against:

"Replacing FrontPage Counters"

"Replacing FrontPage forms with FormMail".


Other notes:

UNIX was the operating system used to develop the Internet and continues to be the dominant web server platform. Windows Server Operating Systems do have a significant, but smaller portion of the server market, but new releases, bug fixes or security patches to these platforms will also soon be discontinued. Your website is most likely hosted on a UNIX platform unless you specifically required Microsoft proprietary components.

Microsoft has since replaced FrontPage with other products such as SharePoint Designer 2007, and Expression Web. These programs, while still offering backward compatibility with extensions, do not default to using extensions, but rather they default to using the web standard, FTP.

Reference:
http://office.microsoft.com/en-us/assistance/HA101205221033.aspx
http://www.microsoft.com/presspass/features/2006/feb06/02-15Designer.mspx
http://www.microsoft.com/products/expression/en/web_designer/default.mspx
http://www.microsoft.com/office/preview/programs/designer/highlights.mspx