I'm trying to install Commerce, however this line seems to be breaking Commerce UI:

sites/all/modules/contrib/commerce/modules/payment/commerce_payment_ui.module
73: $controller = new RulesUIController();

There's no RulesUIController in Rules-7.x-1.x-dev

Cheers

Comments

aidanlis’s picture

aidanlis commented

Seems like it was introduced here: https://drupal.org/node/904978

rszrama’s picture

rszrama commented

I saw this error at one point, too, but I haven't seen it recently... If I remember right, it was because I had to introduce a dependency on rules_admin. Rules Admin defines the missing class, so the question is... why isn't Drupal picking up on it? Is it because Drupal isn't installing Rules Admin before installing Payment UI? Or is there something else odd happening? How exactly are you attempting the install?

arturro’s picture

arturro commented

class RulesUIController is only in 7.x-2.x-dev, not in version: 7.x-2.0-alpha3

xibun’s picture

xibun commented

+1

rszrama’s picture

rszrama commented

Ahh, perhaps I should specify the -dev versions for Rules, Entity, and Views. Updating the project page now. Let me know if there's still some remaining issue here.

damien tournoud’s picture

damien tournoud commented

Drupal 7 supports version dependencies, so you could specify: rules_admin (>2.0-alpha3) in your dependencies.

rszrama’s picture

rszrama commented

Ahh, cool - I suppose the > operator will accept any dev version with a later date than the indicated release?

damien tournoud’s picture

damien tournoud commented

I don't really know :)

xibun’s picture

xibun commented
Status: Active » Reviewed & tested by the community

I now updated the required modules and the problem is gone (see comment #5).
Note: I was already using the .dev versions - but dated 21th December 2010.

rszrama’s picture

rszrama commented
Title: RulesUIController does not exist » RulesUIController does not exist (fix: update to latest dev)
Status: Reviewed & tested by the community » Fixed

A brief investigation of version dependencies didn't see an easy way to target dev versions since they don't have version strings at all... it looks like Drupal core might not know what to do in those situations.

Gonna mark this fixed and hope the documentation on the project page helps enough. It'll be a moot point the next time Rules does a point release, and soon everyone will update their dev versions.

Status: Fixed » Closed (fixed)

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