FORUMS


The Form Tools forums are no longer active, but the old posts have been archived here. Please see the Help page on how to get help / report issues.

Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
PLEASE HELP! Stuck on step 5
#1
Hi,

Please please please help! I need this to work desperately. I have a meeting with a client tomorrow and I have nothing to show them.

I have a multi page form: http://portico1.com/registration/index.php (4 pages of form, 5th being the confirmation, and 6th being the thank you page)

I go through all the verification steps fine, step 4 finds all the fields. On step 5, I smart fill, and the first page is fine, but after that, page 2-5 I get not found!

I tried going through all the suggestions, but nothing. I tried skipping, but when I go to "next step" I get what looks like a formtools page with an error in an iframe right next to the loading bar, which just hangs. Here is a screenshot. Hopefully will make sense. Please let me know what I'm doing wrong.

[Image: formtools.gif]
Reply
#2
Hi gediweb,

I'm *so* sorry I couldn't help out during the week - I have a day job, so my responses from Mon-Fri can be scattered at best. Hope the meeting with the client wasn't too bad.

Wow - that's quite the error!! The reason the page looks so wonky is that the ft_finalize_form had a serious error and automatically redirected to the main error.php page to display the problem. Because it's being loaded via Ajax in the page, the entire error.php page content is loaded into the <div> in the page. DEFINITELY a bug.

However, that's unrelated to your problem at hand. Would it be possible for you to copy the entire error message and post it here? I'd like to take a look at it to see if it's the SQL query that's the problem, or if it's caused elsewhere.

- Ben
Reply
#3
Thanks for looking at this, Ben. Here is the error (copy/paste)

Error:
Failed query in ft_finalize_form, /home3/porticoo/public_html/submit/global/code/forms.php, line 238:

CREATE TABLE ft_form_4 (

submission_id MEDIUMINT UNSIGNED NOT NULL AUTO_INCREMENT,

PRIMARY KEY(submission_id),

col_1 VARCHAR(255),

col_2 VARCHAR(255),

col_3 VARCHAR(255),

col_4 VARCHAR(255),

col_5 VARCHAR(255),

col_6 VARCHAR(255),

col_7 VARCHAR(255),

col_8 VARCHAR(255),

col_9 VARCHAR(255),

col_10 VARCHAR(255),

col_11 VARCHAR(255),

col_12 VARCHAR(255),

col_13 VARCHAR(255),

col_14 VARCHAR(255),

col_15 VARCHAR(255),

col_16 VARCHAR(255),

col_17 VARCHAR(255),

col_18 VARCHAR(255),

col_19 VARCHAR(255),

col_20 VARCHAR(255),

col_21 VARCHAR(255),

col_22 VARCHAR(255),

col_23 VARCHAR(255),

col_24 VARCHAR(255),

col_25 VARCHAR(255),

col_26 VARCHAR(255),

col_27 VARCHAR(255),

col_28 VARCHAR(255),

col_29 VARCHAR(255),

col_30 VARCHAR(255),

col_31 VARCHAR(255),

col_32 VARCHAR(255),

col_33 VARCHAR(255),

col_34 VARCHAR(255),

col_35 VARCHAR(255),

col_36 VARCHAR(255),

col_37 VARCHAR(255),

col_38 VARCHAR(255),

col_39 VARCHAR(255),

col_40 VARCHAR(255),

col_41 VARCHAR(255),

col_42 VARCHAR(255),

col_43 VARCHAR(255),

col_44 VARCHAR(255),

col_45 VARCHAR(255),

col_46 VARCHAR(255),

col_47 VARCHAR(255),

col_48 VARCHAR(255),

col_49 VARCHAR(255),

col_50 VARCHAR(255),

col_51 VARCHAR(255),

col_52 VARCHAR(255),

col_53 VARCHAR(255),

col_54 VARCHAR(255),

col_55 VARCHAR(255),

col_56 VARCHAR(255),

col_57 VARCHAR(255),

col_58 VARCHAR(255),

col_59 VARCHAR(255),

col_60 VARCHAR(255),

col_61 VARCHAR(255),

col_62 VARCHAR(255),

col_63 VARCHAR(255),

col_64 VARCHAR(255),

col_65 VARCHAR(255),

col_66 VARCHAR(255),

col_67 VARCHAR(255),

col_68 VARCHAR(255),

col_69 VARCHAR(255),

col_70 VARCHAR(255),

col_71 VARCHAR(255),

col_72 VARCHAR(255),

col_73 VARCHAR(255),

col_74 VARCHAR(255),

col_75 VARCHAR(255),

col_76 VARCHAR(255),

col_77 VARCHAR(255),

col_78 VARCHAR(255),

col_79 VARCHAR(255),

col_80 VARCHAR(255),

col_81 VARCHAR(255),

col_82 VARCHAR(255),

col_83 VARCHAR(255),

col_84 VARCHAR(255),

col_85 VARCHAR(255),

col_86 VARCHAR(255),

col_87 VARCHAR(255),

col_88 VARCHAR(255),

col_89 VARCHAR(255),

col_90 VARCHAR(255),

col_91 VARCHAR(255),

col_92 VARCHAR(255),

col_93 VARCHAR(255),

col_94 VARCHAR(255),

col_95 VARCHAR(255),

col_96 VARCHAR(255),

col_97 VARCHAR(255),

col_98 VARCHAR(255),

col_99 VARCHAR(255),

col_100 VARCHAR(255),

col_101 VARCHAR(255),

col_102 VARCHAR(255),

col_103 VARCHAR(255),

submission_date DATETIME NOT NULL,

last_modified_date DATETIME NOT NULL,

ip_address VARCHAR(15),

is_finalized ENUM('yes','no') default 'yes')

TYPE=InnoDB DEFAULT CHARSET=utf8

Debug:

Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs
Reply
#4
Ah, that last line sums up the cause pretty well:

Quote:Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs

This is a database restriction. What hosting company do you use? It may be worth dropping them a line to request they increase the permitted size of database table rows.

Unfortunately, Form Tools won't be able to create that form for you with the database restriction in place. But it should definitely handle the situation more elegantly. I've logged this as a bug, here: http://bugs.formtools.org/index.php?cmd=view&id=191

I'll be sure to address it in an upcoming release.

In the meantime... I actually ran into this very same problem for the Prague Fringe festival sometime last year. For them, I ended up to reduce the total size of fields, keeping everything as small as possible. What you could try is reducing the database field size for all those fields that don't really need 255 chars. Are some that could use 20 chars or even 5? That may reduce the total size enough to get around it.

Good luck...!

- Ben
Reply
#5
(Jan 16th, 2010, 1:43 PM)Ben Wrote: Ah, that last line sums up the cause pretty well:

Quote:Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs

This is a database restriction. What hosting company do you use? It may be worth dropping them a line to request they increase the permitted size of database table rows.

Unfortunately, Form Tools won't be able to create that form for you with the database restriction in place. But it should definitely handle the situation more elegantly. I've logged this as a bug, here: http://bugs.formtools.org/index.php?cmd=view&id=191

I'll be sure to address it in an upcoming release.

In the meantime... I actually ran into this very same problem for the Prague Fringe festival sometime last year. For them, I ended up to reduce the total size of fields, keeping everything as small as possible. What you could try is reducing the database field size for all those fields that don't really need 255 chars. Are some that could use 20 chars or even 5? That may reduce the total size enough to get around it.

Good luck...!

- Ben

Thank you Ben! That worked perfectly! Ahhh that was a weight lifted off my shoulders! Thanks again Smile
Reply
#6
how do you reduce the size of the field? Which step? i can't find the fields in the mysql database. I can't find it in any steps 1-4 either!!!

i feel so dumb and stupid right now. getting the error and can't get pass it.
Reply
#7
To change the size of the database field:

Edit the form
Click on "Fields" tab
Use the scroll bar to go to "Field Size".

To change the physical size of the field on your form (how long a text box looks) you will need to change that in your HTML form.

Hope this helps,
Alex

(Sep 30th, 2013, 4:24 AM)aningbo Wrote: how do you reduce the size of the field? Which step? i can't find the fields in the mysql database. I can't find it in any steps 1-4 either!!!

i feel so dumb and stupid right now. getting the error and can't get pass it.

Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)