When I enable the node displays module the display settings for each node type are empty (all fields disabled).
It would be really helpful to import the old display configuration and put any enabled fields in the middle region.

For example if I only want to change the layout of 1 of my 15 content types the other 14 will be broken until I configure the display settings for each.

Comments

swentel’s picture

swentel commented
Status: Active » Postponed

Mmm, yeah that's a hard one, we've been bitten by this one too and we're currently not sure how to handle this well, will be something for beta 4 though.

Wimmmmm’s picture

Wimmmmm commented

I follow keyo on this!

At installation, just put
* the title in header
* core body in middle
* links, author and such in footer

Right now, after installation I'm forced to go through all content types & adjust, only to be where I was before installation...
Also, you kinda have to go though the issue cue to see it's a feature and not a bug... Please alert person installing that this is right now the way you work...

swentel’s picture

swentel commented
Category: bug » feature

Yeah, this is actually not a bug report imo, but a feature request :)

keyo’s picture

keyo commented

Also I might add that any newly created fields should be placed into the middle region. If I remember correctly they are disabled by default, which is a little confusing.

Keep up the good work, I think using this module is more maintainable than printing pieces of $node in a tpl.php. It saves my client from calling me up every time he wants a minor change. :)

Wimmmmm’s picture

Wimmmmm commented

@keyo: I follow you a bit here, not all the way.

Say you have a teaser display, a small table display, a favourites display and the full page display.
Any new fields you add, you don't want them to appear in every layout in the middle region.
I would *like* to see them appear in the full node display only.

Better: I would like to indicate that at the moment I create the new field in CCK:
Do you want to add this field to
* teaser display
* small table display
* full node display
On second thought: just skip this "better" idea, it kinda means bringin the whole management interface into CCK, and that would be over the top...

@swentel: indeed it's a feature request, hadn't noticed the category

Sinan Erdem’s picture

Sinan Erdem commented
Component: Code » ND Core

I dont know if my issue is all the same but I lose all the settings when I upgrade from beta 2 to latest dev version. It is really difficult for me to re-enter all the settings.

I reverted and I dont think I will update the module if all the settings get lost.

swentel’s picture

swentel commented

@etcetera9 it's connected in a way yes. Upgrading to the next beta will be hard for users testing the beta2 version since we completely separated ND from CCK now. Support for cck now lives in the Node displays contributions project.

swentel’s picture

swentel commented
Project: Node displays » Display Suite
Version: 6.x-1.0-beta2 » 6.x-1.x-dev
Component: ND Core » Code

Moving this to the display suite project since this is the major API now.

swentel’s picture

swentel commented
Status: Postponed » Closed (works as designed)

Ok, after a *very* long discussion, we are marking this as 'by design'. We made the rendering of the HTML smart enough to not tamper with the $content variable if there are no initial settings so you will see something pop up of your content. We are working on on a solution to clone settings and support adding a (cck / nd) field automatically in a region in one ore more build modes which is much more interesting to support than this.