Port Signup Status Certificates to D6

Not sure if it affects the workflow in any way either

signup_status_cert is a completely optional add-on submodule that hasn't yet been ported to D6. I believe someone at Arizona State University (ASU), is working on the port, so they might provide a patch here. However, this is hardly critical -- signup_status_cert is pretty obscure -- I doubt anyone *other* than ASU (the folks who originally wrote it) actually cares about the functionality it provides. Please see modules/signup_status_cert/README.txt for more info.

Certificates are one of the very, very useful features of the signup status module for us (in D5). We're not looking to move to D6 until summer 2010, but it's a common need in education to grant such certificates and saves a lot of staff time! Maybe we're the only other ones who care, but I thought I'd let you know there's at least one more :)

It won't become a priority until summer, but maybe the port is something we can help to support.

Just wanted to point out there is a patch for this on an issue marked as a duplicate: #581530: Port of Signup Status Cert to Drupal 6.x-1.x.

I've attached the patch from user don1one here.

Marking as "needs review."

@mlsamuelson Thank You for the link / patch

It is not an obscure module.

I tried to apply the patch to the module but got an error. Patch sent this to the rejected output file;
I was trying to apply it to "signup_status-6.x-1.0-alpha2.tar.gz"

***************
*** 1,4 ****
  ; $Id: signup_status_cert.info,v 1.2 2009/01/12 18:10:26 jrbeeman Exp $
- name = "Signup Status Certificates"
- description = "Allow signup-enabled node creators to grant users a certificate when they 'complete' a signup."
- dependencies = signup_status token--- 1,11 ----
  ; $Id: signup_status_cert.info,v 1.2 2009/01/12 18:10:26 jrbeeman Exp $
+ name = Signup Status Certificates
+ description = Allow signup-enabled node creators to grant users a certificate when they 'complete' a signup.
+ dependencies[] = signup_status 
+ dependencies[] = token
+ ; Information added by drupal.org packaging script on 2009-05-12
+ version = "6.x-1.x-dev"
+ core = "6.x"
+ project = "signup_status"
+ datestamp = "1242087451"
+ 

I see that this patch is trying to patch both the .install and the .module file, seems like it was meant for an early version?

Here is a reroll against the latest dev version. I'll report after some more testing.

Sorry, I missed the .info hunk.

Hello,

I have downloaded the patch and tried applying it to the module but it wont load the sub module. I am new to drupal and I am not exaclty sure how this patch works so let me explain what I did to see if that was correct or not. I took the code that was provided in the patch and copied over the code in the signup_status_cert/signup_status_cert.module. I then uploaded the files and went to enable the module but it still shows as not compatable with Drupal 6. So like I said I really do not know if the problem is with how I tried to apply the patch or if the patch is not compatible with this version of Drupal. We are using the latest version of Drupal 6.26.

Any help or thoughts would be really appreciated.

Probably you did not patch the .info file which contains the information about core compatibility. Try to avoid manually patching the source code, here's a tutorial that should help you: http://drupal.org/patch/apply.

Well it looks like i was doing it wrong but I still can not seem to get it right. I tried command line patch. I put the .patch file in the signup_status module folder located at /sites/all/modules From there I ran the patch -p1 < signup_status_cert-557810-10.patch" command. This command ran but had this error.

patch -p1 < signup_status_cert-557810-10.patch
patching file modules/signup_status_cert/signup_status_cert.info
Hunk #1 FAILED at 1.
1 out of 1 hunk FAILED -- saving rejects to file modules/signup_status_cert/signup_status_cert.info.rej
patching file modules/signup_status_cert/signup_status_cert.install
Hunk #1 succeeded at 2 with fuzz 1 (offset 1 line).
patching file modules/signup_status_cert/signup_status_cert.module
Hunk #1 succeeded at 2 with fuzz 2 (offset 1 line).
Hunk #3 succeeded at 129 (offset 1 line).
Hunk #5 succeeded at 162 (offset 1 line).
Hunk #7 succeeded at 397 (offset 1 line).
Hunk #9 succeeded at 478 (offset 1 line).
Hunk #11 succeeded at 520 (offset 1 line).
Hunk #13 succeeded at 616 (offset 1 line).
Hunk #15 succeeded at 658 (offset 1 line).
Hunk #17 succeeded at 919 (offset 1 line).
[root@ip-184-168-71-194 signup_status]# 

I went and looked to see if that did not matter but drupal still does not recognize the module. I went into the module/signup_status_cert folder and there are orig files for all the files and one signup_status_cert.info.rej file the contents of which are this:

***************
*** 1,4 ****
  name = "Signup Status Certificates"
  description = "Allow signup-enabled node creators to grant users a certificate when they 'complete' a signup."
  package = Signup
- dependencies = signup_status token
--- 1,6 ----
  name = "Signup Status Certificates"
  description = "Allow signup-enabled node creators to grant users a certificate when they 'complete' a signup."
  package = Signup
+ core = 6.x
+ dependencies[] = signup_status 
+ dependencies[] = token

Any thoughts or help. I have never doen a patch so it is all new to me. But Hopefully it is not that difficult to figure out.

Your are trying to patch the 1.4 version while the patch is rolled against the repository HEAD version which has no version information in the .info file. Therefore the .info hunk of the patch does not apply and core compatibility is not updated. Try to append the following lines to signup_status_cert.info manually:

core = 6.x
dependencies[] = signup_status
dependencies[] = token

I didn't realize Signup status had a certificate module…

At this point it might make more sense to integrate with the Certificate module. That comes with a module called Signup certificate which does something very similar.

Certificate module is a bit more robust, with user group (and other) certificate mapping, and does not have hard-coded dompdf requirements etc.

The 2.x branch is where new features are added, so if there's anything missing for what Signup status needs, please let us know!