Certain field elements cause add/edit forms to be hidden
nicholas.alipaz - January 29, 2009 - 09:58
| Project: | CCK Fieldgroup Tabs |
| Version: | 6.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | critical |
| Assigned: | Unassigned |
| Status: | closed |
Description
| Attachment | Size |
|---|---|
| tabsissue.png | 188.86 KB |

#1
I have just installed this module and I really like what it does in the normal displaying of nodes. I have an issue however when enabling tabs in node editing.
After enabling tabs for a group in the edit area it seems that when clicking edit I get the edit page, minus any content or tabs. I simply have the title of the page and the submit buttons, nothing between those.
I have attached a screenshot for you to see what is happening.
#2
Here is the source from between the
<form>tags.#3
Anyone have any input on this? Anyone getting the same problem?
#4
Still never resolved. Anyone else experiencing this issue?
#5
I have encountered this same error, though I also noticed it affected the add form. It took me a while to figure out what exactly was happening. In my case I get the title, submission instructions, and the submit buttons. The form itself is actually there but it's completely hidden. Only one of my content types was affected though.
I created a new content type and added fields one at a time until the form was broken. It turns out that adding a datetime field with a date pop-up calender produces this bug. A datetime field that doesn't have the pop-up calender won't prevent the form from displaying. It doesn't matter if the pop-up field is in the actual tab group or not.
I smell a Javascript conflict here, which is outside of my expertise.
Version Info:
Drupal 6.13
CCK 6.x-2.4
Date 6.x- 2.3
jQuery UI 6.x-1.3
jQuery UI Tabs 6.x-1.0
Javascript Tools 6.x-1.0
#6
Moving tabs rendering to the pre_render stage seems to have solved this issue.
#7
I don't think this issue has really been solved. Now, instead of all of the form tabs being hidden, none of them are hidden. This results in all of the tabs to the right of the active tab showing up at the bottom of them form, and all of the tabs to the left of the active tab showing up on top of the form.
Slightly different behavior, but the overall issue seems to be that tabs aren't hidden correctly.
#8
k, thanks for the update.
This appears to be a JS conflict and so tricky to troubleshoot/resolve. Not clear if this is a problem in tabs or in some other module. What JS errors do you get if any?
#9
I don't see any errors. Just a warning about a function that doesn't always return a value in ui.tabs.js.
I can try to figure out if one of the other modules is causing the problem, but it's going to take a bit of time. I have a lot of them installed on this particular site.
One new thing I noticed, all content types with fieldgroup tabs are affected now, not just the ones with a date pop-up selector.
#10
Referring to a closed issue #314852: Date breaks CCK Fieldgroup Tabs , where this behaviour is also mentioned for a date field.
The solution lies with the tabs module #440098: Incompatible with jquery_update, but is also still ongoing.
It could be conflicting with a pop-up for the date field, or what I believe is more likely is a conflict with Jquery.ui module, which could load another tabs.js in its core.js. The latter is a recent dependency added to the date api.
In my case it's a date field in the edit form. Firebug shows a break error "sites/all/modules/tabs/ui.tabs.js" on line 28. Stating "$.ui.tabs is not a constructor".
UPDATE:
Just added the patch from #8 issue #440098, and it worked.
If others find the problem with the tabs.module, then this post belongs there.
#11
That patch has already been applied to the version of the tabs module I'm using. I can try downgrading as described in #440098-13: Incompatible with jquery_update which might help pinpoint the problem.
I must be seeing a new conflict resulting from upgrading so I'll likely be opening a new issue. I'll mark this one fixed once I confirm that patch works after I downgrade.
#12
I downgraded and applied the patch and can confirm that it did work. I'm seeing something else so I'll mark this as fixed and open a support request. I'm just not sure which module to make the request for, I'm guessing Tabs since it does most of the work.
#13
Automatically closed -- issue fixed for 2 weeks with no activity.