I second what Scott states...for many Coffee Cup users having multiple forms operating on the same site flawlessly and keeping files' relationships consistent are very easy with the new version of FB. If the form is named uniquely, it is very easy to upload the correct folder and the corresponding php file to the directory containing the page containing the form using any FTP program. Including copying and pasting using a mapped server location. Then if I need to change the form it is also easy to find.

I suggest those of you having difficulty take a look at the files and folders within the form folder, ie common, storage, etc and ask yourself do you want these folders in the root directory of the website/webpage. In addition, the php file makes sure that all of the form dependent files(graphics, results) are correctly linked by pointing towards the folder containing these files. I find the use of the (form_name).php file and folder an elegant solution to the issue of making sure all files used by a form are available and addresed properly, which allows them to work flawlessly.

The overwrite happened before the program was adding _exported. The first thing you do is (file save as) where one is saving a file called *.fb and the user has no idea that a folder will be created with that name also. Then it says, 'Do you want to overwrite existing files? Any changes made to a previous export will be lost."

Knowing this was a 1st export and not knowing it would create a whole entire folder called the same name, one can easily think just the *.fb file is being overwritten and it's safe to do so and the program pops up a warning measure about the *fb file "the existing file" because that is the only file that could have previously existed "in using the program".

The warning should have said (before the implementation of the new _exported)(and this is a moot point now that the program does that) is "A folder will be created using your *fb name and will overwrite your folder" or something like that.

But between day before yesterday or so after doing three other clients with same program, it now adds the _exported, so CoffeeCup must have realized this was an issue and changed things and is now a moot point.

The point was the needless additional folder being created and sitting in the directory as is inside of [client folder] and having to move them out before publishing and that it's easier to just add the folder to the iframe code than hassle with moving them. NOTE: with the new _exported folder, I just add that to the iframe coding and be done with it and never have to worry about moving anything. That's the whole point. Not that we're confused on how file structures work.



If anybody doesn't know already your second paragraph, they shouldn't be building websites.

Correction: "and the program must just be popping up a warning....." (thought process....not that it is doing that)

I like the Form Builder working the way it does and am having no difficulty putting the form builder files on my servers or on client servers, allowing them to operate flawlessly, even running multiple forms.

Furthermore, I don't overwrite files nor store the *.fb file on a server, though that is not a bad idea for backup. So I support the current strategy, but if it changes,I will be flexible enough to modify my "hobbyist" website building approach.

That's nice, but changing it will serve both you and I.

I repeat, I really like the way form builder works now...allowing integration on my websites that works flawlessly when one follows the directions. Great work Coffee Cup Team keep it up!

http://tricitieswebsolutions.com/work/CoffeeCup/CoffeeCup.pdf

Staff: please view PDF and consider a change.
Others using such programs: if they don't, just add the extra iframe coding (my entire point).
Those who extract and FTP the 2ndary folder: This conversation doesn't pertain to you.

Oye Vey. I just burned through 4 hours of weekend time because I didn't get the point made here (over and over) that the contents of the folder need to be extracted outside of the folder.

The instructions in WFB in step 2 should be clearer (especially for those of us with thick skulls!).

Maybe something like, "Simply upload the contents of this folder (NOT THE FOLDER ITSELF!) to your server, placing them in the same folder as the webpage the form will appear.

Aside from this problem, I really do get a lot from your product. Thanks!

There is also a button you can click that takes you right into that folder John.