Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Tested on OA 2.32
$ drush dl invite
$ drush pm-enable -y invite
Invite module is https://www.drupal.org/project/invite
PHP Fatal error: Class 'InviteTypeController' not found in /var/www/oa/includes/common.inc on line 7914
Drush command terminated abnormally due to an unrecoverable error. [error]
Error: Class 'InviteTypeController' not found in /var/www/oa/includes/common.inc, line 7914
On latest "normal" Drupal, it installs without any problem.
Comment | File | Size | Author |
---|---|---|---|
#15 | 2446411-Class-InviteTypeController-not-found.patch | 994 bytes | SocialNicheGuru |
Comments
Comment #1
JKingsnorth CreditAttribution: JKingsnorth commentedThis doesn't sound like a bug in Open Atrium per sae, so I'm marking it as a support request.
It may be a bug in the Invite module that makes it incompatible with the patches that the OA distribution applies to certain modules.
So perhaps try installing Invite on vanilla Drupal, but with the patches applied to the ctools and entity modules that OA uses. A list of these patches can be found in the relevant module directories in the OA profile.
Comment #2
Drupaler at UN CreditAttribution: Drupaler at UN commentedI tested on vanilla Drupal, with the following patches applied:
CTOOLS
- http://www.drupal.org/files/issues/2119357-6_0.patch
- https://www.drupal.org/files/issues/views_content-ajax-1910608-23_0.patch
- https://www.drupal.org/files/issues/ctools-views_content-exposed_form_ov...
- http://drupal.org/files/2023705-ctools-autosubmit-2_0.patch
- https://www.drupal.org/files/issues/2423839-ctools-node_tag-2.patch
ENTITY
- http://drupal.org/files/entity-translatable_fields_not_overriding_und_wi...
- http://drupal.org/files/issues/entity-1788568-21-entity_metadata_wrapper...
- http://drupal.org/files/issues/entity_unsupported_operand-2407905-1.patch
invite does install without error.
I then copied from OA the ctools and entity folders, and
invite does install without error.
I can do more patching/testing if needed, just indicate me what other(s) module(s) to test.
Comment #3
Drupaler at UN CreditAttribution: Drupaler at UN commentedComment #4
JKingsnorth CreditAttribution: JKingsnorth commentedAnother patch-related thought - OA also applies patches to Drupal core. Perhaps try again with the Core patches? Currently:
- http://drupal.org/files/1356276-make-D7-21.patch
- http://drupal.org/files/d7_move_access_to_join_condition-1349080-89.patch
- http://drupal.org/files/911354-drupal-profile-85.patch
- http://drupal.org/files/1093420-22.patch
- http://drupal.org/files/drupal-menu_always_load_objects-1697570-5.patch
- http://drupal.org/files/issues/options_drupal7-1919338-58.patch
- https://www.drupal.org/files/issues/1311820-drupal-registry_update-13.patch
Comment #5
Drupaler at UN CreditAttribution: Drupaler at UN commentedHi
I applied the core patches.
invite does install without error.
I f you can guide me in testing more.
Comment #6
JKingsnorth CreditAttribution: JKingsnorth commentedIt seems like this might be related to an issue that already is mentioned in the module's issue queue.
Have you tried installing the latest dev version of Invite instead?
Comment #7
Drupaler at UN CreditAttribution: Drupaler at UN commentedYes, I did.
I can xdebug if you guide me a bit (I have no clue where to start to when doing an install):
here is the stack trace with the dev version
and here is the stack trace with the "stable" version: (it looks identical to me)
Comment #8
JKingsnorth CreditAttribution: JKingsnorth commentedLooks like the linkit module is trying to hook in to the process as well. Perhaps try installing in your steup in #2 but with the linkit module enabled? OA uses linkit 3.3 (unpatched)
I haven't been able to reproduce this on simplytest.me, but it might be worth a shot.
Still not convinced this is an Open Atrium issue, so I'm going to move it to the Invite module's issue queue, maybe they will have a better idea.
Comment #9
mpotter CreditAttribution: mpotter commentedYes, this needs to move over to the Invite issue queue. Nothing else we can do here.
Comment #10
JKingsnorth CreditAttribution: JKingsnorth commentedWe're in the other queue now, so let's see if the Invite maintainers can help.
Comment #11
ckngIt is not clear what version of Invite you are trying to install.
Version: ?
Are you doing fresh install or upgrade from older version?
Based on your comments, the conclusion I'm getting is "invite does install without error". So not sure how we could help.
Comment #12
B-Prod CreditAttribution: B-Prod commentedI have the same issue using a Panopoly distribution.
I tried to install the module with Drush, but it failed with the same message.
It seems that it is caused by a specific configuration, where Entity Translation is enabled.
The following modules, working together, make the error occur at bootstrap time (when calling drupal_path_initialize):
Redirect (patched with a merge to global redirect)
Entity Translation
Invite
The call to
path_is_admin()
from the Redirect module leads to a call toentity_translation_admin_paths()
(called bypath_get_admin_paths()
).This needs to load the entity info, and especially the invite type (
invite_get_types()
called byinvite_entity_info_alter()
). This is where it goes bad: the registry is not rebuilt at this time, so it fails.Solution for disabling the Invite module and get the site back: disabling the Invite module from the system table and rebuilding the registry with drush and Registry Rebuild.
So the problem is not the fact of Invite, but caused by the way Drupal handle the classes autoload.
Solution: make Invite use the PSR-4 and rely on X-Autoload...
Comment #13
B-Prod CreditAttribution: B-Prod commentedIf you really want to use the Invite module, you will need to force the registry to discover the required classes.
SQL Query:
Then you have to rebuild the registry with Drush and Registry Rebuild:
drush rr
Comment #14
ckngI've seen similar issue but with Panopoly and Feeds. What B-Prod says - remove the offending module temporary, rebuild registry, restore the offending module solved it.
Please try the solution proposed to see if it solves your problem.
Comment #15
SocialNicheGuru CreditAttribution: SocialNicheGuru commentedclass loading was not working during install
I added the needed files to the .module file.
I also added two to the .info file
I do not have xautolad enabled
Comment #16
SpartyDan CreditAttribution: SpartyDan commented@SocialNicheGuru
Please include details of your install. Are you using OA or Panopoly?
Do you encounter the same error on a fresh install of Drupal?
I cannot reproduce the error on a fresh install of Drupal 7.51.