Posted by domesticat on December 14, 2009 at 5:36pm
10 followers
| Project: | Form |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs review |
Issue Summary
My site has quite a few custom content types. The Form module seems to work properly on the node/add/* forms for the most part, but I'm seeing two exceptions I don't understand.
node/add/subjectresource and node/add/class both link to a page that contains only "Configure form ()" - no options appear. There are options that do need to be set, as I've got fieldsets for custom breadcrumbs that appear on every nodetype.
The link from /node/add/subjectresource looks like this:
/admin/form/form-9fcc175029d530f3b7ac3dace685e5e5?destination=node%2Fadd%2Fsubjectresource
Any ideas?
Comments
#1
Seeing the same thing with my custom content types and would really like to have a solution for this. I was able to set which fieldsets to include in Vertical Tabs for one of my content types. Then I tried to do it for two other content types and am seeing "Configure form ()" with no options like you. I can return to the first content type and edit the settings on the "Configure this form" page.
It is possible that the module is only allowing you to set these options for one and only one custom content type? The trouble is that the options that were set on my first content type are not applied to other content types.
TIA for any help or suggestions anyone may have.
#2
subscribe.
#3
Ah good, it’s not just me then.
Great module, great planning, simple execution.
What I can tell you for sure is that this module DOES allow configuration of multiple custom content types but juts not some of the ones I want it to! Read on
I realise that this is all a bit experimental right now so I thought I’d add my little conundrum to the mix – it may help in further development. Here we go...
I also have several content types on my site and I use Vertical Tabs all the time to save space on the screen and to help make forms less cluttered
Like the previous caller, for most of my content types it seems to work a treat – for example the attached Content Type ‘site_page’ configures nicely – I see...
‘Configure Create Site PAGE form (site_page_node_form)’ as the title and content as per the attached screenshot - please see ‘screenshot-1-OK’ below.
HOWEVER, for THREE of my content types (and they are all REALLY similar, nothing special at all in these three compared to all those that work fine), the Form module seems unable to configure the form – the Form Title and Content Type are not recognised – I see (as jayson #1) ...
‘Configure form () ‘ as the Title
...and no Vertical Tabs options appear - please see ‘screenshot-2-NOT_OK’.
I have attached the three failing content types so as to help you help meand the rest of the community.
Thanks
#4
form module sets cache via + array(cache=TRUE). The issue there is that if cache has already been set via a module to false, the + won't take effect since the value already exists in the form.
Module that sets it to false is content.
However, in form_builder, if any sub element of the forum sets cache to true, it overrides the main cache and cache takes effects (look at the static $cache).
Module that does that is filefield, possible others.
Anyhow, so forms never get added to the cache and form module works on cache
Add
<?php$form['#cache'] = true;
?>
that to form_form_alter around where it was setting it and it'll work (but beware, setting cache to true will mess up some forms [see other issue]).
#5
See the same. Subscribing.
#6
Same here
#7
The last RC1 version seems to address this issue. Pls verify this on your installations.
#8
No patch to review.
#9
@Dave Reid: Obs sorry about wrong usage of status field.
Have done some more testing with RC1 release and it is now working on all content type I got except two. Getting closer without any intel on what is changed.
#10
As number 4 stated. $form['#cache'] = true;
I added that to this module's hook_form_alter to be able to edit my one form that was showing no options. It worked. Then I removed it and disabled the form module and the settings stuck.
Thanks
BTW, I see no RC1 version of the module under releases.
#11
I also added $form['#cache'] = true; and it fixed the problem. Thanks.
#12
Any update on this getting added to the module or some sort of permutation of this fix? I still deal with this all the time, and have to add the code back in anytime I update this module.