Hi,
I'll put my comments below with your original text for clarity;
Chris Leeds
Contact:
http://chrisleeds.com/contact
"carlben" <(E-Mail Removed)> wrote in message
news:E8F4CB73-C18E-45DF-AD3A-(E-Mail Removed)...
> After learning about the demise of Frontpage and the uncertain future of
> Frontpage Server Extensions (FPSE), I bought Expression Web and ordered
> Jim
> Chishire's Expression Web book with the intention of converting my website
> to
> one that doesn't require FPSE. But the more I research this, the more
> confused I become about what I should do.
>
> My website (http://serenityonlinetherapy.com/) is about 35 pages and
> rather
> simple. Most pages have text, photos and a link bar. In addition, I have
> four
> forms with confirmation and validation pages in which the form data comes
> to
> me by email. I also have a sitemap. The forms and sitemap require FPSE to
> work properly.
>
> Question #1: Is it simpler and more efficient to import my website into
> Expression Web and then modify it and clean it up in Expression Web to
> eliminate the need for FPSE, or is it easier to just recreate it in
> Expression Web so I don't require FPSE?
No need to do either. Open your web in frontpage and publish it (file/
publish site) to another location on your computer (to make a good solid
copy).
then close frontpage and open EW, in EW hit file/ open site and open the
site from the location you just published it to.
that's it.
>
> Question #2: If you think I should import it, which option should I use to
> import it? I know one option is FPSE, which I think I wouldn't want to
> use,
> but there are other options, which I don't really understand. Which is the
> best way to import it for a website like mine
> (http://serenityonlinetherapy.com/).
Importing is a little understood feature. You don't need it in this case.
>
> Question #3: Obviously to eliminate the need for FPSE I will have to
> recreate my forms in Expression Web so they don't require FPSE. What is
> the
> simplest way to do this?
You would use the server side scripting that you like best and that's
supported by your hosting company's server.
FWIW; frontpage forms will continue to work in EW as long as you've got FPSE
on the server.
And, can you recommend a good book or tutorial
> specifically on the simplest way to create forms with confirmation,
> validation and email delivery of form data capabilities using Expression
> Web?
There is/ was a tutorial on this at
www.jimcosoftware.com/
also, if it's PHP I've had good luck modifying frontpage built forms to use
this PHP handler:
www.cluxa.com it's both cheap and nice.
>
> Question #4: If after all is said and done you happen to think I should
> just
> keep using the FPSE, then do I really have any need for Expression Web?
> Should I just return it to the retailer.
Well, I would continue using the FPSE if only for http:// publishing, plus
you've got forms and navigation components.
to totally get rid of your forms it's pretty straight forward, getting rid
of your nav bars is going to be more difficult, you'll have to decide what
you want to replace them with, how you'll get them onto the various pages,
(dwt, etc.) and whatnot.
If youre looking to use EW because of it's ability to write "valid"
HTML/XHTML code the link bars would have to go because they can't be made
valid.
My recomendation to people is to do what I did;
keep frontpage, load EW and use both until either you get used to working
within EW or EW matures to give you similar functionality to what you had in
FP.
If you're not sure, don't open the package, download the free EW trial and
give it a shot. If you don't like it dump it and return your unopened
retail package, if you do like it, keep the retail package. In either case
I would keep FP on my machine.
>
> As I said, I am confused as to what to do here. Thanks for any guidance
> you
> can give me.
>
> Carl
Hope that helped,
Chris
>
>
>
>
>
>
> --
> Thanks so much for your help, as always.
Similar Threads
