Right now, Fieldable panels panes has a dependency Field UI which is a module you should be able to disable on production sites. IMHO, it's in the same category as Views UI, Rules UI and probably a couple of others in contrib as well. While I agree that without Field UI, a new bundle is pretty much worthless, you could argue the same for a new content type which would only have a title and a body.
Also, the patch over at #1618308: User interface for managing bundles does a module_exists('field_ui') for the 'Save and add fields' button.
That would make it consistent, otherwise, that line is redundant.
Patch coming up.
Comments
Comment #1
swentel commentedComment #2
merlinofchaos commentedI think we will need a module_exists('field_ui') around the code that adds the field UI based menus or we will get whitescreens.
Comment #3
swentel commentedNew patch checking on field ui module in fieldable_panels_panes_admin_menu_map()
Comment #4
dave reid#3 wasn't correct either. The end of the function contains non-field UI module related menu paths that are still safe to add. I limited it to specifically the field links that are added under 'Manage fields' and it seemed to work great. Committed to 7.x-1.x.
http://drupalcode.org/project/fieldable_panels_panes.git/commit/3d73b08
Comment #6
recidive commentedThere's still one dependency on field ui that's causing this error:
This is the line that adds the dependency:
http://cgit.drupalcode.org/fieldable_panels_panes/tree/plugins/export_ui...
Comment #7
damienmckennaAnd some tests would help ;-)
Comment #8
damienmckennaThere were a few other places that Field UI was assumed.
Comment #9
damienmckennaThe code that refers to _field_ui_bundle_admin_path() shouldn't run if Field UI isn't enabled because the "Save and continue" button will only exist on the "Add a new fieldable panels panes type" form if Field UI is enabled.
Comment #10
damienmckennaComment #12
damienmckennaCommitted.