At wits end MS Publisher Web Form & Mapping a Network Location

[Sage]

Hello, I am hoping someone can help me with this........I will try and
provide the background and where I'm at.......

1. Created web pages for a web site in MS Publisher 2007 with ONE Web
Form to collect contact information.
2. GoDaddy is the hosting company who has setup the acct on an iis 6
server with Front Page Extentions
3. Can not use FTP to upload due to Web Form use
4. All links, graphics, text appear if files are upload via FTP but
the Web Form does not work
5. Am using the GoDaddy Web form tool ....details at this web page
http://help.godaddy.com/article/512?#webformmailer
6. GoDaddy web form tool requires coding and I'm at a loss to figure
this out....have spent days combing the Internet looking for help and
found this group.

In working with GoDaddy and Microsoft I continue to get conflicting
information. One GoDaddy tech says I can use the GoDaddy .asp web
form tool referenced above and another says no way since I have Pub
2007 and they won't or can't provide support on html coding to get the
script right in Publisher. They continue to send web pages to read and
try with no luck. Have not been able to map a network location with
Publisher and am still trying to get support from Microsoft to trouble
shoot this. Without the mapping of a network I can't use HTTP to
upload the files as FTP breaks the FPEx. Have since run diagnositcs
on my laptop, am now working with a hard wire to the DSL connection,
reset the 2Gateway modem so the IP addresses may get in sync. GoDaddy
says all the setting on their end are in sync and I have full access
and permission to upload directly to the host site via HTTP but can't
get a mapped network location done.....keeps telling me the folder is
wrong.

If I can get the scripting correct in Publisher with the GoDaddy web
form data so the Web Form page works so it sends the input info and
returns the user to a thank you page I will be thrilled beyond my
wildest dreams as I am quite exhausted from all of this. I choose
Publisher 2007 and GoDaddy because I don't have the thousands of
dollars to create a professonal site I would love to have but can't
right now and I need the web site to help me generate business. But I
can't do this without a network map location and seeing if the upload
via HTTP works first before I can get the scripting figured for the
web form and is if the web form will upload correctly.

Please help.....I will be so grateful. Sage

 

[DavidF]

The Publisher forms are setup by default to use FrontPage Server Extensions
as form handlers. To use FPSE you must use HTTP uploading protocol. To use
HTTP uploading protocol with IE7 and newer, or Vista or Windows7, you must
learn how to map the network drive. MSFT has managed to make the whole
process very difficult as you have discovered. Furthermore FPSE are being
deprecated and will not be available in the future, and GoDaddy's use and
support of FPSE are notoriously bad. Bottom line is you should figure out
how to set up your forms using a different form handler, and most likely the
gdform.php as per the page you linked at Godaddy *if* you are using the
Windows shared hosting account at Godaddy. If not, use a different form
handler...

Spike may be along to help you with this, and may not, but he has worked out
how to change the Publisher forms to work with GoDaddy's form handlers, and
thus let you use FTP uploading protocol, and specifically FileZilla. Read
through his posts about the subject until or if he responds to your thread.
I am going to reference Google groups since MSFT has decided to drop this
newsgroup as of the first of June and this may be the only way in the future
to access the years of information provided in this group:
http://groups.google.com/group/micr...sign&q=Spike+php+forms&qt_g=Search+this+group

If those links don't help try a different search for Spike's information
about how to use PHP form handlers with Godaddy. This is a better investment
of your time than trying to figure out how to get the FPSE working correctly
and how to map your network drive.

DavidF

 

[Sage]

The Publisher forms are setup by default to use FrontPage Server Extensions
as form handlers. To use FPSE you must use HTTP uploading protocol. To use
HTTP uploading protocol with IE7 and newer, or Vista or Windows7, you must
learn how to map the network drive. MSFT has managed to make the whole
process very difficult as you have discovered. Furthermore FPSE are being
deprecated and will not be available in the future, and GoDaddy's use and
support of FPSE are notoriously bad. Bottom line is you should figure out
how to set up your forms using a different form handler, and most likely the
gdform.php as per the page you linked at Godaddy *if* you are using the
Windows shared hosting account at Godaddy. If not, use a different form
handler...

Spike may be along to help you with this, and may not, but he has worked out
how to change the Publisher forms to work with GoDaddy's form handlers, and
thus let you use FTP uploading protocol, and specifically FileZilla. Read
through his posts about the subject until or if he responds to your thread.
I am going to reference Google groups since MSFT has decided to drop this
newsgroup as of the first of June and this may be the only way in the future
to access the years of information provided in this group:http://groups.google.com/group/microsoft.public.publisher.webdesign/s...

If those links don't help try a different search for Spike's information
about how to use PHP form handlers with Godaddy. This is a better investment
of your time than trying to figure out how to get the FPSE working correctly
and how to map your network drive.

DavidF










- Show quoted text -

David, thank you for this quick reply. I did spend last night going
through prior posts. Did pick up a few bits of good info related to
the form properties in publisher. I did not catch anything on the HTTP
upload that would help me at the moment so I will keep checking back
here and digging further into prior posts for more input. I will
replace the .asp GoDaddy form handler that the one GoDaddy Tech
recommended with the .php. I am using Windows Shared Hosting w/
GoDaddy.

I suppose this means I will have to rework the web content page for
this new way of creating the web form. When I first contacted GoDaddy
I asked them if there were any concerns or issues I needed to consider
in choosing Publisher 2007 and working with web hosting to do a basic/
simple web site and nothing of the incredible frustrating and time
consuming issues like iis6 over iis 7, FPSE, FPT over HTTP or form
handlers were NEVER hinted to or mentioned. I should have done more
research but I had Publisher and afterall it was Microsoft......what a
lesson this has turned out to be. I feel like I am drowning and may
not be able to scceed here after the last several months of putting
together this simple web site. I am now working through what I wanted
to avoid as I do not have the skill set or time to devote to this but
now I have no other options but to work this through and hope for
success.

If I can just get the site up with the content and minimal redesign
with the web contact form and have that work that will help me in a
very big for the short term. Many thanks for this help and I will keep
checking back.

Again, my deepest thanks.

Sage

 

[DavidF]

GoDaddy didn't really mislead you...it is relatively easy to create a
simple, small and *static* website with Publisher. The problems you are
having are with the dynamic forms which require server side scripting in
order to work. Forms have always been one of the more challenging parts of
using Publisher webs...especially since many web hosts have quit supporting
FPSE and since the introduction of IE7 which meant that you could no longer
use HTTP uploading protocol directly from the Publisher web publication. Now
if you want to use HTTP you need to first map a network drive and then
publish your web files and use Windows Explorer to HTTP your files.
Unfortunately MSFT has never been very helpful in even telling people that
they had to have FPSE enabled in order for the forms to work, or giving
adequate directions of how to do HTTP uploading use a mapped network drive.
And given the FPSE are being deprecated, it doesn't make a lot of sense to
try to figure it out now...in my opinion.

Reference: Prepare, publish, and maintain your Publisher Web site:
http://office.microsoft.com/en-us/publisher/HA100947601033.aspx
Down under "Publish a Web site by using FTP" expand the + sign by how and it
gives you some directions on how to map a drive for FTP. Basically it is the
same except substitute http for ftp....

The thing to remember is in the form properties dialog for your form you
will select the option to use "an ISP Program" and then input the server
path and name of the form program....the php forms program in your case.
Note also that usually you have to actually publish the form in order to
test it...it won't work from your local computer.

Here is a link to more about the Publisher forms:
http://office.microsoft.com/en-us/publisher/CH063576891033.aspx

I hope that Spike can come along as he has given specific directions as to
how to use the php form handlers on Godaddy...that is why I suggested
seeking out his posts on the subject.

Finally, you do know that not only is MSFT dropping this newsgroup as of the
first of the month, but also they are deprecating the web building
functionality in Publisher 2010. You will be able to open and manage
existing web publications, but they are phasing it out... Since you are just
now building your site, perhaps you should look at using Serif Web Plus...it
works much as Publisher and has a much easier form setup. Check it out..

DavidF

The Publisher forms are setup by default to use FrontPage Server
Extensions
as form handlers. To use FPSE you must use HTTP uploading protocol. To use
HTTP uploading protocol with IE7 and newer, or Vista or Windows7, you must
learn how to map the network drive. MSFT has managed to make the whole
process very difficult as you have discovered. Furthermore FPSE are being
deprecated and will not be available in the future, and GoDaddy's use and
support of FPSE are notoriously bad. Bottom line is you should figure out
how to set up your forms using a different form handler, and most likely
the
gdform.php as per the page you linked at Godaddy *if* you are using the
Windows shared hosting account at Godaddy. If not, use a different form
handler...

Spike may be along to help you with this, and may not, but he has worked
out
how to change the Publisher forms to work with GoDaddy's form handlers,
and
thus let you use FTP uploading protocol, and specifically FileZilla. Read
through his posts about the subject until or if he responds to your
thread.
I am going to reference Google groups since MSFT has decided to drop this
newsgroup as of the first of June and this may be the only way in the
future
to access the years of information provided in this
group:http://groups.google.com/group/microsoft.public.publisher.webdesign/s...

If those links don't help try a different search for Spike's information
about how to use PHP form handlers with Godaddy. This is a better
investment
of your time than trying to figure out how to get the FPSE working
correctly
and how to map your network drive.

DavidF










- Show quoted text -

David, thank you for this quick reply. I did spend last night going
through prior posts. Did pick up a few bits of good info related to
the form properties in publisher. I did not catch anything on the HTTP
upload that would help me at the moment so I will keep checking back
here and digging further into prior posts for more input. I will
replace the .asp GoDaddy form handler that the one GoDaddy Tech
recommended with the .php. I am using Windows Shared Hosting w/
GoDaddy.

I suppose this means I will have to rework the web content page for
this new way of creating the web form. When I first contacted GoDaddy
I asked them if there were any concerns or issues I needed to consider
in choosing Publisher 2007 and working with web hosting to do a basic/
simple web site and nothing of the incredible frustrating and time
consuming issues like iis6 over iis 7, FPSE, FPT over HTTP or form
handlers were NEVER hinted to or mentioned. I should have done more
research but I had Publisher and afterall it was Microsoft......what a
lesson this has turned out to be. I feel like I am drowning and may
not be able to scceed here after the last several months of putting
together this simple web site. I am now working through what I wanted
to avoid as I do not have the skill set or time to devote to this but
now I have no other options but to work this through and hope for
success.

If I can just get the site up with the content and minimal redesign
with the web contact form and have that work that will help me in a
very big for the short term. Many thanks for this help and I will keep
checking back.

Again, my deepest thanks.

Sage

 

[Sage]

GoDaddy didn't really mislead you...it is relatively easy to create a
simple, small and *static* website with Publisher. The problems you are
having are with the dynamic forms which require server side scripting in
order to work. Forms have always been one of the more challenging parts of
using Publisher webs...especially since many web hosts have quit supporting
FPSE and since the introduction of IE7 which meant that you could no longer
use HTTP uploading protocol directly from the Publisher web publication. Now
if you want to use HTTP you need to first map a network drive and then
publish your web files and use Windows Explorer to HTTP your files.
Unfortunately MSFT has never been very helpful in even telling people that
they had to have FPSE enabled in order for the forms to work, or giving
adequate directions of how to do HTTP uploading use a mapped network drive.
And given the FPSE are being deprecated, it doesn't make a lot of sense to
try to figure it out now...in my opinion.

Reference: Prepare, publish, and maintain your Publisher Web site:http://office.microsoft.com/en-us/publisher/HA100947601033.aspx
Down under "Publish a Web site by using FTP" expand the + sign by how andit
gives you some directions on how to map a drive for FTP. Basically it is the
same except substitute http for ftp....

The thing to remember is in the form properties dialog for your form you
will select the option to use "an ISP Program" and then input the server
path and name of the form program....the php forms program in your case.
Note also that usually you have to actually publish the form in order to
test it...it won't work from your local computer.

Here is a link to more about the Publisher forms:http://office.microsoft.com/en-us/publisher/CH063576891033.aspx

I hope that Spike can come along as he has given specific directions as to
how to use the php form handlers on Godaddy...that is why I suggested
seeking out his posts on the subject.

Finally, you do know that not only is MSFT dropping this newsgroup as of the
first of the month, but also they are deprecating the web building
functionality in Publisher 2010. You will be able to open and manage
existing web publications, but they are phasing it out... Since you are just
now building your site, perhaps you should look at using Serif Web Plus....it
works much as Publisher and has a much easier form setup. Check it out..

DavidF







David, thank you for this quick reply. I did spend last night going
through prior posts. Did pick up a few bits of good info related to
the form properties in publisher. I did not catch anything on the HTTP
upload that would help me at the moment so I will keep checking back
here and digging further into prior posts for more input.  I will
replace the .asp GoDaddy form handler that the one GoDaddy Tech
recommended with the .php.  I am using Windows Shared Hosting w/
GoDaddy.

I suppose this means I will have to rework the web content page for
this new way of creating the web form. When I first contacted GoDaddy
I asked them if there were any concerns or issues I needed to consider
in choosing Publisher 2007 and working with web hosting to do a basic/
simple web site and nothing of the incredible frustrating and time
consuming issues like iis6 over iis 7, FPSE, FPT over HTTP or form
handlers were NEVER hinted to or mentioned. I should have done more
research but I had Publisher and afterall it was Microsoft......what a
lesson this has turned out to be.   I feel like I am drowning and may
not be able to scceed here after the last several months of putting
together this simple web site. I am now working through what I wanted
to avoid as I do not have the skill set or time to devote to this but
now I have no other options but to work this through and hope for
success.

If I can just get the site up with the content and minimal redesign
with the web contact form and have that work that will help me in a
very big for the short term. Many thanks for this help and I will keep
checking back.

Again, my deepest thanks.

Sage- Hide quoted text -

- Show quoted text -

Hello David, I did search the prior postings as you suggested and
have not come across a more detailed version of the php web form
handler or mapping a network location but did find some info that I
will call clues and will apply those. I have made multiple attempts
to "map a network location" with Vista but for some reason the wizard
steps are not creating the network location and GoDaddy has confirmed
that my settings are correct and I have full access and permissions to
the host site. So I don't know what is preventing the mapping at this
stage......so far this has not been a simple easy process since I
began the efforts to upload and host.

Do you know anything about Web Folders and software update at this MS
web page http://support.microsoft.com/kb/907306
I have not downloaded this update yet.........would like to try and
find out more about before the lights go out on this forum.

I have already reworked the Web Form-Contact Page on what I think I
understand. I inserted the php code using the Publisher HTML fragment
feature. This may or may not be correct as I have yet to be able to
input a setting that states I'm using an ISP feature for this so
perhaps using the HTML fragment feature upsing php is not correct.

The MS web page you reference I have read many times and applied the
info located there with mixed success http://office.microsoft.com/en-us/publisher/HA100947601033.aspx

Since starting this exchange on the forum I am now "well aware" of the
limitations of using Publisher for a web site and hosting.
Unfortunately, it took days of research and finding this info in
forums to discover these costly and frustrating limitations. I have
to ask the question why the forums and not Microsoft and GoDaddy could
not provide this info on the front end?? But to ask this question is
truly a waste of time and resouces. For the short term I have to try
and get this current site hosted and functional with the web form.

I do hope Spike comes along or if there is anyone else who may have
those steps you have referred to on mapping a network and using php. I
made note of the other resource you mentioned for web creation and
will check it out. Some of those apps may limit the number of pages or
certain functionality which I would have to factor into the exisiting
content I created for in Publisher. So that will take some planning
and thinking. I certainly will not move to another app without further
research that has been prompted by this experience.

I do greatly appreciate the information you have provided...I honestly
do. It has helped and if Spike or anyone else can offer move nfo
before the lights go out on this forum then I will be one lucky
person.

Where I'm at now is getting the Vista network mapping to work and
setting up the php correctly for the web form.......but if I use php
then I can use FileZilla and not have to be concerned with Vista
nework mapping only learning File Zilla and then cross my fingers that
I can work out all the things that will pop-up.

Sincerely,
Sage

 

[Spike]

Sage

I am presently using GoDaddy and PHP mailers. I do not use FPSE. I am
using forms made in publisher utilizing PHP mailers and GoDaddys CGI mailers
(both work fine). I can not help you with the mapping of network drives for
FPSE. I can give you directions on suing the PHP mailers using the FTP
process.

A point of making things on here easier for us. Please post your replies
at the beginning of the thread rather than at the end. Much easier to
follow the time line of posts.
====================
Here are general instructions for GoDaddy form mail using the FTP process to
post
====================

CGI Mail form
If your ISP supports cgi and has a form handling program then a form created
in publisher will function using FTP upload rather than front page server
extensions to upload the pages.

You must tell the server what e mail address you want the form results sent
to. Some ISP's are different than others. Check with the ISP help section
on handling forms for that information.

Locate the cgi form handler file on the server. It is probably in the cgi
or cgi-bin folder. Again ISP's are not all the same.

For example, if the form handler is in the cgi folder and it is named
myform.cgi then the path for the handler in publisher will be "
/cgi/myform.cgi " without the quotes.


In publisher create a page for your form and build the form.
In the form properties window select "Use a program from my ISP"
In the action section insert the path you discovered above. Example for
godaddy.com is " /cgi/gdform.cgi " without the quotes.

From method is Post

In the hidden fields window: enter under Item "subject" no quotes an in
the item value for subject enter a subject line that you want on the form
when you receive it.


Below the subject enter "redirect" no quotes if you want have a thank you
page built and in the item value enter the path to your thank you page

Example: " /thank_you/thankyou.htm " the thankyou.htm file is located in
the thank_you folder in the root directory.
The thank you page may have a link back to the page where you came from or
any where else you so desire or an auto redirect script with a delay.
The auto redirect script is inserted using the HTML fragment function and
looks like:

<meta http-equiv="Refresh" content="4; url=/index.htm">

In this case the time delay is 4 seconds and the page that will come up is
the index.htm.

*********************
Post back if you need more on this
*********************

Spike

 

[Sage]

Hello Spike, I'm sorry for not following forum protocal and starting
replies at the top of the tread.......I have not spent a lot of time
in forums until recently. It is amazing this forum will be closed
since it reallys appears to be providing a valuable service to
people. Your reply is very easy to follow and understand.......will
you marry me? Ok...think about it..... we have til June 1st.......and
I really do know how to cook.

When you say you have no problems with GoDaddy and PHPmailers and
don't use FPSE then you avoid network mapping and can use FTP to
upload and have the web form work.

Questions as they related to Publisher 2007...................

- So you don't have to use iis 6 Windows server? In fact, iis 7 would
be ideal?
- Vista Op Sys does not impact anything?
- What browsers shun or shy away from Publisher 2007 web pages? Only
talking about Pub 2007.
- With FPSE out of the picture then the fact it is breathing its'
last breath DOES THIS impact the continued use of Publisher using cgi
or even php (at this point in time)?
- Does it make a difference which FTP client is used to upload if
using Publisher form tools and cgi or php?

I will be moving out of Publisher as soon as I can ....but......the
answeres to the above questions will help me understand what the short
term use may be like.

Now, having asked the above questions and looking at what I had done
to date with recent input from this forum and ongoing calls to GoDaddy
here is where I'm at...................

1. I copied the PHP script from this web page http://help.godaddy.com/article/512?#gdform
provided by GoDaddy and inserted it into an HTML fragment box on the
Publisher page.
2. Next, I studied the script and added a couple of more fields and
used the web preview feature to see if what I was doing worked....it
did.
3. When I first created the contact form I used all the Publisher
features and forms tools which included working and setting up the
form properties. I spent some hours moving things around lining things
up, etc. I really loved the way the page look and flowed. When I got
into the hosting efforts a GoDaddy Tech told me I could not use the
Publisher form I created as it would not work. Stunned and amazed with
no other place to go.....I took this input and next went with asp as
that was recommended.......but when I called with a question I was
told I could not use asp due to the server I had form my hosting acct
on. Keep in mind I have been following GoD's lead on all of this.
So....back I go and redid everything with PHP.....and called again
with a question about inserting an email address....was told then that
I should be using asp......needless to say I am ready for a nice
bottle or two of really nice red wine.Have you ever heard of Cameron
Huges wine....love it.
4. I have put the wine on hold until I get the site up and
functioning......so......I explained to the GoDaddy Tech what I had
been doing and she put me on hold, came back and said I was good to go
with the PHP (and you have just confirmed this).
5. My question about inserting an email in the PHP script was answered
by GoD with "it was not required as the script as it is written goes
out to the web hosing acct and looks for the one that is on
file".....which the GoD tech confirmed the email address was correctly
in place. I recall reading in one of your prior posting that using PHP
is good because would be snoopers can not snatch email addresses from
from the script.
6. I don't like the look of the GoD PHP form handler. I don't have
enough html experience or time right now to rework it.....and that red
bottle of wine is waiting for me....but then if you agree to marry me
then I would never keep you waiting.......sorry, got off on a
tangent.....and I have to get my site up so I can focus on my
business.

If you are still with me on this.......which I really hope you
are......I will be using PHP that GoD has pointed me to. I'm really
burned out right now. If you can please find the time to provide
your input on this that will be a huge help to me. If I use PHP do I
still have to use FPSE and mapping a network location with Vista or
can I use a third party FTP client like FileZilla that I have seen
recommended quite a bit. I know you can not help on the network
mapping but perhaps using the PHP will remove this hurdle.

Thank you in advance for any help and please forgive my lack of
protocol in using forums.

Sincerely,
Sage

 

[MAURH]

Better give this girl an answer to her proposal before June 1st Spike...red
wine and a good cook!...you won't get an offer like that in the new Forum

Maureen



Hello Spike, I'm sorry for not following forum protocal and starting
replies at the top of the tread.......I have not spent a lot of time
in forums until recently. It is amazing this forum will be closed
since it reallys appears to be providing a valuable service to
people. Your reply is very easy to follow and understand.......will
you marry me? Ok...think about it..... we have til June 1st.......and
I really do know how to cook.

When you say you have no problems with GoDaddy and PHPmailers and
don't use FPSE then you avoid network mapping and can use FTP to
upload and have the web form work.

Questions as they related to Publisher 2007...................

- So you don't have to use iis 6 Windows server? In fact, iis 7 would
be ideal?
- Vista Op Sys does not impact anything?
- What browsers shun or shy away from Publisher 2007 web pages? Only
talking about Pub 2007.
- With FPSE out of the picture then the fact it is breathing its'
last breath DOES THIS impact the continued use of Publisher using cgi
or even php (at this point in time)?
- Does it make a difference which FTP client is used to upload if
using Publisher form tools and cgi or php?

I will be moving out of Publisher as soon as I can ....but......the
answeres to the above questions will help me understand what the short
term use may be like.

Now, having asked the above questions and looking at what I had done
to date with recent input from this forum and ongoing calls to GoDaddy
here is where I'm at...................

1. I copied the PHP script from this web page
http://help.godaddy.com/article/512?#gdform
provided by GoDaddy and inserted it into an HTML fragment box on the
Publisher page.
2. Next, I studied the script and added a couple of more fields and
used the web preview feature to see if what I was doing worked....it
did.
3. When I first created the contact form I used all the Publisher
features and forms tools which included working and setting up the
form properties. I spent some hours moving things around lining things
up, etc. I really loved the way the page look and flowed. When I got
into the hosting efforts a GoDaddy Tech told me I could not use the
Publisher form I created as it would not work. Stunned and amazed with
no other place to go.....I took this input and next went with asp as
that was recommended.......but when I called with a question I was
told I could not use asp due to the server I had form my hosting acct
on. Keep in mind I have been following GoD's lead on all of this.
So....back I go and redid everything with PHP.....and called again
with a question about inserting an email address....was told then that
I should be using asp......needless to say I am ready for a nice
bottle or two of really nice red wine.Have you ever heard of Cameron
Huges wine....love it.
4. I have put the wine on hold until I get the site up and
functioning......so......I explained to the GoDaddy Tech what I had
been doing and she put me on hold, came back and said I was good to go
with the PHP (and you have just confirmed this).
5. My question about inserting an email in the PHP script was answered
by GoD with "it was not required as the script as it is written goes
out to the web hosing acct and looks for the one that is on
file".....which the GoD tech confirmed the email address was correctly
in place. I recall reading in one of your prior posting that using PHP
is good because would be snoopers can not snatch email addresses from
from the script.
6. I don't like the look of the GoD PHP form handler. I don't have
enough html experience or time right now to rework it.....and that red
bottle of wine is waiting for me....but then if you agree to marry me
then I would never keep you waiting.......sorry, got off on a
tangent.....and I have to get my site up so I can focus on my
business.

If you are still with me on this.......which I really hope you
are......I will be using PHP that GoD has pointed me to. I'm really
burned out right now. If you can please find the time to provide
your input on this that will be a huge help to me. If I use PHP do I
still have to use FPSE and mapping a network location with Vista or
can I use a third party FTP client like FileZilla that I have seen
recommended quite a bit. I know you can not help on the network
mapping but perhaps using the PHP will remove this hurdle.

Thank you in advance for any help and please forgive my lack of
protocol in using forums.

Sincerely,
Sage

 

[Spike]

Sage

I should have mentioned that I use GoDaddy's Linux server which is a little
different than the windows server which I believe that you are using.

Filezilla is an excellent FTP program (GoDaddy also recommends it)
Use filezilla to look at your space on GoDaddy's sever and find the form
handler folder and look to see what form handler is installed. The folder
used to be named CGI. That is the link you will need to put in the form
properties. It will look something like /cgi/ gdform.asp

I have not looked at the windows server is a long time since I switched to
Linux.

Your questions:
Vista Op Sys ***** Does not matter

What browsers ***** If you have downloaded the latest SP for Publisher
2007 all browsers will render your pages correctly as far as I have found
out.

With FPSE out of the picture ***** Not a factor as long as you use the form
handler provided by GoDaddy

Instead of using the code from GoDaddy to build your form, I suggest that
you create your form in Publisher and fill out the form properties as I gave
you in this thread. The instructions were good for both Linux and Windows
servers that last time I checked on it. To test this, make a new 1 page
publication. Create a form, fill out the form properties and publish it.
You cannot test it from your computer, the htm files must be on the server.
I think I understood that you already recorded the email address on the
server. See http://help.godaddy.com/article/511


No need to give up on Publisher if you like what you have accomplished so
far.

When you get Filezilla installed and publish you pages to your server give
us the URL so we can give you better advise on adjusting things.

Spike

 

[Spike]

Maureen

I still have not taken you up on the cake!
May be heading back your way this fall again if the volcanoes are quiet and
BA is flying.


Spike

 

[MAURH]

BA are on strike at the moment Spike, so we don't need a volcano to cause
disruption, we seem to manage it all on our own But hey, you tell me when
and the cake will be ready!

 

[Sage]

Spike, I will download FileZilla and get oriented with that and
locate the file/link/path for the Publisher form properties that
enables connection between server and form. I saved the version of
Publisher where I created the contact form so I won't have to rework
that. And, it appears the redirect for the thank you page will
function fine with the Publisher html frag box. That page has as a
thank you msg and nav for continued viewing of the web site.

My next steps:
- Download FileZilla, orient myself, locate path to cgi form handler
to insert into form properties
- Insert HTML frag box for the redirect to thank you page. The script
for this box is <meta http-equiv="Refresh" content="4; url=/
index.htm">

Questions:
1. Does it matter where the Publisher html frag box appears on the
page for the redirect to the Thank You page? For example, should it
be placed below the Submit button or anywhere on the page as long as
it is out of the way? And, I use this script <meta http-
equiv="Refresh" content="4; url=/index.htm"> for the frag html
box...correct?

2. Does the host name need to be part of the cgi path? For example,
the Publisher form property would look something like this
http://ftpnamehere.com/cgi/myform.cgi

3. What drives the order of how the content from the input fields
appears in the email when received? Are there more hidden fields to
insert for this?

A concern about this is not getting this done before June 1st and
getting it all worked out before this forum turns out the
lights......in other words Spike has left the building. If I'm able to
achieve this in time I will be back with the web site url and welcome
the continued help.

BTW - Maureen, if you catch this reply please know I appreciate the
vote of confidence on my proposal
But I really suspect Spike has long been spoken for. I'm really
grateful for the help.

My best, Sage

 

[Spike]

Sage

The redirect code fragment can go anywhere on the page (as it does not show
up on the web site)
The redirect code fragment goes on the thank_you.htm page
The form page properties directs the user to your thank your page after the
submit button is pressed
The thank you page will go to wherever you direct (in the code fragment) in
4 seconds.

/cgi/ gdform.asp or what ever form handler is being used, no need for the
host name

The order for the email is alphabetical
If you want a particular order then you need to name the fields in
alpha/numerical order

Spike

 

[Sage]

Spike, I think I understand the order of things/steps to move forward
with. Another question came to mind........since there is no
validation with the input fields in Publisher does this create a
security issue for malware attack on the web site? I will have the SSL
security seal from GoDa to help secure the delivery of the content
from the web form.........I realize this does not protect from malware
attacks.........but what else do you suggest for malware attacks on
web sites to help mitigate attacks on customers/clients visiting the
site or any one web page?

BTW.......I subscribe to The Atlantic magazine and there is a very
interesting article on the Conficker computer worm. I believe the
full article is located at this url
http://www.theatlantic.com/magazine/archive/2010/06/the-enemy-within/8098/
if not, it is published in the June issue of The Atlantic. I think it
is worthwhile reading.

Many thanks.........Sage