Possible upgrade to version 6.x

v2egroup - July 22, 2008 - 23:33
Project:Signup Pay for a node
Version:5.x-1.x-dev
Component:Code
Category:support request
Priority:normal
Assigned:Unassigned
Status:needs review
Description

What is involved in upgrading this module to work with a 6.x site? Thanks, -Bill Franklin (bill@v2egroup.com)

#1

kbahey - July 23, 2008 - 02:38

This is a frequently asked question.

Also, remember that the module does not have a stable version for Drupal 5.x yet. This will happen when enough people test the existing code for features and bugs and declare it as stable-worthy. After that, a D6 version can proceed, via one of the avenues outlined in the link above.

#2

v2egroup - July 24, 2008 - 15:28

So, whats involved in upgrading it myself or having you upgrade it? I'm perfectly familiar with coding in PHP, but to "scratch my own itch," it would be helpful to have some hint of how big a job that is, or if you want to upgrade it/what you want in return. Feel free to email me directly, since I don't really have any other reason to check the drupal issues queue. Bill Franklin bill@v2egroup.com

#3

kbahey - July 24, 2008 - 16:06

Here is all the info you need for the conversion http://drupal.org/node/114774

#4

v2egroup - July 24, 2008 - 19:25

I had already found the coder module and started on my own. Converting signup, signup_paypal and simple_paypal. Done with simple_paypal. Should finish other two sometime today and then start testing. Any further advice? Thanks, -Bill

#5

kbahey - July 24, 2008 - 20:38

Before you start on other modules, check that you are not duplicating effort.

For example, simple_paypal is here http://drupal.org/node/280101

#6

v2egroup - July 25, 2008 - 13:06

Got it. That one still had errors from coder. Passed those on.

#7

kbahey - July 25, 2008 - 15:00

Do not rely solely on coder. Use it only as a starting point. There are many other things you have to do manually, like hook_menu() and all the theme stuff.

#8

v2egroup - July 25, 2008 - 23:05

Questions: What is the mechanism "connecting" signup and signup_pay? IE, what is supposed to cause signup_pay_do_payment to be called?

The relevant modules are: event, signup, signup_pay, simple_paypal.

I've got functioning ports of the modules merged from other sources (lots of testing and debugging there) and everything works fine when signup_pay is deactivated. Data in the tables for all the modules looks ok. All the right notices get sent.

When I activate singup_pay and try to signup for a test event, I get "You have registered but not yet paid for this event." I'm just not getting redirected from the signup form post to paypal and back.

Any hints would be greatly appreciated. Thanks.

#9

v2egroup - July 28, 2008 - 15:35

node->signup_pay_enabled is not set when entering signup_pay_form_alter even though it gets set correctly first in signup_pay_nodeapi. The value is not in the form parameters (I've printed them out), so there's no value to check when you get there. Basically, even though nodeapi sets signup_pay_enabled, it is not getting on the form to then be available when $node = $form['#parameters'][1];

#10

kbahey - July 28, 2008 - 15:47

Is this $node stuff related to upgrading to D6, or a separate issue? Please do not mix issues by going off topic. Open a new issue if need be.

#11

v2egroup - July 28, 2008 - 15:53

This looks like a separate issue.

#12

greggles - November 15, 2008 - 19:15

Marked #280346: D6 update? as a duplicate. Also, signup is now in RC status of being ported to 6.x so this should be easier.

#13

greenbeans - April 6, 2009 - 23:53

I could really use this right about now, too. I'd be very glad to contribute to the effort, but the module is too unfamiliar for me to tackle the whole thing myself. Anyone interested in teaming up?

#14

mdowsett - April 30, 2009 - 18:37

I'd love to help as I really need this as well. All I can do is help with testing tho (and maybe minor coding)

#15

UnderDesign - May 1, 2009 - 10:53

Just flagging this to subscribe as also need this quite quickly

#16

capellic - June 3, 2009 - 19:22

@v2egroup - Any luck getting this to work? There doesn't seem to be another option out there for Drupal 6.

#17

greggles - June 4, 2009 - 00:15

Well, it's brand new and may not be perfect, but for those willing to use Ubercart there is now http://drupal.org/project/uc_signup

#18

turadg - June 7, 2009 - 11:48

+1 subscribe

#19

capellic - June 8, 2009 - 15:44

I tried to contact v2egroup to see if he made any progress he could share, but I haven't heard back. I have started to convert the module, but it's slow going because I've never done this before. I will post my results here.

#20

capellic - July 7, 2009 - 01:50
Status:active» needs review

I rolled up my sleeves and ported signup_pay to Drupal 6! It by no means is rigorously tested, but I thought I would post it in case someone really needs it. I was on a b-line to get it to work with signup_status and simple_paypal. The code is still full of Deadwood comments and areas where I still have questions. Here are the enhancements:

My decisions have been biased towards the anonymous user

Added email address to the User column for Anonymous users.

Added text at the top of the Signup pay list page /admin/content/signup_pay to indicate that the Name column was the name on the PayPal account.

Updated the node title in the Event column to link to the signups/admin page for the node.

I wanted an admin to have the option of getting an email notification every time somebody paid. I added a field to the signup_pay configuration screen, "Notification Email Address". The default is the variable.site_mail field.

Problem with IPN hitting the IPN URL more than once and logging multiple payments. Apparently something is being returned to PayPal to make it think that there was a 500 Error. You can see this if you test the IPN handshake from PayPal's sandbox. While best to figure out why this is happening, it was also important to be sure that multiple payments were not logged for the same transaction. To solve this:

1. Add a field to the database "transaction_id"
2. Write the transaction id to signup_pay
3. Add check for transaction ID and then don't write the transaction if it exists.

I am using the signup_status module in conjunction with signup_pay. Signup Pay has functionality to update the status of the signup once PayPal's IPN gives us the go ahead. But, the 6.x version of signup_status doesn't have have the API function that signup_pay 5.x was relying on. For the meantime, signup_pay is running the query directly against the signup_log table. I have logged an issue with Signup Status to ask for an API: http://drupal.org/node/508294

AttachmentSize
simple_paypal.zip 3.38 KB

#21

capellic - July 7, 2009 - 01:53

Brilliant, so I uploaded the WRONG zip file in #20 and I can't delete it. The correct one is below.

AttachmentSize
signup_pay.zip 20.65 KB

#22

remotenemesis - October 5, 2009 - 23:28

capellic, thanks for your work on this.

I think I have everything setup correctly, however, none of the changes I make in the "Signup Payment" sub-form of my content appear to be saved anytime I make changes. When I sign up for an event, I am not presented with an option to pay and I am told that I have registered but not paid for this event.

Any ideas what I should check?

Thanks again!

#23

espirates - October 11, 2009 - 02:59

Same here, the form on the node is not saving anything, inparticular Enable signup payment options for this node? is not sticking.

#24

hugafish - October 24, 2009 - 14:49

subscribing

#25

grguth - November 26, 2009 - 18:41

subscribing - may be able to help after the 1st of 2010

 
 

Drupal is a registered trademark of Dries Buytaert.