Timeline for Recipient loading failed in mailing after upgrade to 5.65.1
Current License: CC BY-SA 4.0
38 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 20, 2023 at 1:07 | comment | added | Lars SG | Easiest probably just to delete them and replace with ones from the new version, but might be worth figuring out what went wrong here. | |
| Sep 19, 2023 at 21:46 | comment | added | markd | Many thanks for your help as I would not have progressed this far ;-)....I will investigate and report any findings. | |
| Sep 19, 2023 at 14:06 | comment | added | Lars SG | I'm not sure what's up, but all the 5.57 ones should be upgraded when you upgrade. If they aren't being upgraded, then you should try to figure out why. I don't know. Maybe a permissions issue, like the upgrader can't delete the existing versions? IATS is not in core, nor contribution cancel actions. But both oauth client and afform should be 5.65. Sounds like you might have the same problem as flexmailer for those. | |
| Sep 19, 2023 at 8:22 | comment | added | markd | Many Thanks @Lars SG...I've been checking our set up and the following core modules are Not 5.65.1... CiviGrant 5.57.0 (we do not use this) CiviGrant 5.57.0 (we do not use this) IATs Payments 1.7.5 (we do not use this) Contribution cancel actions 1.0 Elavon Payment Processor 5.57.0 OAuth Client 1.0 Afform x 3 - 0.5 with "Flask" Admin UI although has the right version but has a flask. Payflowpro 1.0 How do I get them all to 5.65.1? | |
| Sep 17, 2023 at 14:51 | comment | added | Lars SG | You should have up to date versions of all the extensions that come with core, none of them should be different versions than the core version. The civicrm/ext directory is part of the upgrade process. Afform core is required. | |
| Sep 16, 2023 at 22:25 | comment | added | markd | Thanks @Lars....I had an earlier beta version of Serchkit when I compared with my other server. I do have a number of extensions that are pre-release. AuthX, Civicrm Admin UI, CivicImport. {Afform Core Runtime, HTML, Form builder}...Do I need Afform set of extensions? as I believe it is contributing to [warning] Deprecated function Civi\Angular\AngularLoader::load, use angularjs.loader service. | |
| Sep 16, 2023 at 14:54 | comment | added | Lars SG | Yeah, search kit is required now, I'm not sure you ended up without it. The little flask means it is pre-release, not a mature extension (hover over it, there is help text). Your other warnings may or may not be meaningful, I'm not sure. | |
| Sep 16, 2023 at 13:58 | comment | added | markd | I have also disabled CiviCase to check if stops the “angular” warnings. I have also disabled CiviGrant and Civicampaign as we do not use these functions. Btw, what is the yellow icon (that looks like a flask) in the extensions UI? | |
| Sep 16, 2023 at 13:32 | comment | added | markd | Any suggestions on these 3 warnings? btw, I didnt roll back to the pre upgrade files. | |
| Sep 16, 2023 at 13:30 | comment | added | markd | The only warnings that I am getting are 1. [warning] Deprecated function CRM_Core_BAO_Job::retrieve, use API. 2 [warning] Deprecated function Civi\Angular\AngularLoader::setModules, use addModules. 3. [warning] Deprecated function Civi\Angular\AngularLoader::load, use angularjs.loader service. The other errors (e.g. ManagedEntity) are not present. Hence I think that the mailing issue may have been resolved for now except for the warnings above. I will keep you posted after I do some testing. Many thanks for your help. | |
| Sep 16, 2023 at 13:30 | comment | added | markd | I took your advise and did some investigative work. Your suggestion of Search_kit was correct. I renamed my Search_Kit and copied search_kit to the extensions directory from my subdomain server. I Uninstall Extensions - SearchUI, OAuth Client only. | |
| Sep 16, 2023 at 2:58 | comment | added | markd | Can I turn off Search kit first? Should I leave out core CiviCrm components which I turned on today before the upgrade or turn it on after the upgrade? | |
| Sep 16, 2023 at 1:35 | comment | added | Lars SG | Otherwise, it sounds like possibly an issue to do with SearchKit. You can check that, but you might want to consider going to your backup at this point, switching Flexmailer before upgrading, and trying the upgrade again. It's possible something went wrong in the upgrade process. | |
| Sep 16, 2023 at 1:33 | comment | added | Lars SG | Oh, I just meant the core extensions that have core components (CiviMail, CiviEvent, etc). Did you check that CiviMail is enabled as an extension and also enabled as a component (Administer -> System Settings -> Extensions and -> Components)? | |
| Sep 16, 2023 at 0:19 | comment | added | markd | I now can't get to administer >System Settings>Scheduled Jobs screen. The error is - Invalid field 'saved_search.name' Does this give us some clues for the mailing perhaps? | |
| Sep 16, 2023 at 0:00 | comment | added | markd | This Warning has appeared in the last 1 hr. [warning] Civi\Api4\Generic\BasicBatchAction constructor received $doer as a non-callable; the 3rd param as the $select param has been removed Caller: Civi\Api4\Action\OAuthSysToken\Refresh::__construct Array ( [civi.tag] => deprecated ) is this because OAuth Client was installed? | |
| Sep 15, 2023 at 22:18 | comment | added | markd | ...what would be my next steps? | |
| Sep 15, 2023 at 22:17 | comment | added | markd | The mailing issue was immediately (100%) after the upgrade. I have now enabled all core extensions that were in /wp-content/plugins/civicrm/civicrm/ext through the UI which are as follows... CiviCase, CiviCampaign, CiviPledge, admin UI, Search UI, CiciGrant, CiviImports, iATSpayments, Elavon payment processor, OAuth Client, payflowpro Cleared cache with CV flush The mailing issue still exists.... Error log has many warning entries - [warning] ManagedEntity update policy "unmodified" specified for entity type SearchDisplay which is not an APIv4 ManagedEntity. Falling back to policy "always" | |
| Sep 15, 2023 at 13:25 | comment | added | Lars SG | Check if all core extensions (CiviContribute, CiviMail, etc) are enabled in Extensions and enabled as Components. | |
| Sep 15, 2023 at 13:25 | comment | added | Lars SG | Yes, those might be unrelated to the mailings issue. Are you sure the mailings issue you are having now came after the Flexmailer changes? Or possibly just after the upgrade? | |
| Sep 15, 2023 at 5:59 | comment | added | markd | content/plugins/civicrm/includes/civicrm.basepage.php:380 { …} /example.org/httpdocs/wp-includes/class-wp-hook.php:310 { …} /example.org/httpdocs/wp-includes/class-wp-hook.php:334 { …} /example.org/httpdocs/wp-includes/plugin.php:565 { …} /example.org/httpdocs/wp-includes/class-wp.php:796 { …} /example.org/httpdocs/wp-includes/functions.php:1335 { …} /example.org/httpdocs/wp-blog-header.php:16 { …} /example.org/httpdocs/index.php:17 { …}........ I'm not sure what this is about???..Probably unrelated to what info we exchanging earlier | |
| Sep 15, 2023 at 5:44 | comment | added | markd | /example.org/httpdocs/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php:319 { …} /example.org/httpdocs/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php:69 { …} /example.org/httpdocs/wp-content/plugins/civicrm/civicrm/CRM/Core/Invoke.php:36 { …} /example.org/httpdocs/wp-content/plugins/civicrm/civicrm.php:1199 { …} /example.org/httpdocs/wp- | |
| Sep 15, 2023 at 5:41 | comment | added | markd | trace: { /example.org/httpdocs/wp-content/plugins/civicrm/civicrm/CRM/Utils/System/WordPress.php:605 { CRM_Utils_System_WordPress->permissionDenied() › $civicrm_wp_title = ts('You do not have permission to access this page.'); › throw new CRM_Core_Exception(ts('You do not have permission to access this page.')); › } } /example.org/httpdocs/wp-content/plugins/civicrm/civicrm/CRM/Utils/System.php:62 { …} /example.org/httpdocs/wp-content/plugins/civicrm/civicrm/CRM/Mailing/Page/View.php:140 { …} ....... | |
| Sep 15, 2023 at 5:39 | comment | added | markd | The following has appeared in the last hour.....[error] $Fatal Error Details = array:3 [ "message" => "You do not have permission to access this page." "code" => null "exception" => CRM_Core_Exception {#22537 -errorData: array:1 [ "error_code" => 0 ] #cause: null -_trace: null #message: "You do not have permission to access this page." #code: 0 #file: "/example.org/httpdocs/wp-content/plugins/civicrm/civicrm/CRM/Utils/System/WordPress.php" #line: 605 and this continues.... | |
| Sep 15, 2023 at 5:25 | comment | added | markd | No specific error in the Civicrm logs......it is primary domain with a CiviCRM Db and a subdomain with a separate CiviCrm Db on the same physical server......the subdomain works fine.......what next steps would you like me try out as I have asked our user community to not use Civi for mail outs till I can rectify. Would re-installing core s'ware help and what would be the steps.?By the way the managed entity warnings have surfaced after the upgrade only. | |
| Sep 15, 2023 at 4:22 | comment | added | Lars SG | That's a weird warning. Not sure what to make of it. Are they all about Managed Entities or other things too? Do you get a specific error when you try to open a new mailing for instance? | |
| Sep 15, 2023 at 0:34 | comment | added | markd | yes, I enabled both and can see them in Adminster>System Settings>Extensions shows Flexmailer 5.65.1 (status required with green tick and no uninstall option) and Mosaico 3.2.1691060437 with green tick. yes I performed cv flush. | |
| Sep 15, 2023 at 0:19 | comment | added | Lars SG | Are both Mosaico and Flexmailer enabled? Cleared the cache? | |
| Sep 15, 2023 at 0:05 | comment | added | markd | Error log has many warning entries - [warning] ManagedEntity update policy "unmodified" specified for entity type SearchDisplay which is not an APIv4 ManagedEntity. Falling back to policy "always" Any other suggestions to get this working would be greatly appreciated. | |
| Sep 15, 2023 at 0:05 | comment | added | markd | ..thks..here is what I have done. I have brought the flexmailer directory/files back into ~/wp-content/plugins/civicrm/civicrm/ext Just fyi, I do not have flexmailer Directory or flexmailer files in ~/example.org/httpdocs/wp-content/uploads/civicrm/ext I only have ca.civicrm.logviewer, mosaicotweaks, uk.co.vedaconsulting.mosaico and webtracking-1.3(not used) in this drectory Adminster>System Settings>Extensions shows Flexmailer 5.65.1. “Loading failed” still comes up when accessing draft mailings. | |
| Sep 14, 2023 at 14:15 | comment | added | Lars SG | Sounds like you deleted the current Flexmailer and kept the old one, because you were in the CiviCRM/ext directory (which is for extensions that come with CiviCRM) instead of the extensions directory for added extensions (normally in /wp-content/uploads/civicrm/ext). So, put the one you deleted back, go to the added extensions directory and follow the same procedure there. | |
| Sep 14, 2023 at 12:56 | comment | added | markd | ...Would you suggest that I revert back to v5.58.1 as I have the files and database and then remove Fleximailer v1.1.2. Once this is done to upgrade the system to 5.65.1? | |
| Sep 14, 2023 at 7:26 | comment | added | markd | I am now a little lost on what to do next as it is not picking up new Flexmailer but shows Flexmailer 1.1.2. | |
| Sep 14, 2023 at 7:26 | comment | added | markd | Thanks @Lars My steps of what I did (Managed to get CLI working) From Extensions. Directory 1. copied flexmailer to different directory just in case I need it. 2. cv dis mosaico flexmailer 3. rm -rf org.civicrm.flexmailer when I did this, it did not remove the directory/contents so I used rm -rf flexmailer 4. cv flush 5. cv en flexmailer mosaico >>>>>error Extension cache does not contain requested item(s) Refreshing extension cache >>>Error: Unrecognized extension "flexmailer" I noticed in Adminster>System Settings>Extensions that FlexMailer was disabled and in red | |
| Sep 13, 2023 at 13:24 | history | edited | Lars SG | CC BY-SA 4.0 |
added 221 characters in body
|
| Sep 13, 2023 at 13:21 | comment | added | Lars SG | I've added instructions to the answer above. | |
| Sep 13, 2023 at 12:37 | comment | added | markd | Thanks Lars SG....I did check and I noticed that I had Flexmailer 1.1.2 instead of Flexmailer 5.65....I have checked the past question for instructions....I have another problem as I am having problem installing command line interface to run cv commands....is there another way to update to Flexmailer 5.65 through UI? | |
| Sep 12, 2023 at 14:56 | history | answered | Lars SG | CC BY-SA 4.0 |