Answers.Body: <p>The issue is resolved by disabling form processor and action provider, rolling action provider back to version 1.18, and re-enabling form processor. Apparently the update of action provider on 3rd March broke form processor, at least in my instance of CiviCRM on WordPress.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2023-03-06T21:06:51.973Z
Answers.LastActivityDate: 2023-03-06T21:06:51.973Z
Answers.UserDisplayName: gillenpj
Body: <p>I've been using the fabulous Form Processor and Action Provider extensions for several months, and have built up a very useful suite of forms implemented in Google Forms and connected to various form processors in CiviCRM to execute actions. Everything was working great until today. Now, if I even try to access the Form Process menu item I get the error in the screenshot below. I've tried disabling this extension and also the Action Provider extension upon which it depends and then re-enabling both but that hasn't helped. The Action Provider was updated on 3rd March but I don't exactly know when this issue arose. Can anyone suggest any lines of inquiry / resolutions based on the screenshot below? Many thanks, Patrick.</p>
  <p><a href="https://i.sstatic.net/tgEJu.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/tgEJu.png" alt="enter image description here" /></a></p>
  
Tags: <form-processor><action-provider>
Title: Fatal error Form Processor and/or Action Provider
ThreadText: # Fatal error Form Processor and/or Action Provider
  
  (Asked by: username_0 on 2023-03-06)
  
  I've been using the fabulous Form Processor and Action Provider extensions for several months, and have built up a very useful suite of forms implemented in Google Forms and connected to various form processors in CiviCRM to execute actions. Everything was working great until today. Now, if I even try to access the Form Process menu item I get the error in the screenshot below. I've tried disabling this extension and also the Action Provider extension upon which it depends and then re-enabling both but that hasn't helped. The Action Provider was updated on 3rd March but I don't exactly know when this issue arose. Can anyone suggest any lines of inquiry / resolutions based on the screenshot below? Many thanks, Patrick.
  
  [![enter image description here](https://i.sstatic.net/tgEJu.png)](https://i.sstatic.net/tgEJu.png)
  
  **Tags:** form-processor, action-provider
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_0 on 2023-03-06. Score: 2
  
  The issue is resolved by disabling form processor and action provider, rolling action provider back to version 1.18, and re-enabling form processor. Apparently the update of action provider on 3rd March broke form processor, at least in my instance of CiviCRM on WordPress.
  
  
  ---
  
  