Depending on how the solutions are developed the back button may behave differently. Multi-part forms have this trouble in Drupal because they use the "op" action to tell what page you're on. Pageroute is likely to behave better with the back button than some others. I'd recommend being careful to test back/forward button behaviors with these solutions.
Dave
________________________________
From: support-bounces@drupal.org [mailto:support-bounces@drupal.org] On Behalf Of Jeff Beeman Sent: Thursday, September 27, 2007 12:32 PM To: support@drupal.org Subject: Re: [support] CCK - Content types with lots of fields
Good to know - this is the kind of info I'm looking to gather. Anyone else know of any caveats?
Jeff
On 9/27/07, Yves Chedemois < yched.drupal@free.fr mailto:yched.drupal@free.fr > wrote:
Also note that its been reported that sites with both many (like 40, 50 ?) cck fields *and* Views module can result in high memory consumption. Still an open issue...
Bill Fitzgerald a ecrit le 27/09/2007 17:49:
Hello, Jeff,
Three options I'd look at, in this order:
http://drupal.org/project/cck_fieldgroup_tabs
http://drupal.org/project/wizard -- this will need some development attention, but would be an amazing module to have working cleanly
http://drupal.org/project/pageroute -- this might not be your exact
use
case, because this provides a path to create multiple nodes.
Cheers,
Bill
Jeff Beeman wrote:
Does anyone have any experience or comments on creating content types with CCK that have lots of fields? I am considering it's use in a project where content types would need 30, 40, maybe even 50 fields.
If performance isn't an issue, what about UI? Are there ways to
break
node submission into several pages? The groups would be at least a good start for node submission, but it'd be nice in this case if it were a little more "wizard"-ish.
Jeff Beeman