P
Pete
I've read about the many causes of this problem when browsing a page with
an FP form. The solutions all seem to *require* using FP to publish the
web.
Thus far, I have always used a separate FTP client to publish, because my
FP web has lots of files and folders from old versions, and many of the
pages were auto-generated by web-builder apps. I'd rather not create a mess
on the host!
My questions are:
1. How can I tell if my Linux web host provider really has installed FP
extensions, as I requested them to do some time back?
2. Is it really impossible to get FP forms to work without publishing via
FP? I'm only talking about one page with forms! After all, a file is a
file.
3. If I *have* to publish via FP, can I put my form page into a separate FP
web and only publish that? Even if it ends up in the same domain tree on
the host?
Thanks for your help
Pete
an FP form. The solutions all seem to *require* using FP to publish the
web.
Thus far, I have always used a separate FTP client to publish, because my
FP web has lots of files and folders from old versions, and many of the
pages were auto-generated by web-builder apps. I'd rather not create a mess
on the host!
My questions are:
1. How can I tell if my Linux web host provider really has installed FP
extensions, as I requested them to do some time back?
2. Is it really impossible to get FP forms to work without publishing via
FP? I'm only talking about one page with forms! After all, a file is a
file.
3. If I *have* to publish via FP, can I put my form page into a separate FP
web and only publish that? Even if it ends up in the same domain tree on
the host?
Thanks for your help
Pete