Closed (works as designed)
Project:
Drupal core
Version:
8.0.x-dev
Component:
node system
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
6 Jun 2006 at 17:38 UTC
Updated:
29 Jul 2014 at 17:30 UTC
Jump to comment: Most recent
Comments
Comment #1
acanyone consider this?
Comment #2
acah? ah? anyone else thing this is worthy of at least commenting on? anyone? bueller?
Comment #3
marcoBauli commentedyes, this would be definitely a nice feature, still is something that none of the other core anc contributed content types have (it could be a good start though ;)
moreover, imho the whole /node/add page is a bit lousy, since it's a nude and crude list of the content-types available. No introduction text, no sorting, no theming possible! (maybe another feature request?)
you could always make your own add-content node, and try to hack the menu.module to link to your custom page. Not the best solution in terms of mainteinability, but might work...
Comment #4
jonbob commentedThis is more a core issue than a CCK issue IMO, especially now that configurable basic content types are available in core.
Comment #5
acyep good call
Comment #6
webchickThis should be as simple as adding "id" attributes to either the links or list items of something lke "add-content-content-type", and putting the page output in a themeable function. http://drupal.org/node/72003 might help.
Comment #7
acyep this is all that is needed. but from the point of view of less experienced css developers it might be nice to have a icon upload field.. i understand that this is significantly more complicated to implement but it is also significantly more user friendly for less technical developers... either way i am happy... maybe we should implement webchicks method and see if people like the idea, if so we can add upload support later. (the unique id should definately be in the list element rather than the anchor)
Comment #8
Anonymous (not verified) commentedIt will be a great feature, it will let the users easily choose a content type like Panels does with the layout icons.
Comment #9
Anonymous (not verified) commentedGreat idea, on the other hand this is something that can be incorporated in a (administrative) theme by a theme designer. You should be able to style any menu with CSS, customize in template.php, or with(in) a module.
As it appears no one has worked on this in more than three years closing for now. Please feel free to re-open if you see life or importance in this.
Someone will also have to design, or get permission, to use icon sets.
Comment #10
acFor what it is worth, I don't think you should have to modify the DOM in a template to get a unique ID on the list of content types - it should just be added as per http://drupal.org/node/67595#comment-414752. This is still an issue in D7 and I am reopening it for the 8.x branch.
Comment #11
zilla commentedwhy not just make "content types" more field able?
seems that the most simple thing is to do what fields for taxonomy did in d7: let you add an image without using some other module to achieve the effect.
in this, when i edit a content type in drupal core, the actual "content name" page would have a few fields (separate from manage fields *within* the type) so that i could add an image for the content type and from there choose to display 'throughout site' (like a thumbnail via core image handling) and/or on "node creation" pages, and so on...
themers could then extend their base themes to control display of such items (or allow for omission depending on specific theme output or wants)
Comment #12
videographics commentedThx, zilla. I love your basic premise. Here's an idea for a functional implementation...
Since we already have fields for each content type, one way to accomplish this would be to simply present the option to make a particular field 'static' for the content type it's being defined for. You would click a 'Make static within this content type' checkbox on the field configuration form and then it would present a way to enter the static value for the field. Then, that value would remain the same every time that field was displayed for that content type. These 'static' fields would then be available under the "manage displays" tab along with all of the other fields. We might also want some way of identifying these fields as static—like maybe an asterisk.
These 'static' fields could be used for icons, banners, descriptive elements, help text, or anything else that might need to remain consistent across a content type. To me, this seems like it would be an elegant and universally useful core feature that would have a minimal effect on the current interface design.
I've done this kind of thing within a theme, but themes probably aren't the best place since, out of the box, they shouldn't care about which content types you're working with. I've also done this with Computed Field by having it compute the same value regardless of where the field's being displayed, but it would be infinitely more useful to have the standard field creation interface available when doing this. I think things like Display Suite fields are also cool but they're more global in scope and don't quite have the same universal utility that this would.
(I hope I'm not co-opting this post beyond it's original intent. Hopefully, the principal of the original concept of adding static 'elements' of some sort [icons or otherwise] to a content type remains intact.)
(I think it's cool to see this issue was resurrected from a post back in '06. Some of the early comments are especially fun to see now that we've got cck in core. See #4. Back then, everyone was getting juiced about having 'configurable basic content types' in core! Long live Drupal!)
Comment #13
Anonymous (not verified) commentedIt sounds like something that could enhance the user experience for people who like eye candy.
There are modules that do something like this for example:
http://drupal.org/project/iconizer
and see also for more search results (haven't read all the results):
http://drupal.org/search/apachesolr_multisitesearch/icon?filters=ss_meta...
Considering the low traffic on this feature request, and the availability of substitute options through a module (with some modification) closing this for now as works as designed.
Please feel free to re-open if you feel the admin backend should have something like this in core. Would need to decide on which eye candy though, or if that is also a user choice? Keeping the possibility for people to customize this (which from what I read they can), while focussing for maximum usability in core admin, may be the viable option. Feel free to chime in.