Skip to content
Snippets Groups Projects
  1. Feb 21, 2020
  2. Jan 18, 2020
  3. Oct 02, 2019
    • totten's avatar
      extension-compatibility - Add 'force-uninstall' mode for api4 transition · 6542d699
      totten authored
      There is a compatibility problem when upgrading a system which  has an old
      copy of api4: the top level `api4.php` indiscriminately declares the
      function `civicrm_api4()`, which eventually provokes a conflict with the
      copy that is now in `civicrm-core`.
      
      Using the normal disable/uninstall actions doesn't resolve this because the
      error arises too early during boot (before the upgrader gets a chance to
      remove the extension).
      
      The 'force-uninstall' option will make the system behave as if the extension
      is uninstalled, regardless of what files exist and what state may be stored
      in the `civicrm_extension` table.
      
      This commit technically does ~3 things:
      
      1. Changes the policy for `org.civicrm.api4` to use `force-uninstall`
      2. Makes the extension-cache version-dependent. During an upgrade, you
         might have a stale cache that claims that the old extension is
         active. This ensures that (as soon as you drop in new code)
         it begins working with a fresh cache.
      3. Update any spots which query the table `civicrm_extensions` for
         extension status. Have it consult `extension-compatibility.json`
         for `force-uninstall`ed items.
      6542d699
    • colemanw's avatar
      Completely uninstall obsolete extensions during upgrade · df7a1988
      colemanw authored and totten's avatar totten committed
      df7a1988
  4. Sep 14, 2019
  5. Feb 28, 2019
  6. Feb 21, 2019
  7. Dec 29, 2018
Loading