Adding and removing attributes to STORM content types
illepic - February 20, 2009 - 19:38
| Project: | Storm |
| Version: | 6.x-1.x-dev |
| Component: | Storm Attribute |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Description
For the life of me I can't figure out how to do this:
On the "Ticket" content type in STORM, how do I remove a few extra attributes and add some of my own? I've created the attributes of course in the attributes area, but I cannot figure out how to add/remove them to the display/creation of a ticket (by user Role would be pretty sweet too!).
Please let me know if I'm missing something very basic!
#1
it doesn't seem to map directly but one alternative is to modify the code in the stormattribute.install file. then uninstall the stormattribute module. clear your drupal cache. upload your new code for the stormattribute module and re-install the stormattribute module. it's pretty easy to alter the arrays. for example i changed my Project Status to different values with the following (p.s. make sure you go through and replace all instances in the code):
<?php
$attributes['Project status'] = array(
'Quote/Grant' => 'Quote/Grant',
'Planning' => 'Planning',
'Executing' => 'Executing',
'Completed' => 'Completed'
);
$attributes['Project status search'] = array(
'Quote/Grant' => 'Quote/Grant',
'Planning' => 'Planning',
'Executing' => 'Executing',
'Completed' => 'Completed'
);
?>
Hope this helps!
#2
Oh please tell me there's something coming in UI to do this! (That is, the hiding and showing of attributes in the header)
#3
Would indeed be nice to have this in a ui...
Just started configuring STORM but I wonder why it's not all CCK based, or is it somehow?
Cheers
#4
Subscribing
#5
I ended up solving this in a very web-devy sort of way. I simply put the following in my local theme css override:
#edit-pricemode-wrapper, #edit-price-wrapper, #edit-currency-wrapper{display:none;}#6
We've decided not to continue the use of STORM due to the lack of customization options.
Your problem would have been so easy to fix if it was all CCK based.
Your workaround is a clever solution to it but I don't think it should be the way.
IMO it's not the Drupal way... yet I could be wrong :)
Cheers
#7
Marked #317517: creating a new Attribute for Project status doesn't make it available for filtering as a duplicate of this.
#8
Have just investigated this one:
The original issue has been fixed in newer versions of Drupal - adding attributes through storm attributes will make them automatically come up in the create xxx form.
The comments about showing / hiding fields can already be done by overriding the theme function.
#9
Magnity -- Does this have any relevance to the creation of new Attributes for Knowledge Base? Those new attributes / Knowledge Base types show in the filter, but any knowledge base articles / nodes created do not list. I created a separate issue about it here.
It almost appears as if Knowledge Base items could be properly tagged and parented using standard Taxonomy instead the current implementation...? Would that be feasible?
*Edited to add: Tho I like the concept of KB articles as book types...if it could be incorporated with Taxonomy as well, that would be pretty spiffy.
#10
#454412: Knowledge Base doesn't allow filtering by non-default attribute is a different issue, which seems specific to the Knowledge base part of Storm - I don't think it is related to this issue at the moment.
#11
Automatically closed -- issue fixed for 2 weeks with no activity.
#12
What version is this fixed in? I am running Storm 6.122 and still cannot figure out how to add newly created attributes. Can I only create new options for the drop downs? Or can I create whole new fields via attributes versus cck?
#13
Perhaps I misunderstood this ticket - I thought it to mean options for the dropdowns.
There isn't support for adding / removing fields.
Reopening for consideration, but I suspect it may be more viable after #293485: Integrate with CCK.
#14
Recategorising...