Closed (won't fix)
Project:
Yahoo Terms
Version:
4.7.x-1.x-dev
Component:
Code
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
22 May 2007 at 18:57 UTC
Updated:
20 Oct 2010 at 23:43 UTC
I think per vocabulary settings are enough - is there a good reason why to have per content type settings on top of per vocab settings?
e. g.:
http://leech47.devseeddev.com/admin/settings/content-types/page
Comments
Comment #1
Shiny commentedPerhaps a "all content types" option would be useful?
Comment #2
Shiny commentedclosing issue from D4.7