Extensions - Setup <classloader> during "enable" and "uninstall"
authorTim Otten <totten@civicrm.org>
Wed, 21 Apr 2021 16:43:56 +0000 (09:43 -0700)
committerTim Otten <totten@civicrm.org>
Wed, 21 Apr 2021 16:56:30 +0000 (09:56 -0700)
commitc09b5c5b673cebb7f0470debe0b6df8fbc7c93f8
treeb6294ce85e086e986a54325c828d7bf6c4dda2ad
parent1d1b7ce2fdc0e660a54ae8a17c644aca037783ee
Extensions - Setup <classloader> during "enable" and "uninstall"

This is an analog/follow-up to https://github.com/civicrm/civicrm-core/pull/20091

Why is this necessary? Recall that a typical admin will go through this lifecycle:

1. Enable extension $x
2. Disable extension $x
3. Either:
   * (a) Re-enable extension $x
   * (b) Uninstall extension $x

Step `#2` disables the classloader for purposes of regular page-loading. However, when you
get to step `#3a` or `#3b`, then you need the classloader again.
CRM/Extension/Manager/Module.php