It seems to me that the Field UI module is not actually a dependency of this module; once your fields are configured properly, the Field UI module can be disabled and things work just fine. The only reason to keep this module enabled once your fields are configured, actually, is because other modules depend on it.

So here's a patch that removes the dependency on Field UI. It may be nice to put in some help text somewhere that just says that this module will not really do anything without it though.

CommentFileSizeAuthor
field_formatter_settings-no-field_ui.patch399 bytestheunraveler
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

swentel’s picture

swentel CreditAttribution: swentel commented
Status: Active » Reviewed & tested by the community

I agree with that. Field UI should be able to be disabled on production.

andrewmacpherson’s picture

andrewmacpherson CreditAttribution: andrewmacpherson commented

+1 for removing dependency.

osopolar’s picture

osopolar
Primary language German
Location 🇩🇪 GER 🌐
CreditAttribution: osopolar commented
Category: feature » bug
Priority: Normal » Critical

This 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.

havran’s picture

havran CreditAttribution: havran commented

I had same experience on my live site today. +1 for this patch.

Dave Reid’s picture

Dave Reid
he/him
Primary language English
Location Nebraska USA
CreditAttribution: Dave Reid commented
Priority: Critical » Major
Status: Reviewed & tested by the community » Fixed

I 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

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

theunraveler’s picture

theunraveler CreditAttribution: theunraveler commented

Just 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.

lmeurs’s picture

lmeurs CreditAttribution: lmeurs commented
Issue summary: View changes

When 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!