I am customizing the Project Management (pm) module. When I create a new Project content type I do not need some of the fields such as price and currency for my particular application. I am concerned that if I use the Fields UI to delete them that when a new version of pm is release that I'll have problems installing it. I also worry that I might mess up the database.
I have made these fields hidden, but they still appear on the create new Project content page.
Someone suggested using Field Permissions module. Another possibility would be for me to create a new content type using just the fields that interest me. I guess a third alternative would be to uninstall pm and create my own content types. (My project management needs are not complex.)
Comments
Comment #1
d34dman commentedYou can delete them, please post an issue if you find any problems.
Comment #2
samstamport commentedSo ... If I go about deleting unused fields a future version of pm will not complain and there will be no damage to my database?
Is it common practice to delete fields while building a web site for a particular use case?
I want to make sure that I don't create a problem for myself at some later date by making these kinds of changes.
I'm trying to wrap my brain around this aspect of Drupal.
Comment #3
juliangb commented@D34dMan, just to flag that this will commit us to checking whether any field exists before trying to run any updates. Otherwise the update will fail. For example, if we removed these fields in an update.
My 2c here would be:
- if you need most of the PM fields, use pm and field permissions or something custom to hide unwanted fields
- if you want something much simpler, investigate casetracker or another module
Comment #4
samstamport commentedThanks for your help.
The Field Permissions module works, but I decided that my situation was so simple that I created a new content type for tasks and another for projects using the model of the pm modules. It works well.
Comment #5
d34dman commentedHi @juliangb valid observation, i have created an issue to track the case here #2540172: Handle deleted fields / content types provided by Drupal PM.
Since OP's original issue have been resolved. Closing this.