Body: <p>Using Civi 4.6.18 with Wordpress, we have event registrations working smoothly using the Paypal Website Payments Standard payment processor. The next stage is to get memberships up and running and we want to use Veda's UK Direct Debit/GoCardless payment processor to facilitate recurring membership payments.</p>
  
  <p>However, as soon as I enable the Direct Debit extension (I've not configured it yet and it's not been enabled on any contribution pages), my event contribution pages, which are set up to use Paypal, stop working correctly because the billing block is no longer being displayed as it should be when the user chooses the 'pay later' option. As a result the user is faced with validation errors that they can't fix.</p>
  
  <p>If I disable the direct Debit extension, my Paypal event registration form works as it should.</p>
  
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-17T05:46:16.560Z
Comments.Text: For information I've also posted this as an issue on the extension's GitHub page: https://github.com/veda-consulting/uk.co.vedaconsulting.payment.ukdirectdebit/issues/50
Comments.UserDisplayName: Graham
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-17T15:08:03.810Z
Comments.Text: You mention version 4.6.x - but which one?  There have been many changes to billing block logic in the 4.6.x series.  Do you have the same problem with the latest version of 4.6?
Comments.UserDisplayName: Jon G - Megaphone Tech
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-18T07:54:35.630Z
Comments.Text: I should have been more precise. We are running 4.6.18, and seeing the issue as described. I'll edit the question accordingly.
Comments.UserDisplayName: Graham
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-18T08:10:03.550Z
Comments.Text: Graham - just for completeness - which version of gocardless? also i think there are some patches on their way for improving it with memberships. You may want to raise an issue on their github?
Comments.UserDisplayName: petednz - fuzion
Comments.ContentLicense: CC BY-SA 3.0
Comments.CreationDate: 2016-07-18T08:30:00.450Z
Comments.Text: Hi Pete: I didn't even get to the point where the GoCardless extension was installed. All I did was install and enable the base Direct Debit extension, so I logged the issue there.
Comments.UserDisplayName: Graham
Tags: <civicontribute><payment-processor><paypal><billingblock><paylater>
Title: Is it possible to run the UK Direct Debit/GoCardless payment processor alongside Paypal Website Payments Standard?
ThreadText: # Is it possible to run the UK Direct Debit/GoCardless payment processor alongside Paypal Website Payments Standard?
  
  (Asked by: username_0 on 2016-07-17)
  
  Using Civi 4.6.18 with Wordpress, we have event registrations working smoothly using the Paypal Website Payments Standard payment processor. The next stage is to get memberships up and running and we want to use Veda's UK Direct Debit/GoCardless payment processor to facilitate recurring membership payments.
  
  However, as soon as I enable the Direct Debit extension (I've not configured it yet and it's not been enabled on any contribution pages), my event contribution pages, which are set up to use Paypal, stop working correctly because the billing block is no longer being displayed as it should be when the user chooses the 'pay later' option. As a result the user is faced with validation errors that they can't fix.
  
  If I disable the direct Debit extension, my Paypal event registration form works as it should.
  
  **Tags:** civicontribute, payment-processor, paypal, billingblock, paylater
  
  > **Comments:**
  > **username_0**: For information I've also posted this as an issue on the extension's GitHub page: https://github.com/veda-consulting/uk.co.vedaconsulting.payment.ukdirectdebit/issues/50  
  > **username_1**: You mention version 4.6.x - but which one?  There have been many changes to billing block logic in the 4.6.x series.  Do you have the same problem with the latest version of 4.6?  
  > **username_0**: I should have been more precise. We are running 4.6.18, and seeing the issue as described. I'll edit the question accordingly.  
  > **username_2**: username_0 - just for completeness - which version of gocardless? also i think there are some patches on their way for improving it with memberships. You may want to raise an issue on their github?  
  > **username_0**: Hi Pete: I didn't even get to the point where the GoCardless extension was installed. All I did was install and enable the base Direct Debit extension, so I logged the issue there.  
  
  ---
  
  ## 0 answers
  
  