Grillos / jquery-datatables-editable

Automatically exported from code.google.com/p/jquery-datatables-editable
0 stars 0 forks source link

_fnOnRowAdded errors when two tables on same page have different settings #19

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
What steps will reproduce the problem?
1. Create two editable data tables each different column counts
2. Add new row to second table created

What is the expected output? What do you see instead?
Expected: new row is added to table
Instead: Receive errors referencing # of values and # of columns

What version of the product are you using? On what operating system?
1.1.7 Windows 7

Attached is the v1.1.7 of the file with the proposed fix.

Original issue reported on code.google.com by chad.gra...@dominionenterprises.com on 20 May 2011 at 5:22

Attachments:

GoogleCodeExporter commented 8 years ago
Hi Chad,

I cannot reproduce this problem. I hav ecreated this example on the 
http://jquery-datatables-editable.googlecode.com/svn/trunk/issue19.html and I 
sucessfuly adding rows on bothe tables without any error. Your change is placed 
in the latest version but I have comment it out until I succeed to reproduce 
the probel. Is there a chance to show me some online example or send me 
complete code (HTML/JavaScript/CSS) in some archive so I can try it?

Thanks,
Jovan

Original comment by joc...@gmail.com on 28 May 2011 at 1:32

GoogleCodeExporter commented 8 years ago
I noticed in your example, you are not specifying the aoColumns option.  In my 
example I am specifically assigning table A to have 6 columns and table B to 
have 8.

Original comment by chad.gra...@dominionenterprises.com on 1 Jun 2011 at 1:17

GoogleCodeExporter commented 8 years ago
I have added aoColumns 5 columns in first and 4 in second table.

It still works fine.

Original comment by joc...@gmail.com on 1 Jun 2011 at 4:57

GoogleCodeExporter commented 8 years ago
I have experienced the same problem, with multiple tables (in hidden spans 
under tabs on the page).  The problem occurs when the first table rendered (by 
javascript in the browser) has fewer columns than a subsequent table that will 
be edited.  As a workaround, you can either: 1) determine which table will be 
rendered first and pad it with extra columns (not visible), or 2) create a 
dummy table with enough columns inside a hidden span, and make sure that one is 
rendered first.  But I would like to see this little bit fixed.  Thanks.

Original comment by coatesca...@gmail.com on 2 Jun 2011 at 2:18

GoogleCodeExporter commented 8 years ago
I have succeed to reproduce this problem. I will take a look what is causing it.

Thanks,
Jovan

Original comment by joc...@gmail.com on 2 Jun 2011 at 1:42

GoogleCodeExporter commented 8 years ago
Hi,

Could you please take the latest version from the demo site? I have fixed this 
problem. You are right when there are more than one table on the page setting 
for the first table are taken. 
Could you please try it again and confirm that it works fine?

Regards,
Jovan

Original comment by joc...@gmail.com on 2 Jun 2011 at 4:37

GoogleCodeExporter commented 8 years ago
It works on demo so as there is no more conversation on this issue I will 
assume that it is fixed.

Original comment by joc...@gmail.com on 17 Jun 2011 at 6:43