Order UI contains a dependency on Field UI in the .info file. This seems unnecessary.
We don't use Field UI on production environments, but users should be able to view their own orders.

As far as I can see, this dependency can be safely removed.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

BarisW’s picture

Status: Active » Needs review
FileSize
470 bytes
rszrama’s picture

Category: Bug report » Task
BarisW’s picture

This also goes for Product UI. Not need to require Field UI.

rszrama’s picture

Issue tags: +sprint

Curious. Looks like my tag didn't take. : P

ptmkenny’s picture

Status: Needs review » Reviewed & tested by the community

This works for me. It doesn't make sense to have field_ui enabled on production.

rszrama’s picture

Status: Reviewed & tested by the community » Postponed (maintainer needs more info)

Even with this patch, there are other modules that depend on the Field UI module. The problem is the Commerce related UI modules end up being nigh useless without Field UI ... we don't directly invoke Field UI modules, but we do use the UI modules to add admin paths to our entity types for the Field UI module to throw the manage fields / manage display interfaces up on.

I'm not entirely comfortable with this change, though I wouldn't necessarily rule it out for the future.

bojanz’s picture

Status: Postponed (maintainer needs more info) » Closed (won't fix)

It's safe to say this won't happen in 1.x.