Answers.Body: <p>I think you are referring to the jquery blockUI which was enabled on the webform_civicrm payment page recently to prevent submission until the processor has actually loaded all it's fields?</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2019-03-16T22:10:52.067Z
Answers.LastActivityDate: 2019-03-16T22:10:52.067Z
Answers.UserDisplayName: Matthew Wire
Body: <p><strong>Specific Issue</strong>
  I have a View that contains a Views Block Area as one of its rows. In each of these Views Block Areas I have a Webform that contains a CiviCRM Payment Processor.</p>
  
  <p>I want the Payment Processor that is used to be set on content within the row.</p>
  
  <p>When I set this by Javascript I get a grey box appearing on the screen and disappearing. Google Chrome's Console shows the data is: form?currency=GBP&amp;snippet=4&amp;processor_id=[[index of the selected payment processor]]</p>
  
  <p>My Questions are:</p>
  
  <p>1) What is this for? What does it do?
  2) How can I get rid of it / stop it happening?
  3) Is there a better way other than javascript to do this? The only other thing I could think of was using views_post_render. That feels like using a sledgehammer to crack a nut.</p>
  
  <p><strong>Purpose</strong>
  I want to be able to have multiple donation options on the same screen for a crowd funding effort. These options are generated by a View. I am open to having a link instead of a payment form, and definitely open to a better way than using Views Block Areas in rows! </p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-03-14T04:55:11.410Z
Comments.Text: can you explain a bit more about why you need separate webforms for each payment processor? ie what does this achieve that fails just by offering 'user select' on the PP in a single webform?
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-03-14T09:54:37.930Z
Comments.Text: I think you are referring to the jquery blockUI which was enabled on the webform_civicrm payment page recently to prevent submission until the processor has actually loaded all it's fields?
Comments.UserDisplayName: Matthew Wire
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2019-03-15T13:42:15.743Z
Comments.Text: @MatthewWire If you answer the question with that I'll accept it :D
Comments.UserDisplayName: JohnFF
Tags: <payment-processor><drupal-views>
Title: What is the grey box on selecting Webform Payment Processor?
ThreadText: # What is the grey box on selecting Webform Payment Processor?
  
  (Asked by: username_0 on 2019-03-13)
  
  **Specific Issue**
  I have a View that contains a Views Block Area as one of its rows. In each of these Views Block Areas I have a Webform that contains a CiviCRM Payment Processor.
  
  I want the Payment Processor that is used to be set on content within the row.
  
  When I set this by Javascript I get a grey box appearing on the screen and disappearing. Google Chrome's Console shows the data is: form?currency=GBP&snippet=4&processor\_id=[[index of the selected payment processor]]
  
  My Questions are:
  
  1) What is this for? What does it do?
  2) How can I get rid of it / stop it happening?
  3) Is there a better way other than javascript to do this? The only other thing I could think of was using views\_post\_render. That feels like using a sledgehammer to crack a nut.
  
  **Purpose**
  I want to be able to have multiple donation options on the same screen for a crowd funding effort. These options are generated by a View. I am open to having a link instead of a payment form, and definitely open to a better way than using Views Block Areas in rows!
  
  **Tags:** payment-processor, drupal-views
  
  > **Comments:**
  > **username_1**: can you explain a bit more about why you need separate webforms for each payment processor? ie what does this achieve that fails just by offering 'user select' on the PP in a single webform?  
  > **username_2**: I think you are referring to the jquery blockUI which was enabled on the webform_civicrm payment page recently to prevent submission until the processor has actually loaded all it's fields?  
  > **username_0**: @MatthewWire If you answer the question with that I'll accept it :D  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_2 on 2019-03-16. Score: 1 | Accepted answer
  
  I think you are referring to the jquery blockUI which was enabled on the webform\_civicrm payment page recently to prevent submission until the processor has actually loaded all it's fields?
  
  
  ---
  
  