PHP Fatal error: Class 'RegistrationMetadataController' not found in entity/entity.info.inc on line 23

i have to use drush rr to flush registries

Comments

mrconnerton’s picture

I was getting a similar error when I tried to upgrade the module with registration.entity.inc after it moved in this commit: http://drupalcode.org/project/registration.git/commit/d26ec59cbf5a6df6f5...

I was able to solve the problem by downloading this command: http://drupal.org/project/registry_rebuild and running it on the effected site.

levelos’s picture

Status: Active » Closed (fixed)
ezra-g’s picture

Status: Closed (fixed) » Active

If Registry Rebuild is required to prevent fatal errors in Entity Registration, it should be added as a dependency. If it's not a dependency, we should fix the bug in ER.

Moving status back to "active."

levelos’s picture

Status: Active » Closed (works as designed)

Ezra, it is not required and I am not aware of any bugs raised in this issue. The fact that someone's registry is hosed it not a bug with ER. I'm closing; if you can find a bug, please reopen, ideally with a patch.

mrconnerton’s picture

Status: Closed (works as designed) » Active

Registry Rebuild isn't actually a module, just a drush command to simplifying clearing out the class registry. My particular issue was when I upgraded the registration module, I couldn't run a drush updb -y because of missing classes which got moved in this commit: http://drupalcode.org/project/registration.git/commit/d26ec59cbf5a6df6f5...

mrconnerton’s picture

Status: Active » Closed (fixed)
SocialNicheGuru’s picture

Is there a better way to deal with this? Many modules have ctools related classes and/or other classes.
This is the only one that continually will throw a fatal error when I use 'drush dis' to disable it

SocialNicheGuru’s picture

Status: Closed (fixed) » Active

I wonder if somehow these two are related: https://drupal.org/node/2106995

I get an error on install and an error on disable using drush

SocialNicheGuru’s picture

Issue summary: View changes

Is this a module weight issue between entity and registration? If entity gets enabled before registration, how would it see the registration class?

This could be why enabling registration the second time seems to work.

john.oltman’s picture

Status: Active » Closed (outdated)