Closed (fixed)
Project:
Field formatter settings
Version:
7.x-1.x-dev
Component:
Code
Priority:
Major
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
5 May 2012 at 03:36 UTC
Updated:
8 Feb 2014 at 09:18 UTC
Jump to comment: Most recent
Comments
Comment #1
swentel commentedI agree with that. Field UI should be able to be disabled on production.
Comment #2
andrewmacpherson commented+1 for removing dependency.
Comment #3
osopolarThis is critical because it can break a whole site. Field UI will be disabled by the Admin-Menu-Entry "disable developer modules". Having features with field_formatter_settings dependencies will disable these features without confirmation, because of its field_ui dependency.
+ Patch fixes the problem.
Comment #4
havran commentedI had same experience on my live site today. +1 for this patch.
Comment #5
dave reidI think this makes sense, but nothing in this module actually works without Field UI or Views UI, so it's an odd situation because modules depend on this one to allow them to be configured, but then once you have everything set up, you don't really need this module at all, which then, why would any of the modules need to require this module? Maybe I'm overthinking it.
Committed #1 to 7.x-1.x Thanks everyone!
http://drupalcode.org/project/field_formatter_settings.git/commit/42403fa
Comment #7
theunraveler commentedJust an idea, but maybe it would make sense to rename this module "Field Formatter Settings UI", to sort of match the idea that this module provides a UI to an API that continues to exist without this module enabled. Much like field/field_ui or views/views_ui.
Comment #8
lmeurs commentedWhen using Admin menu's Disable developer modules, settings done by Field multiple limit (which depends on Field formatter settings) were ignored. This dependency patch fixed it, thanks a lot!