Just checking. Would be nice to have this, if only as part of managing an upgrade to D7.
| Comment | File | Size | Author |
|---|---|---|---|
| #13 | qa_checklist-1031710-13.patch | 53.98 KB | traviscarden |
| #12 | QA_Checklist-Port-1031710-12.patch | 6.76 KB | mgifford |
| #10 | qachecklist-upgrade-d7.patch | 6.13 KB | perfectweb |
| #6 | qachecklist_module_upgrade_d7-1031710-6.patch | 5.97 KB | mgifford |
Comments
Comment #1
mehtatejas commentedsubscribing
Comment #2
midmood commentedsubscribe
Comment #3
midmood commentedsubscribe
Comment #4
eidolon nightI've been busy lately, but I'll work on getting this up to D7 in the next couple months.
Comment #5
jakonore commentedsub
Comment #6
mgiffordOk.. Here's a patch. Seems to work fine for me.
Comment #7
mgiffordAnyone going to test this & put out a release?
Comment #8
perfectweb commentedI download the latest 6.x branch today and applied the patch in #6. After installing the module I was prompted with an error telling me that this module wasn't meant for Drupal 7.x.
I noticed that the .info file had two lots of version=7.x and version=6.x lines that were marked as being added by the drupal packaging script. Remove the lines related to 6.x and refreshing the modules page allowed me to enable the module successfully.
Once enabled the module appeared to work correctly.
Comment #9
mgiffordCan you roll a new patch with the correction?
Comment #10
perfectweb commentedHere is the patch that resolves the issue. This patch replaces the one in #6
Comment #11
traviscarden commentedComment #12
mgiffordOk, so this didn't install against git, so I re-rolled it.
But there are issues with the .install file when running through Coder:
Now not sure how much a fear there is of injection attacks from an .install file, but worth noting that it's not a best practice.
The other files seem fine.
Comment #13
traviscarden commentedGreat start, @mgifford. Here's another patch with the following changes:
qachecklisttoqa_checklist.) A 6.x to 7.x port, when nobody's using the major branch yet, seems like the perfect time to fix a schizophrenic project. :)qa_checklist_install()to define tasks in a (more readable, less redundant) array format, and replaceddb_query()calls withdrupal_write_record(), eliminating SQL injection vulnerability complaints from Coder.Comment #14
mgiffordI think it's missing the version number in the .info file. Think this should be
version = "7.x-3.0-dev"but that's a pretty trivial thing.This is good to go I think. Really to see many of the changes you brought in. It's a way more comprehensive patch than what I contributed.
I've tried to reach out to the developer.
Comment #15
traviscarden commentedThanks, @mgifford!
The version property is actually added by the drupal.org packaging system. Thus we are discouraged from including it manually.
Comment #16
mgiffordAhh.. Good to know.
Comment #17
traviscarden commentedGetting under the hood for this patch motivated me write an abstraction for QA Checklist and SEO Checklist to share. Please weigh in on #1571642: Re-implement on Checklist API?.
Comment #18
traviscarden commentedAll right! @Eidolon Night has kindly granted me maintainer rights to the checklist. I've completed the port and uploaded a release candidate. Please try it out (you'll need the new Checklist API) and provide feedback in the issue queue. If there are no bug reports in a few weeks, I'll make it a full release. Thanks for everyone's help!
UPDATE: I've created an issue to completely rethink the contents of the checklist. Please weigh in at #1645936: Re-invent QA Checklist.
Comment #19
mgiffordGreat to hear that there's a D7 version now & thanks for taking on the leadership to re-invent the module. Lots can be done with this for sure.