I even found a blog from the creator that had an email address, but, again, useless.īased on my horrible experience with Expressions I am going to try to hang on to using my good old trusty FP as long as possible. I sent a lengthy email to the development team, detailing the myriad of problems I had trying to get the program functional, but got no response.
Although I did try to download and install and buy Expressions, it was such a total disaster that I gave up. Sorry, not truly related to this thread, but after spending several hours now looking for answers, I'm getting desperate. Let us know if you have any other questions. But again, you will need to find out by asking or experimentation. So, for example, your web site may be in a folder named "public_html," which is the root folder of the HTTP web site, making other directories outside of "public_html" only available to you when using FTP to access your web site. The difference is that when you are using FTP, you are accessing the actual directories and files in your web site, whereas, when a user is accessing the web site using HTTP, the URL may be a "virtual directory name" which is different than the actual folder name. You can ask your hosting service what folder(s) to publish to, or you can try publishing a page or two via FTP, and see where they end up when accessing the site using HTTP. The web site will still be accessed by users using HTTP, in the same way as before.Īs for the folder(s) you publish to, that is entirely a matter of the hosting service's configuration. This is only relevant to you when publishing.
The reason that the URL to the web site begins with "ftp" instead of "http" is that you are using a different protocol than HTTP to publish. But you won't need to have FrontPage server extensions installed in your web site to publish, and it will be faster and easier.įTP is an old protocol, and stands for "File Transfer Protocol." It is highly reliable and simple. So, if yuo want to publish with FTP, which is a good way to go, you will probably need to do away with any FrontPage form handlers and WebBots in your web site. If you don't publish using FrontPage server extensions, they break. Some FrontPage components can work without them, but many cannot, as they require the server extensions for publishing, not just when being used on the web site. ThanksįrontPage server extensions are a special kind of web server extension which requires HTTP to work, and have been problematic since they were first used.
I am just unsure about how to publish correctly and the entire website and how to change my settings now to publish using FTP, rather than FrontPage with FSE. I am not liking this change, but I knew it would have to happen eventually. Is it supposed to be now, or is it supposed to be something totally different and into your public_html directory? I have searched the web for hours and hours and cannot find any answers.ġ) When publishing a website originally designed with FrontPage, with Expression Web, FTP method, do you disable your FrontPage Extensions on your domain accountĢ) When publishing, it looks like the remote site is no longer, it now appears to have to have "ftp://" in front of it. If anyone can help me, I would really appreciate it. I have never published using FTP, so I am not sure about some things. My website host has just transitions to new servers, which have major issues with FrontPage Extensions, so I was highy reccomended to switch to Expression Web for all of my website design and publishing, now. I am by far, no expert and only experienced enough to make it work, without knowing all the guts and techs. FrontPage was discontinued after 2003.I, like Many, have been using Front3 for several years creating and publishing my website with no problems. There was a single Macintosh version released in 1998. The actual result: FrontPage became a laughing stock, gave WYSIWYG HTML editors a bad name in general, and web developers went back to developing using sticks, stones, VT100 terminals, and Microsoft Notepad.įor the most part, FrontPage was Windows-only. The intention was to create browser lock-in. Unfortunately, as Microsoft enhanced the product they made FrontPage documents render incorrectly in browsers other than Microsoft Internet Explorer. So why should HTML documents be any different? Really, you would not try to write a Microsoft Word document in binary would you? By the mid 1990s, few word processors still exposed internal formatting codes or markup, and those that did were viewed as relics of the 1970s mainframe/terminal era. Microsoft FrontPage is a WYSIWYG HTML editor/Cuisinart for Microsoft Windows.įrontPage was supposed to enable developers to create web pages graphically, without manually messing around with markup code.