Skip to content
Snippets Groups Projects
  1. Mar 15, 2023
  2. Mar 14, 2023
  3. Mar 08, 2023
  4. Mar 06, 2023
  5. Mar 01, 2023
  6. Feb 28, 2023
  7. Feb 18, 2023
  8. Feb 17, 2023
  9. Feb 16, 2023
  10. Feb 15, 2023
  11. Feb 14, 2023
  12. Feb 10, 2023
  13. Dec 03, 2022
  14. Oct 21, 2022
  15. Sep 30, 2022
  16. Aug 03, 2022
  17. Jun 17, 2022
  18. May 23, 2022
  19. Sep 08, 2021
    • totten's avatar
      #101 - Do not activate custom-search classes on all page-views · 0736926a
      totten authored
      _Overview_: Civi 5.41 began migrating the "custom search" layer to an extension
      (`legacycustomsearches`).  `dataprocessor` uses the "custom search" layer in a way that
      provokes a hard/ubiquitous error during upgrade.  This revision makes it more robust
      against upgrade errors.
      
      _Before_: `hook_config` unconditionally (*on all page-views*) loads
      `CRM_DataprocessorSearch_Form_Search_Custom_DataprocessorSmartGroupIntegration` and calls
      `redirectCustomSearchToDataProcessorSearch()`.
      
      _After_: `hook_config` only calls `CRM_DataprocessorSearch_Form_Search_Custom_DataprocessorSmartGroupIntegration`
      if it's needed.
      
      _Comments_:
      
      * The error arises from when autoloading the base-class `CRM_Contact_Form_Search_Custom_Base`. This class
        exists, but it won't be available until the upgrade is complete.
      * Strictly speaking, the two conditionals (on `$currentUrl` and `ssID`) are sufficient. I threw in a
        third conditional (`class_exists()`) as an extra bit of paranoia.
      * I did a light `r-run` to ensure that the upgrade process works with the patch. However, I did not
        test the redirect.
      * We're planning to include a short-term work-around in 5.41.1. However, this work-around will go away
        soon (eg 5.42 or 5.43).
      0736926a
  20. May 20, 2021
  21. May 14, 2021
  22. May 13, 2021
  23. Apr 07, 2021
  24. Apr 06, 2021
  25. Mar 12, 2021
  26. Mar 11, 2021
  27. Feb 25, 2021
Loading