|
Home > Archive > FrontPage Server Extensions for Windows > May 2004 > FrontPage Server Extensions - Functionality changes upon Publishing of site?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
FrontPage Server Extensions - Functionality changes upon Publishing of site?
|
|
| Eric G 2004-04-29, 8:35 am |
| Hello,
I have a smallish host that is most accommodating, customer orientated and
helpful in every possible way. Normally, they don't offer hosting with FPSE,
but have made an exception for me and installed it. They run IIS 5.0
(Windows 2000).
The problem is that after they have installed the FPSE and I've published a
site for testing - including one form-to-email - the standard error message
appears when trying to submit the form:
"FrontPage Run-Time Component Page
You have submitted a form or followed a link to a page that requires a web
server and the FrontPage Server Extensions to function properly.
This form or other FrontPage component will work correctly if you publish
this web to a web server that has the FrontPage Server Extensions installed.
Click the <Back> arrow to return to the previous page".
My host then reactivates the FPSE and my site works fine, all forms
submitted are mailed as intended. However, after I re-publish my site, the
FPSE functionality is gone and the error message is displayed anew. My host
reactivates the FPSE and everything works fine, just as intended. That is,
until next time .
Now, as my host has not previously worked with FPSE, this is a new
experience to them and they can't straight away tell what the problem might
be and/or why the system behaves the way it does, or for that matter, what
parameters must be changed to avoid this problem from happening.
Have you any idea of what's going wrong, what I, or my host, is doing wrong,
or what either of us can do to solve this problem?
I would be most grateful for any suggestions, hints or whatever, to resolve
this issue.
Best Regards,
Eric G
Stockholm, Sweden
| |
| Stefan B Rusynko 2004-04-29, 9:37 am |
| Are you publishing using FP http mode (required) or FTP mode (breaks the FP SE)
--
________________________________________
_____
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
________________________________________
_____
"Eric G" < eg1(please_remove_this_garbage)@intermar
ine.se> wrote in message news:u$p3AfeLEHA.3324@TK2MSFTNGP10.phx.gbl...
| Hello,
|
| I have a smallish host that is most accommodating, customer orientated and
| helpful in every possible way. Normally, they don't offer hosting with FPSE,
| but have made an exception for me and installed it. They run IIS 5.0
| (Windows 2000).
|
| The problem is that after they have installed the FPSE and I've published a
| site for testing - including one form-to-email - the standard error message
| appears when trying to submit the form:
|
| "FrontPage Run-Time Component Page
| You have submitted a form or followed a link to a page that requires a web
| server and the FrontPage Server Extensions to function properly.
| This form or other FrontPage component will work correctly if you publish
| this web to a web server that has the FrontPage Server Extensions installed.
| Click the <Back> arrow to return to the previous page".
|
| My host then reactivates the FPSE and my site works fine, all forms
| submitted are mailed as intended. However, after I re-publish my site, the
| FPSE functionality is gone and the error message is displayed anew. My host
| reactivates the FPSE and everything works fine, just as intended. That is,
| until next time .
|
| Now, as my host has not previously worked with FPSE, this is a new
| experience to them and they can't straight away tell what the problem might
| be and/or why the system behaves the way it does, or for that matter, what
| parameters must be changed to avoid this problem from happening.
|
| Have you any idea of what's going wrong, what I, or my host, is doing wrong,
| or what either of us can do to solve this problem?
|
| I would be most grateful for any suggestions, hints or whatever, to resolve
| this issue.
|
| Best Regards,
|
| Eric G
| Stockholm, Sweden
|
|
|
| |
| Eric G 2004-04-29, 9:37 am |
| Stefan,
Now you make me unsure, and I even I had a look just now, to once again
confirm my settings.
I, as the publisher, use the standard Publishing procedure in FP 2003, i.e.
File/Publish Site, tab Remote Web Site, and then the radio button "FTP" is
marked. However, there are 3 other alternatives available "FrontPage or
SharePoint Service", "WebDAV" and "File System".
Since the site is not going to be published to "File System" or "WebDAV",
could it possibly mean that the radio button marked "FrontPage or SharePoint
Service" should be selected, rather than the "FTP" and it's where the
problem lies - by me?
Please let me know if my deduction capability is correct., or not.
My very best regards,
Eric G
Stockholm, Sweden
| |
| Stefan B Rusynko 2004-04-29, 1:37 pm |
| If your site has the FP SE and you use FP SE tools (like FP forms) you must publish using http
- Select FrontPage or SharePoint Services and enter your URL using http://www.yoursite.com/
--
________________________________________
_____
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
________________________________________
_____
"Eric G" < eg1(please_remove_this_garbage)@intermar
ine.se> wrote in message news:%23cNMy0eLEHA.2624@TK2MSFTNGP09.phx.gbl...
| Stefan,
|
| Now you make me unsure, and I even I had a look just now, to once again
| confirm my settings.
|
| I, as the publisher, use the standard Publishing procedure in FP 2003, i.e.
| File/Publish Site, tab Remote Web Site, and then the radio button "FTP" is
| marked. However, there are 3 other alternatives available "FrontPage or
| SharePoint Service", "WebDAV" and "File System".
|
| Since the site is not going to be published to "File System" or "WebDAV",
| could it possibly mean that the radio button marked "FrontPage or SharePoint
| Service" should be selected, rather than the "FTP" and it's where the
| problem lies - by me?
|
| Please let me know if my deduction capability is correct., or not.
|
| My very best regards,
|
|
| Eric G
| Stockholm, Sweden
|
|
|
| |
| Eric G 2004-04-30, 3:34 am |
| Thank you very much Stefan, your assistance is much appreciated!
My host is now trying to figure out how to set up his side to allow me to
connect via http. Ftp connection worked fine, but apparently my host has
never set up http connections before.
Best regards,
Eric Green
Stockholm, Sweden
| |
| G Farris 2004-05-15, 3:36 am |
| I was always told if I used FTP to edit a site with FPSE activated, this would
deactivate the extensions, and even create security problems. And yet I have
done just that, and so far haven't run into this problem.
Usually they'll say after activating the server extensions, the only way to
edit is in Front Page, using the http "Publish" function, and not FTP. This
can be time consuming, because FP wants to check and re-publish the entire
site (when you may have made nothing more than a spelling correction). What's
more, after republishing, then you have to go through and fix everything that
the publish function broke - adding unwanted syntax to links is the
favorite.
So to make the odd spelling check or simple updates, I've always stuck to FTP
and text editors. FP sites still seem to work with their extensions.
Greg
| |
| Stefan B Rusynko 2004-05-15, 4:36 am |
| Any changes you make in pages are not recognized by the FP SE and eventually your SE meta files will become corrupt, causing the SE
dependent tools to fail
- plus any design time tools (includes, nav bars, etc) will also become corrupt
PS
Make sure when publishing using FP you use the changed pages only option
--
________________________________________
_____
SBR @ ENJOY (-: [ Microsoft MVP - FrontPage ]
"Warning - Using the F1 Key will not break anything!" (-;
To find the best Newsgroup for FrontPage support see:
http://www.net-sites.com/sitebuilder/newsgroups.asp
________________________________________
_____
"G Farris" <farris@nonum.com> wrote in message news:c83bum$19i3$1@biggoron.nerim.net...
| I was always told if I used FTP to edit a site with FPSE activated, this would
| deactivate the extensions, and even create security problems. And yet I have
| done just that, and so far haven't run into this problem.
|
| Usually they'll say after activating the server extensions, the only way to
| edit is in Front Page, using the http "Publish" function, and not FTP. This
| can be time consuming, because FP wants to check and re-publish the entire
| site (when you may have made nothing more than a spelling correction). What's
| more, after republishing, then you have to go through and fix everything that
| the publish function broke - adding unwanted syntax to links is the
| favorite.
|
| So to make the odd spelling check or simple updates, I've always stuck to FTP
| and text editors. FP sites still seem to work with their extensions.
|
| Greg
|
|
|
|
|
|