Closed (fixed)
Project:
TableField
Version:
6.x-1.1
Component:
Code
Priority:
Critical
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
9 Nov 2009 at 09:31 UTC
Updated:
27 Jun 2017 at 11:15 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
JockeL commentedThis problem seems to appear only when the "Number of values" option on the Manage fields page is set to Unlimited.
Comment #2
kevin hankens commentedHey, thanks for the report. I haven't been able to reproduce, but I have a patch that might help. It just removes the collapsibility of the fieldset. Can you try applying it and see if you can see the table fields?
Comment #3
fw_crocodile commentedHi,
I can confirm that the problem persist.
The problem appear when the "Number of values" option on the Manage fields page is different from 1. It seems the problem appear when more than one table form is used.
If you see at code of the generated page, with "Number of values" set to 1:
while with "Number of values" set to 2:
So there is something different on the "outside" container of the form's section regarding tablefield module that is different when you change the number of values settings.
Comment #4
fw_crocodile commentedmay be, just adding a fieldset container would be sufficient to eliminate the problem.
Comment #5
fw_crocodile commentedMore details:
the problem is not only related to "Number of values" option. You have to have "Number of values" option set to a value different from "1" AND a table with at least one field (not zero row and columns).
Comment #6
fw_crocodile commentedI've done some more inquiry.
I think the problem is related to the markup of the form. But I didn't found how to resolv.
But I've found another problem. It seems that there is something wrong with the
<tr>tag. The closing tag is used instead of the opening one.I've resolved the problem incrementing the index.
But this isn't enough to resolve the collapse problem.
Comment #7
kevin hankens commentedCool, thanks for all of the research on this one. I'm pretty slammed at the moment, but I'll try to do some testing soon!
Comment #8
kevin hankens commentedOut of curiosity, which browser are you using? Also, are you aggregating CSS and Javascript files?
I ran into an issue one day where I was on a site with a lot of modules and there was a strange JS error occurring. Aggregating CSS and JS files in Site Configuration -> Performance fixed it.
Comment #9
fw_crocodile commentedHi,
I'm using iceweasel (say firefox on debian) and konqueror. The same behaviour appear on both browser. Both CSS and JS optimization are turned on.
Comment #10
fw_crocodile commentedI definitely think this is related to markup and js. But I really could not found which is the problem. This happen in multiple situation related to number and type of fields you've added with the cck module to the node type. Unfortunatly this make to module unusable.
Comment #11
kevin hankens commentedI am unable to reproduce. Are you certain that you are using the latest version 6.x-1.1?
Thanks!
Comment #12
fw_crocodile commentedHi,
yes I am, but i'm using some other modules too, may be some conflict between modules. I've some modules to be updated, I will update them and then post some more details on the configuration I'm using.
Comment #13
fw_crocodile commentedHi,
I finally found where the problem was. It's not directly related to your module.
The "conflict" was with JQuery Update 6.x-2.x-dev that I need for a lightbox. I should have thinked about JQuery Update first. I will change the lightbox and remove the dependecie.
So it's definitely about js.
In the mean time, exploring your code, some idea to improve a little your module came to my mind, I will try to transform the idea in some code and eventually propose some little code change in a feature request.
Bye
Anselmo
Comment #14
vthirteen commentedsame problem here. the last version of jquery (1.3, the one in the most recent JQuery Update 6.x-2.x-dev ) is used by a bunch of modules and wysiwyg editors...
Comment #15
tchopshop commentedYes, I'm using the latest version of jquery and update and it disables most of the javascript on my page. I really would love to use this module!
Comment #16
kevin hankens commentedIn my, sparse, freetime, I've only been focusing on 7.x-2.x. Can someone suggest a patch that fixes this?
Thanks!
Comment #17
ndf commentedjquery_update 6.x-2.x-dev (2011-Apr-20) solves the problem with hanging js.
(At least with ckeditor & superfish menu)
Comment #18
lolandese commentedAs for the latest comment this seems to be fixed with a newer JQuery version. Reopen if it still occurs.