FrontPage Server Extensions for Unix? 45
beetle496 asks: "Okay, so I didn't research my choice of ISP adequately. Despite running Apache 2.0 on Red Hat, the only option for dynamic content they support is FrontPage Server Extensions. I am quite comfortable with X/HTML and CSS, and am okay with JavaScript. I am annoyed enough that I would buy FrontPage, were it available for my preferred platform. I've performed the customary MSDN and Google searches. The best I came up with was a page on FrontPage UNIX Server Extensions, which sounds exactly on target, but didn't help me. Can anyone point me toward a resource on writing HTML code to make use of FPSE (aka, webbot) -- without using FrontPage?"
power of choice (Score:5, Insightful)
use the power of choice: change ISP's
Re:power of choice (Score:4, Insightful)
Re:power of choice (Score:5, Informative)
Freeshell: $36 ONE TIME, 100MB web space (also 100MB shell and 100MB mailbox), Perl, PHP, and Python ALL supported for dynamic content, and you can put almost anything in your webspace.
Which sounds like the better idea?
Re:power of choice (Score:1)
I am surprised that no one here thinks making use of FPSE by hand is an interesting hack.
Re:power of choice (Score:2)
I don't deny that it's interesting, but not easy.
See, Microsoft is going to make it a royal PITA.
You're almost better off writing your HTML, then getting someone with FrontPage to put the components that you need in. (And, no, I'm not doing that...)
Re:power of choice (Score:1)
Re:power of choice (Score:1)
FrontPage anything... (Score:3, Informative)
yep, change ISPs.
Web standards are scary enough without adding yet another layer of, "more to go wrong".
Re:FrontPage anything... (Score:3, Informative)
I do believe FP (even the 2003 version which I happen to have tried recently because I was given a copy for free) is hands down the worst web editor out there. (Well, okay, it's a tie between FP and MS-Word!
So yeah, change ISPs...
Re:FrontPage anything... (Score:1)
You might start by rooting around Microsoft's MSDN site for information.
\\Greg
Re:FrontPage anything... (Score:1)
The time wasted for a buggy outcome, will certainly exceed any money thrown away.
"...start by rooting around Microsoft's MSDN site..."
lol, not sure you meant the pun, but I alternatively read that as rooting the MSDN site, (running Linux), and use that for your host.
I think... (Score:5, Funny)
You love to be hated? (Score:2)
Microsoft will make using Frontpage on Linux the most painful experience you've ever had, trying to force you into switching to Windows.
Re:You love to be hated? (Score:2)
using frontpage on MSware is also painful, forcing you into trying other new things.
$10 says... (Score:5, Interesting)
<?php phpinfo(); ?>
Then, visit the page in your browser. If you see the code, or it wants you to download the file, you're SOL. Otherwise, rock on!
Re:$10 says... (Score:3, Insightful)
Re:$10 says... (Score:1)
Re:$10 says... (Score:1)
Frontpage extensions for WINDOWS (Score:3, Interesting)
Re:Frontpage extensions for WINDOWS (Score:2, Informative)
Re:Frontpage extensions for WINDOWS (Score:2)
Re:Frontpage extensions for WINDOWS (Score:1)
Re:Frontpage extensions for WINDOWS (Score:2)
Re:Frontpage extensions for WINDOWS (Score:1)
You have GOT to be kidding me (Score:5, Insightful)
I have the unfortunate "pleasure" of supporting the Frontpage extensions on about 40 production web hosting servers. They are *horrible*. I mean *HORRIBLE*. When they work, they work fine, but then they quit working, it sometimes takes wiping out a clients site, reinstalling the extensions, and then having them re-publish from *scratch*. Oh yeah, great stuff there.
Do yourself a favor and use a few PHP or Perl scripts do do what you need to do. There's nothing in Frontpage that can't be done in PHP or Perl. Its NOT that great. Heck I've done prettier, more functional sites using shtml and php.
Just reading this post makes me feel like I'm watching a bad horror movie and the main character is about to enter the room where the axe murderer is waiting, and everybody in the audience KNOWS there's an axe murderer. "DONT GO IN THERE!" somebody shouts.
Remember, Friends don't let friends use Frontpage.
Re:You have GOT to be kidding me (Score:3, Informative)
Re:You have GOT to be kidding me (Score:2)
Frontpage for UNIX is EOL'd (Score:5, Informative)
Perhaps you should find a new ISP since your current one is using obsolete software.
Re:Frontpage for UNIX is EOL'd (Score:2, Informative)
you would buy it ? (Score:1, Insightful)
The 90's called .. (Score:1)
Sheesh. "Frontpage Extensions"
[OT] For the love of Gods, WHY? (Score:1)
- it looks horrid! Make the bleeding stop!
Re:[OT] For the love of Gods, WHY? (Score:1)
Overview: Frontpage extensibility (Score:5, Informative)
As other people have mentioned, FPSE is obsolete. Today, you are supposed to use client-side dynamic (webbot, DTC, add-in) or more modern server-side dynamic (ASP) techniques. A lot of things including navigation can be handled design-time, reply or email if you're interested in that topic. I do everything design-time; it's my preferred method, and FP2003 is my preferred tool.
However you can still use a webbot for server-side dynamic behavior. Visit MSDN and download the Frontpage 2002 SDK [microsoft.com]. Don't worry, it's not outdated. The extensibility models haven't changed between versions.
With a perl script, it's the same as a standard CGI script [microsoft.com] as described on MSDN. Look for the example \FPSDK\Files\WebBot\wbtest4 in the SDK. If you prefer to use a DLL or shared library, use the BeginWebBotExpand macro [microsoft.com] which lets you access the bot attributes. In either case, you're going to build a BTL file [microsoft.com] and call the webbot from HTML [microsoft.com] like:
The SDK describes the four ways a webbot can activate [microsoft.com]. Try to test things client-side first, it's a lot easier. If your webbot fails it will just insert a generic [FrontPage Component name] on the page. Doublecheck the logs in _vti_pvt for the logs, to get hint why things are failing.
It's oldschool, it works, and it's a simple variant on CGI scripting. Again, for simple things like navigation bars it's a heck of a lot easier to use a design-time dynamic control (client-side webbot, DTC, or add-in). I strongly recommend you consider those instead.
Re: Reply if you're interested in that topic (Score:1)
I was just trying to add a hit counter and was modestly surprised that I could not find the syntax documented. I then became astounded at Adelphia's refusal (or, more likely, inability) to explain why they supported FPSE but not cgi scripting when they were running Apache under Red Hat. (That discussion logically followed when they could not point me to resources either.)
Anyway, the broken hit counter is here [adelphia.net]. Web searches turn up similar problems, but none that I could understan
No. (Score:3, Informative)
No.
Get. Out. (Score:2)
Frontpage Express (Score:2)
Cable (Score:2)
It sucks to have to pay more, but you could always find a webhost with cheap plans [infexion.net].
Profit (Score:2)
2) ????
3) Profit!
Seriously, I have quite a bit of experience in MS Web Dev land. Stay clear of the FP extensions. If you are on IIS, use ASP or ASP.NET. If you are running on Unix PHP will probably be available and is the most widely supported (read: you will be able to find examples of what you want to do online) web scripting language out there. Also, give Ruby on Rails a try.
You *could* pay for frontpage to work, but... (Score:3, Informative)
(My experience: I run a lightly used download site there along with a personal bookmark synchronization php/mysql app to share my mozilla bookmarks between machines. I've spent just under $1.50 for credit card fees, transfer and disk space since October.)
Re:You *could* pay for frontpage to work, but... (Score:2)
Lock-in (Score:1)
Is this something you really want to do?