Most of the configuration options that were formerly located ?q=admin/node/types have been moved to ?q=admin/settings/content-types. Perhaps moving cck from ?q=admin/node/types to ?q=admin/settings/content-types as well would help for overall interface consistency.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | content.settings_0.patch | 10.34 KB | sun |
| #2 | content.settings.patch | 4.54 KB | sun |
Comments
Comment #1
sun+1 for this proposal
Comment #2
sunJust a quick step towards this goal. Drupal should provide a default local task here to allow quickly jumping back to non-cck content types.
Comment #3
sunNow we're talking! Attached patch totally integrates CCK settings into Drupal content type settings and works like a charm.
Comment #4
knowing_prophet commentedI completely agree. I was kind of suprized to see this was not already done when I first installed CCK.
Comment #5
boz commentedwell, and this seem to fix "Flexinode menus override CCK"
http://drupal.org/node/63746
Comment #6
sunCan someone confirm this patch is working?
I'm already using this patch at one of my sites without exceptions but I can not and must not confirm this patch is working. If you can, please set its status to ready to be committed, thanks.
Comment #7
CloudCuckoo commentedConfirmed - working like a charm for me too. Thanks for this.
Comment #8
venkat-rk commentedSubscribing to track
Comment #9
sunThanks for replying. The old location is somewhat disturbing - JonBob, could you please... :)
Comment #10
sunSorry, this is not yet usable. I'm using this on a productive site now and there are some heavy usability gaps we have to fix first. (Local tasks are disappearing, missing action links below type/field listings and so on)
Comment #11
sunDisappearing local task menus weren't related to CCK and are fixed in Drupal 4.7 CVS.
However, when submitting any content type edit form the user gets redirected to the common settings page for the edited content type. I've to investigate how custom destinations can be added to those forms now.
Comment #12
karens commentedI'm inclined to mark this won't fix because it's a complicated change that impacts lots of other things, including other contributed modules, and the locations are changed in 5.x already, so this only affects 4.7.
If you disagree you can re-open and discuss this.