I’m trying to do a simple form on a contact page which has Name/Email/Comments in the form.
I’ve set up FTG and set the form settinging to ‘POST’ in FW. The problem is that when I go to publish I get the following: One or more HTML files which do not not belong to this site will be overwritten. Do you want to continue’ A
It’s probably because you are publishing to a site folder with the same page file name already published from a previous version of the site. I.e. you have re-saved (Save as…) your original Freeway file as a different version or you are woking from a new file.
It won’t hurt to go ahead if the previous version still exists, as you can always re publish that, with the same warning appearing, if the need arises.
Colin
On 7 Feb 2011, at 09:52, Gray Owl wrote:
I’ve set up FTG and set the form settinging to ‘POST’ in FW. The problem is that when I go to publish I get the following: One or more HTML files which do not not belong to this site will be overwritten. Do you want to continue’ A
At a guess, it’s because by adding FTG content you have changed the the file type from html to php. A comment from Softpress (who read these posts) would be welcome.
Colin
On 7 Feb 2011, at 10:49, Gray Owl wrote:
Hi Colin
What I cant understand is that the basic design of the page was done last week. Only the form elements were added this morning?
At a guess, it’s because by adding FTG content you have changed the the file type from html to php. A comment from Softpress (who read these posts) would be welcome.
Colin
Hi Colin
I’ve never had this problem before with FTG & FW. I’ve got 2 forms up on other sites that are working fine.
I don’t think FTG is at fault here. Check in the Document Setup dialog
for the current value of the Site Folder option. In fact, just change
it to a new empty folder. Publish. You should not get this error again.
Walter
On Feb 7, 2011, at 6:10 AM, Gray Owl wrote:
On 7 Feb 2011, 9:55 am, ColinJA wrote:
At a guess, it’s because by adding FTG content you have changed the
the file type from html to php. A comment from Softpress (who read
these posts) would be welcome.
Colin
Hi Colin
I’ve never had this problem before with FTG & FW. I’ve got 2 forms
up on other sites that are working fine.
One of the HUGE pluses about using the PHPFF action is that you can reuse a form a zillion times over.
Once built, a standard form constructed (in a table with the action applied preferably) can be copied/pasted from one site to another with only minor alterations to text required.
This will save you tons of time and you never have to leave FW to do it.
True Dave, but the biggest reason why people choose FTG over the PHP Feedback Form action is because the email sent to you is just awful in regards to formatting. It feels cheap, it feels like everything is just thrown together, and on a big form it’s hard to dissect the results.
In the examples used on the action sites they use three or so fields, but imagine submitting a form that has 25 fields or even 50 fields. It makes it harder for your client to understand what exactly they’re getting.
I know recently I tried PHPFF and while it worked I was disappointed with the email sent to me as my client wanted a better and organized way for them to easily pull out the information they wanted.
Plus you’re also limited on how many people it can be sent to, you don’t get to insert what browser they were using nor the time that they sent it, plus you can’t customize the email the way that you want. Sure PHPFF is quick, fast, and easy to use but that’s just in the form creation and not in the options you’d expect and that’s why people use FTG. Same goes for easiBase forms to as you can’t customize the email.
An obviously superior product FTG is by focusing solely on making form scripts that work, are customized to your liking in all aspects from unique form field type validation to customizable emails, and I will say that it is totally worth the money. Plus the support is unbelievable. They wrote me back on Super Bowl Sunday during the game. Impressive.
Sure - all points noted but the original question was about a simple 3 field form that doesn’t require any bells and whistles. A 2 min job with PHPFF.
As far as formatting email output from the form - sure it is a bit basic but it is doable - especially for a guy with your skills.
What I normally do in a circumstance like that is use PHPFF to create the ‘basic’ handler, the whatever-go file, then open it in BBEdit do the mods and then use the customised version set as the target Post in Page>Form setup and delete the action from the page. Voila - custom form handler.
I don’t think FTG is at fault here. Check in the Document Setup dialog
for the current value of the Site Folder option. In fact, just change
it to a new empty folder. Publish. You should not get this error again.
Walter
Hi Walter
Sorry I don’t understand. Where’s the ‘Site Folder’ option within the Document Setup.
Right in the middle of the dialog on the Document tab. It says Site
folder: (path to your site folder) and right underneath that there’s a
Select button which lets you choose a different folder.
Walter
On Feb 7, 2011, at 3:14 PM, Gray Owl wrote:
On 7 Feb 2011, 12:32 pm, waltd wrote:
I don’t think FTG is at fault here. Check in the Document Setup
dialog
for the current value of the Site Folder option. In fact, just change
it to a new empty folder. Publish. You should not get this error
again.
Walter
Hi Walter
Sorry I don’t understand. Where’s the ‘Site Folder’ option within
the Document Setup.
@Dave - My interest hasn’t perked enough to dig into the outputted file from PHPFF. I do agree, as I stated, that the examples use just a couple of fields which I would agree works for this posting.
Come to think of it, I’m not necessarily sure how Tim would expand the processing of the form formatting within the action itself considering how forms vary both in content and setup.
I guess that is why there is a more commercial alternative in FTG.
What I normally do in a circumstance like that is use PHPFF to create the ‘basic’ handler, the whatever-go file, then open it in BBEdit do the mods and then use the customised version set as the target Post in Page>Form setup and delete the action from the page. Voila - custom form handler.
D
Dave, Can you point to a website where I can read up on the customization part so I can Voila too?