David Hayes (01298b49) at 15 May 07:55
Similar (same?) issue with Contact Summary Tabs since in the end both CRM_DataprocessorDashlet_Form_Dashlet
and CRM_Contact_Form_DataProcessorContactSummaryTab
extend the same base class CRM_Dataprocessor_Form_Output_AbstractUIOutputForm
PHP Fatal error: Cannot make static method CRM_Dataprocessor_Form_Output_AbstractUIOutputForm::getDefaultLimit() non static in class CRM_Contact_Form_DataProcessorContactSummaryTab in /home/example.com/public_html/wp-content/uploads/civicrm/ext/dataprocessor/CRM/Contact/Form/DataProcessorContactSummaryTab.php on line 24, referer: https://example.com/wp-admin/admin.php?page=CiviCRM&q=civicrm%2Fcontact%2Fview&reset=1&cid=2925&selectedChild=dataprocessor_referrals
Here is a merge request that fixes the issue for me: !115 (merged)
Copied fix detailed here: 48296352
David Hayes (01298b49) at 13 May 02:15
Fix for related issue to #122. Contact Summary tab not loading due ...
... and 258 more commits
David Hayes (48296352) at 13 May 01:46
Regression fix dashlets not working anymore #122
... and 257 more commits
Problem solved @eileen as of 5.60.0! Thank you!
I double checked civicrm_custom_field
, the schema seems correct.
`html_type` varchar(32) COLLATE utf8mb4_unicode_ci NOT NULL COMMENT 'HTML types plus several built-in extended types.',
`is_view` tinyint(4) NOT NULL DEFAULT '0' COMMENT 'Is this property set by PHP Code? A code field is viewable but not editable',
Hello! Apologies for the delay. I must need to turn on email updates, didn't get one until you tagged me @eileen. I will update the affected site in the next week or so and report back.
If this issue persists, what would useful for debugging purposes. Maybe a dump of civicrm_custom_field
and $cFields
looking at @totten 's comment?
After update to 5.59 (maybe earlier). A fatal error is received on merging contacts.
PHP Fatal error: Uncaught TypeError: Argument 6 passed to CRM_Dedupe_Merger::processCustomFields() must be of the type bool, null given, called in /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Dedupe/Merger.php on line 2128 and defined in /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Dedupe/Merger.php:2553
Stack trace:
#0 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Dedupe/Merger.php(2128): CRM_Dedupe_Merger::processCustomFields()
#1 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Contact/Form/Merge.php(324): CRM_Dedupe_Merger::moveAllBelongings()
#2 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Form.php(573): CRM_Contact_Form_Merge->postProcess()
#3 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/StateMachine.php(144): CRM_Core_Form->mainProcess()
#4 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/QuickForm/Action/Next.php(43): CRM_Core_StateMachine->perform()
#5 /home/example/public_html/wp-content/plugins/civicrm/ in /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Dedupe/Merger.php on line 2553
Ensure $htmlType
and $isView
are set and bools.
Contacts merged.
NA
@bradleyt Ya, it's still happening for us. I have not had time to circle around and debug further. Working around it by creating users before their first login manually currently. Not optimal, but nothing is.
Right now, testing fixes is a bit cumbersome because I am having to creating users on the Idp side (sso) then test each individual fix. Do you have a method to better reproduce the issue so I could iterate fixes faster?
I would tend to agree @lcdweb. I tried a few similar checks, but did not have any success. I ended up looking pretty deep into how extension classes are autoloaded, but I could not quite identify what was happening in the wrong order.
Currently, my working theory is that the multiple calls to CiviCRM initialize is tripping a "CiviCRM loaded" check and letting code run that shouldn't be before the initialize is completed. However, this need more research.
#11 /home/example/public_html/wp-content/plugins/civicrm-admin-utilities/civicrm-admin-utilities.php(361): CiviCRM_For_WordPress->initialize()
...
#26 /home/example/public_html/wp-content/plugins/civicrm/civicrm.php(794): CiviCRM_For_WordPress->initialize()
The more I look, doesn't seem to be CiviRules specific. Seems there is a path that triggers the preinsert
event before the CiviCRM extension classes load.
The event payload is the Contact creation object for the new user. The issue goes away if I manually syncronize users to contacts.
#0 /home/example/public_html/wp-content/plugins/civicrm/civicrm/vendor/symfony/event-dispatcher/EventDispatcher.php(214): civirules_trigger_preinsert()
#1 /home/example/public_html/wp-content/plugins/civicrm/civicrm/vendor/symfony/event-dispatcher/EventDispatcher.php(44): Symfony\Component\EventDispatcher\EventDispatcher->doDispatch()
#2 /home/example/public_html/wp-content/plugins/civicrm/civicrm/Civi/Core/CiviEventDispatcher.php(198): Symfony\Component\EventDispatcher\EventDispatcher->dispatch()
#3 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/DAO.php(653): Civi\Core\CiviEventDispatcher->dispatch()
#4 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Contact/BAO/Contact.php(189): CRM_Core_DAO->save()
#5 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Contact/BAO/Contact.php(290): CRM_Contact_BAO_Contact::add()
#6 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Contact/BAO/Contact.php(2029): CRM_Contact_BAO_Contact::create()
#7 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/BAO/UFMatch.php(281): CRM_Contact_BAO_Contact::createProfileContact()
#8 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/BAO/UFMatch.php(104): CRM_Core_BAO_UFMatch::synchronizeUFMatch()
#9 /home/example/public_html/wp-content/plugins/civicrm/includes/civicrm.admin.php(449): CRM_Core_BAO_UFMatch::synchronize()
#10 /home/example/public_html/wp-content/plugins/civicrm/civicrm.php(972): CiviCRM_For_WordPress_Admin->initialize()
#11 /home/example/public_html/wp-content/plugins/civicrm-admin-utilities/civicrm-admin-utilities.php(361): CiviCRM_For_WordPress->initialize()
#12 /home/example/public_html/wp-content/plugins/civicrm-admin-utilities/includes/civicrm-admin-utilities-single.php(1690): CiviCRM_Admin_Utilities->is_civicrm_initialised()
#13 /home/example/public_html/wp-includes/class-wp-hook.php(307): CiviCRM_Admin_Utilities_Single->register_menu_directory()
#14 /home/example/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#15 /home/example/public_html/wp-includes/plugin.php(522): WP_Hook->do_action()
#16 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Utils/Hook/WordPress.php(108): do_action_ref_array()
#17 /home/example/public_html/wp-content/plugins/civicrm/civicrm/Civi/Core/CiviEventDispatcher.php(237): CRM_Utils_Hook_WordPress->invokeViaUF()
#18 /home/example/public_html/wp-content/plugins/civicrm/civicrm/vendor/symfony/event-dispatcher/EventDispatcher.php(214): Civi\Core\CiviEventDispatcher::delegateToUF()
#19 /home/example/public_html/wp-content/plugins/civicrm/civicrm/vendor/symfony/event-dispatcher/EventDispatcher.php(44): Symfony\Component\EventDispatcher\EventDispatcher->doDispatch()
#20 /home/example/public_html/wp-content/plugins/civicrm/civicrm/Civi/Core/CiviEventDispatcher.php(198): Symfony\Component\EventDispatcher\EventDispatcher->dispatch()
#21 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Utils/Hook.php(167): Civi\Core\CiviEventDispatcher->dispatch()
#22 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Utils/Hook.php(1352): CRM_Utils_Hook->invoke()
#23 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/Config.php(92): CRM_Utils_Hook::config()
#24 /home/example/public_html/wp-content/plugins/civicrm/includes/civicrm.admin.php(434): CRM_Core_Config::singleton()
#25 /home/example/public_html/wp-content/plugins/civicrm/civicrm.php(972): CiviCRM_For_WordPress_Admin->initialize()
#26 /home/example/public_html/wp-content/plugins/civicrm/civicrm.php(794): CiviCRM_For_WordPress->initialize()
#27 /home/example/public_html/wp-content/plugins/civicrm/civicrm.php(767): CiviCRM_For_WordPress->register_hooks_clean_urls()
#28 /home/example/public_html/wp-content/plugins/civicrm/civicrm.php(651): CiviCRM_For_WordPress->register_hooks_common()
#29 /home/example/public_html/wp-includes/class-wp-hook.php(307): CiviCRM_For_WordPress->register_hooks()
#30 /home/example/public_html/wp-includes/class-wp-hook.php(331): WP_Hook->apply_filters()
#31 /home/example/public_html/wp-includes/plugin.php(474): WP_Hook->do_action()
#32 /home/example/public_html/wp-settings.php(587): do_action()
#33 /home/example/public_html/wp-config.php(90): require_once('/home/example...')
#34 /home/example/public_html/wp-load.php(50): require_once('/home/example...')
#35 /home/example/public_html/wp-admin/admin.php(34): require_once('/home/example...')
#36 {main}
David Hayes (853e8d82) at 01 Apr 19:21
Merge branch 'artfulrobot-fix-notice-errors' into 'master'
... and 24 more commits
CiviCRM is running on a Wordpress site with a SSO plugin that is capable of provisioning users on first login (JIT). Existing users are able to log in correctly, however new users (ie a user/contact creation) fails with the following fatal error.
This seems to be related to the civirules_trigger_preinsert
hook. My initial guess is the somehow the autoloading is not successfully resolving in a scenario where where a user is created but the contact has not been created.
I suspect this is related to #156.
PHP Fatal error: Uncaught Error: Class 'CRM_Civirules_Utils' not found in /home/example/public_html/wp-content/uploads/civicrm/ext/org.civicoop.civirules/civirules.php:356, referer: https://ssoprovider.com/
Stack trace:, referer: https://ssoprovider.com/
#0 /home/example/public_html/wp-content/plugins/civicrm/civicrm/vendor/symfony/event-dispatcher/EventDispatcher.php(214): civirules_trigger_preinsert(), referer: https://ssoprovider.com/
#1 /home/example/public_html/wp-content/plugins/civicrm/civicrm/vendor/symfony/event-dispatcher/EventDispatcher.php(44): Symfony\\Component\\EventDispatcher\\EventDispatcher->doDispatch(), referer: https://ssoprovider.com/
#2 /home/example/public_html/wp-content/plugins/civicrm/civicrm/Civi/Core/CiviEventDispatcher.php(198): Symfony\\Component\\EventDispatcher\\EventDispatcher->dispatch(), referer: https://ssoprovider.com/
#3 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Core/DAO.php(653): Civi\\Core\\CiviEventDispatcher->dispatch(), referer: https://ssoprovider.com/
#4 /home/example/public_html/wp-content/plugins/civicrm/civicrm/CRM/Contact/BAO/Contact.php(189): CRM_Core_DAO->save(), referer: https://ssoprovider.com/
#5 /home/example/public_html/wp-content/plugins/civicrm/civicrm in /home/example/public_html/wp-content/uploads/civicrm/ext/org.civicoop.civirules/civirules.php on line 356, referer: https://ssoprovider.com/
Thoughts appreciated. Where would be a good place to start looking for the issue?
David Hayes (cdb3ecb7) at 29 Mar 07:42
Added action register participant, fixes #169
... and 287 more commits
When using a profile with user creation in Wordpress, the user is not longer logged in.
https://github.com/civicrm/civicrm-core/pull/20807
(PR was a while ago, I think I forgot to finish opening this issue and it was left in my draft)
That is a good idea. There have been some good recent changes to make the Civi <> User Account process more seemless.
Thanks @justinfreeman! I should have checked my links. I updated the issue.
Finished execution of Send Scheduled Reminders with result: Failure, Error message: Failed encoding non-numeric value (#selectedValues)
The selected activity types are stored in the civicrm_action_schedule
table in the entity_value
column. This column only supports 255 characters. Adding any more characters than this causes the value to be truncated with an elipsis "..." at the end. This error originates from CRM_Activity_ActionMapping::createQuery
where the code places the trucated list of Activity Types into a where clause in a query. The "..." after the last value cause an integer check to fail.
Convert this column to something longer? TEXT maybe? Happy to make a PR, but would like to know the preferred path.