Layout option: Please do not arbitrarily reorder the CCK field positions from how they are on the content type Display Fields page. Please make the assumptions that: the developer painstakingly ordered 50+ fields thusly but wants a few add'l display tweaks; that it is past midnight after a long day, and now the whole node display is screwed; and that the client was to start working with that content first thing in the AM. Not even the field groups are preserved. And, the labels all have all been disabled. Pretty much everything (everything?) about the content type Display was overwritten to an illogical default. Moreover, in spite of disabling every single Display Suite related module, clearing cache, and running update.php, the overrides remain. Having to rollback the db is never desirable.

Is there no way to preserve that CCK content type display order/settings as a default? (The Display Order module did the same thing, which prompted me to uninstall that immediately.) Or is there and I have overlooked it? Even a simple "restore" button?

Comments

jstoller’s picture

jstoller
he/him
commented

@greta_drupal:
I'm not sure exactly what behavior you're expecting. By default your CCK settings are used to display a node, unless you specifically choose to let DS takeover a specific buildmode for that content type. And if you do that, the default is for all fields to start off as disabled. You have to move each field into the region and order you want, so the order is whatever you set it to be. Am I missing something?

xtfer’s picture

xtfer commented
Status: Active » Closed (cannot reproduce)
digitalfrontiersmedia’s picture

digitalfrontiersmedia
Location Sarasota, FL
commented
Status: Closed (cannot reproduce) » Active

I think this is a reasonable request if it's possible. @jstoller, I think what she's asking for here is that instead of the DS default being that all fields to start off as disabled that they start off with the same display settings as set on the Manage Display page for a build mode prior to enabling DS. As she says, everything may have been previously setup and working fairly well until a new request requires some DS Rx (maybe simply a single change to one field). As written, enabling DS would require completely rebuilding the display settings for all the fields (possibly dozens) instead of enabling DS, choosing a new build mode that pulls the existing display settings as default and simply altering that single field's setting.

However, is it possible or is it something that would be prohibitively difficult given the order of operations when enabling DS for a display?

xtfer’s picture

xtfer commented
Status: Active » Closed (won't fix)

I should have paid more attention to this when I closed it... I don't have a problem with it, in theory, however I am unlikely to add it as a feature at this stage. I think it impacts a relatively small number of users - those with existing 6.x sites implementing DS after their site is already set up. But, 6.x is winding down development after the 6.x-2.x release as most users are now starting to move towards 7.x.

I am not sure how difficult it would be to implement, probably not too hard, so I'm welcome to a patch. In the meantime, I'm marking this as 'won't fix'.

greta_drupal’s picture

greta_drupal commented

Yes, DigitalFrontier, you (re)described the situation precisely. (Although, in all fairness, I thought that I had painted a rather good picture of the issue.)

@jstoller, you might think this an isolated case (I'd tend to disagree), but why limit DS to new installations? Same scenario could occur for D7 projects too.

xtfer’s picture

xtfer commented

@jstoller, you might think this an isolated case (I'd tend to disagree), but why limit DS to new installations? Same scenario could occur for D7 projects too.

I think that comment was directed at me...

I don't think its not a good idea.The situation you are describing, however, only really happens when you install DS after having done field configuration, which usually only happens on sites where you are adding DS after the fact, as on a clean build you'd probably just set up DS from the beginning. So it's not isolated, it's just not common, and on a branch which is declining in popularity Im disinclined to add new features currently anyway.

As for 7.x, this request is logged against 6.x, which is developed almost entirely separately from 7.x. If you want to request this feature for 7.x I suggest you open a new issue for it, perhaps linking back to this one for reference.

greta_drupal’s picture

greta_drupal commented

I posted initially when installing for D6. (I abandoned use of this module for the subject reason.) I don't know why you think that adding a module after build out is so rare. I really think through projects before I begin. But, clients make feature requests all through a project. Or, a project changes in a way that then necessitates a certain module to achieve desired result. With all due respect, I think that assuming that rarely happens is shortsighted.

I now am trying DS (for the first time) on a D7 fresh install - for a business directory. And, I can tell you that the DS implications are making me woosy. I'd really like to just get the many fields built, for the many custom content types, so that I can have client start entering some content for testing -- so that client can evaluate their needs and so I can refine the taxonomy/content types/fields...before I start building a million views. But, I know that if I simply re-order the fields in some logical way for now, that work will be overwritten by DS. And, creating the DS build modes is really slowing me down. If my field and fieldgroup order was preserved when ready to start the DS customization, it would bring some relief. [I'll open a feature request for D7.]

Just offering some site builder perspective.

digitalfrontiersmedia’s picture

digitalfrontiersmedia
Location Sarasota, FL
commented

greta, already filed request for D7: #1525684: Use Core Field Display Weights and Enabled Statuses as Initial Settings When Adding New Build/Display Mode with DS