Support

November 26, 2014 at 5:54 am

Thanks Dean. My client needs a solution in place by end of year. Does “soon” mean a couple weeks or a couple months?

December 4, 2014 at 9:50 am

Hi guys. I have another wrinkle. My client is ready to purchase EE4 (they’re just waiting on approval for their non-profit status). They want a set of custom fields for defining a separate Invoice contact, as described above. But they really want this to only be displayed AFTER the registering user selects the Invoice payment option.

I’ve been around and around with EED_Single_Page_Checkout.module.php and the associated gateways and models. But I’m really struggling to figure out how to accomplish this in a forward-compatible manner. I see three approaches:

1. Add a custom registration step by hooking into the FHEE__Single_Page_Checkout__setup_reg_steps_array__reg_steps filter. As far as I can tell, though, the process_func and display_func options have to reference methods within the EED_Single_Page_Checkout class. That limits my ability to extend them without tampering with the code itself.

2. If I have to, I can add a small hook into EE_Invoice::espresso_display_payment_gateways() to add the fields so that they appear when the user selects the Invoice option. However, I can’t for the life of me figure out where the form fields for payment options are actually processed and stored. The form (#spco-registration-payment_options-frm) has a setting which registers this payment type. Can you point me to where this occurs in the code? Ideally, I’d like to save the invoice information into the Billing Information section of the Transaction post.

3. Worst case scenario is that I just add the fields through the normal registration fields. Then I can hide them, reveal them and scroll to them when the user selects Invoice. This would do the trick, but I’d really prefer to keep the user’s focus in place.

I understand this is beyond a normal support request. I’m just hoping you might be able to point me to something I’ve missed in the code, particularly for #1 or #2. If you think one of your people could walk me through this in a 30-min chat, I’d happily buy a priority support ticket. I wouldn’t need everything spelled out, just some quick points on where to hook in and add these fields to the registration process.

Thanks.

December 4, 2014 at 2:37 pm

Hi Josh,

Thanks for the quick response. I’ll definitely sign up for GitHub access and look into 4.6 as soon as my client has made the purchase. (Do non-profit discount applications take very long?)

Do you know how stable Events Espresso 4.6 is at the moment? Normally I would jump on board without hesitation, but my client has a very tight deadline and this project needs to be implemented by December 22. So if EE 4.6 is still pretty rough, I unfortunately don’t have the time to hold off until it stabilizes.

December 10, 2014 at 7:46 am

How long does it take to get github access? I applied on Monday using my client’s username (qnis). I’d love to see what SPCO looks like in 4.6. My 4.4.6 hack is super ugly and fragile.

December 10, 2014 at 10:12 am

Thanks!