Another really powerful point would be to implement having the option for more than one situation/scenario saved in one preset. In some situations with alternating titles or links this could be very important and ....

(maybe ... could be the start for a work-a-round on the suffering stucking "title"-problem with node types.)

Comments

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented

and here ... my "field formatting" point, mentioned on another issue, comes in again ;-) ...
because field formatting enables us to use different presets on different displays (teaser,full view, etc)

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented
Title: possibility to use cases or -if- (php) or alternatively more than one version for front/not-front etc. » Implementation of field formatting options in preset
rjay’s picture

rjay commented
Assigned: Unassigned » rjay
Category: task » feature

This is interesting, a colleague of mine actually made a very similar suggestion as well. This would definitely require further investigation, as it seems like it could be a fairly major change at this point.

I can definitely see how useful this could be. I have actually created another custom module that allows you to specify different theme settings on a per path basis, so this would be a similar idea, except using display contexts rather than paths.

I'll take a closer look and let you know what I think.

Scott J’s picture

Scott J commented

There is a Preset module made as a helper, but it looks like it has been abandoned. Still, it may have some ideas.

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented

Thanks rjay for taking into consideration,
and thanks Scott J for poiting to the Preset module. I will examine it.

Finally we should be aware of, that if it gets these three points together, than there is no need of views and ctools no more in may cases. This would be a huge step in proofing drupal 7's possibilities and much less database rows. To have the option to add html tags AND code to the field output would make the hole field management completely modular and free modifyable to any kind of use. Even for Image galleries and link list managements like Drigg. (I was thinking about developing a modul for that before)

Tell me if I can help (PHP, HTML, CSS) - I look forward to it ...
kind regards

rjay’s picture

rjay commented

Sorry for the delay in getting back to this issue. I have recently implemented some fairly significant UI changes (#1182452: UI Changes) that are related to what we've been discussing here. The field format selection has been moved from the field settings form to the "Manage display" tab for each content type. This provides the ability to select different presets for different display modes (eg. full, teaser) for different content types.

@Digidog: once you have some time to try out the new UI changes, can you let me know if they are anything like what you had in mind in your original post?

dqd’s picture

dqd
Location London | N.Y.C | Paris | Hamburg | Berlin
commented

@rjay: sorry, didn't saw the issue update on my dashboard. I don't know why. I came here by chance today. Thanks for asking. I will try it out now.

For you (and anyone else), I will test it here at our playground site: http://d7trail.maroqqo.com
Rjay, did you have any feedback on how it works or makes still sense in use with display suite?

I will come back and report soon.