| User |
Post |
|
10:20 pm January 4, 2013
|
|
MO
|
|
|
|
|
|
Guest
|
|
|
|
|
|
|
My table has three columns and no preset rows because people will be adding as many as they need. If only one row is added, the display shows three columns and three rows, with “on” repeated three times in the first column and nothing in the next two.
If I go back to edit my form, I see my three columns but instead of one row it shows three messed-up rows. The first row shows whatever was in the first input column, repeated three times across the row, the second does the same with the second one, etc.
If it's more than one row, everything behaves as expected.
|
|
|
10:03 pm January 20, 2013
|
|
MikeGriffiths
|
|
|
|
|
|
New Member
|
|
posts 1
|
|
|
|
|
I am having this same issue.
|
|
|
12:39 am February 11, 2013
|
|
WendyPorter
|
|
|
|
|
|
Member
|
|
posts 9
|
|
|
|
|
Same issue here. The $_POST[item-meta][field-id] is not consistent (one-dimensional array when only one row versus two-dimensional array when there are more than 2 rows).
Any idea how this can be fixed?
Thanks.
|
|
|
5:18 pm February 24, 2013
|
|
Top Quark
|
|
|
Barrie, ON
|
|
|
|
|
Member
|
|
posts 177
|
|

|
|
|
|
Hi all,
The issue has been resolved with Formidable Plus 1.1.8.
I'm very sorry for the length of time it took to get this resolved.
Trevor
|
|
|
5:14 pm March 5, 2013
|
|
WendyPorter
|
|
|
|
|
|
Member
|
|
posts 9
|
|
|
|
|
Hi Trevor,
I decided to install the new Formidable Plus version and remove the fixes I had written for this problem and the delete_row issue. However, that spoof fix you put in place doesn't seem to work perfectly. I received the following error:
Fatal error: Cannot unset string offsets in /home/motio409/public_html/mskhealthprofiles.com/wp-content/plugins/formidable-plus/classes/helpers/FrmPlusEntryMetaHelper.php on line 201
This happens when one of your expected table fields ($frm_field->getAll('fi.form_id='. (int)$_POST['form_id'].' AND fi.type = “table”') is not an array. This would happen if, for example, the table in the form was conditionnaly hidden (the field would then be an empty string).
I added the following fix to FrmPlusEntryMetaHelper::get_rid_of_spoofs ->
foreach ($spoofed_field_ids as $field_id){
if(is_array($_POST['item_meta'][$field_id])) {
unset($_POST['item_meta'][$field_id]['spoof']);
}
}
It seems to work but I'd like you to validate that this won't break stuff elsewhere.
Thanks,
Phil
|
|
|
3:38 pm March 7, 2013
|
|
Top Quark
|
|
|
Barrie, ON
|
|
|
|
|
Member
|
|
posts 177
|
|

|
|
|
|
Hi Phil,
Thanks for the fix. Makes sense. I've implemented it into version 1.1.8.4, now available for download.
Cheers
Trevor
|
|
|
11:20 am March 9, 2013
|
|
WendyPorter
|
|
|
|
|
|
Member
|
|
posts 9
|
|
|
|
|
Just installed the new version. Looking good.
Thanks!
Phil
Note for potential enhancement in future version: supporting “disabled” fields in the table.
|
|
|
11:25 pm April 29, 2013
|
|
pandawill
|
|
|
|
|
|
Guest
|
|
|
|
|
|
|
Post Awaiting Approval by Forum Administrator
|
|