I am extremely interested in this module, or a similar one, for my site, in which users will be filling out forms over the course of several hours, with timestamps for each revision to the form until it is submitted, as they accomplish activities, and the form cannot be broken up into multiple submissions, because of the technical illiteracy of the user to be able to manage that many forms. (sorry for the huge sentence, there's a reason I chose Programming over English classes). So saving a content type as a draft is as close to essential as I can get with this.
What is/are the opinion(s) from this module's developers of how difficult the d7 port will be? Perhaps in terms of time? I'm new to Drupal and php, and pretty much web dev in general but I'm learning extremely quickly. I am only just now learning d7, but I have several development servers at my fingertips, so if any testing would be useful to you in speeding up the port, I am interested in helping.
Also if you think another module would better suit my needs, I'm all ears, and I recognize this isn't likely because I've probably been too vague about what I'm doing, but it doesn't hurt to throw out there that I'm open to other modules as well, my needs aren't exactly set in stone, as I'm still working with the client on what they need.
Thanks, I seem to have overlooked that one. The module you suggested seems to be alright, though I'm not too wild about this publish/unpublish functionality, but that's for me to deal with for that module. I'll still be watching out for the d7 port of this module though :)
Hi darren.ferguson,
I am importing this module to D7 version. Completed the saving of draft and currently working on the draft_views part which is related to the views integration.
I will soon be uploading the code here for review by the community.
The above zip folder contains test file (mod_draft.module). I removed that and uploading again. Please review the drupal 7 version of the draft module.
4. git branch -a
Gave the following result
*6.x-1.x remotes/origin/6.x-1.x
remotes/origin/HEAD -> origin/master
remotes/origin/master
Next command is:
git checkout [branchname]
Out of 3(mentioned in bold letters) which one has to use, Instead of [branchname]. How can I copy my new files(D7 version files)?
In dealing with most projects the code to follow is HEAD. This is usually the default, but not always.
I usually do steps 1 & 2 and just as you have described.
Since you've already got a working set of files I'd just copy them over, so step 3 would be:
3. cp -r ../my_version_of_draft/* .
And then you'd want to create the patch, ideally with a file name that follows [description]-[issue-number]-[comment-number].patch:
4. git diff > D7_upgrade-1120336-16.patch
Then upload it here and set the project status to needs review. There must be simpler descriptions though somewhere else...
Hi,
I am uploading D7 version patch for draft(D6) module. Please review this module.
While adding content in D7 version by enabling draft module, some notices are coming as below (After adding content click on the "Save as draft" button, close the layer window and refresh the page. now we can see the following notices)
* Notice: Array to string conversion in drupal_attributes() (line 2264 of C:\wamp\www\drupal7\includes\common.inc).
* Notice: Array to string conversion in drupal_attributes() (line 2264 of C:\wamp\www\drupal7\includes\common.inc).
So I am trying to resolve this. If any one wants to resolve this notices, please do the needful.
Ran it through coder and: Coder found 2 projects, 22 files, 41 normal warnings, 0 warnings were flagged to be ignored
One of them might affect translation Javascript strings should be passed through Drupal.t(). The rest are pretty trivial, but should still be taken care of.
Comments
Comment #1
AtomicTangerine commentedI am extremely interested in this module, or a similar one, for my site, in which users will be filling out forms over the course of several hours, with timestamps for each revision to the form until it is submitted, as they accomplish activities, and the form cannot be broken up into multiple submissions, because of the technical illiteracy of the user to be able to manage that many forms. (sorry for the huge sentence, there's a reason I chose Programming over English classes). So saving a content type as a draft is as close to essential as I can get with this.
What is/are the opinion(s) from this module's developers of how difficult the d7 port will be? Perhaps in terms of time? I'm new to Drupal and php, and pretty much web dev in general but I'm learning extremely quickly. I am only just now learning d7, but I have several development servers at my fingertips, so if any testing would be useful to you in speeding up the port, I am interested in helping.
Also if you think another module would better suit my needs, I'm all ears, and I recognize this isn't likely because I've probably been too vague about what I'm doing, but it doesn't hurt to throw out there that I'm open to other modules as well, my needs aren't exactly set in stone, as I'm still working with the client on what they need.
Comment #2
vm commentedhttp://drupal.org/project/save_draft = a simplier (by design) method for creating draft nodes.
Comment #3
AtomicTangerine commentedThanks, I seem to have overlooked that one. The module you suggested seems to be alright, though I'm not too wild about this publish/unpublish functionality, but that's for me to deal with for that module. I'll still be watching out for the d7 port of this module though :)
Comment #4
vm commentedfor D7 more complex workflows (which can include drafts) can be accomplished with rules and the NKOTB, maestro.
Comment #5
AtomicTangerine commentedum.. what is NKOTB? I only know that acronym for a band....
Comment #6
vm commentedNew Kid On The Block = the saying from where the boy band you refer to took their name.
Comment #7
AtomicTangerine commentedhaha thanks, gotcha now
Comment #8
srivalli commentedHi darren.ferguson,
I am importing this module to D7 version. Completed the saving of draft and currently working on the draft_views part which is related to the views integration.
I will soon be uploading the code here for review by the community.
Comment #9
srivalli commentedHi,
I am uploading the D7 version of the draft module. Please review it.. In content adding page i am getting warnings, I am trying to fix them.
Comment #10
srivalli commentedThe above zip folder contains test file (mod_draft.module). I removed that and uploading again. Please review the drupal 7 version of the draft module.
Comment #11
mgifford@srivalli do you need help rolling a patch? That's generally the way that code is reviewed & then brought into a project.
Did you run it through Coder to review it? Not sure how good the D6 code is when reviewed with Coder.
Anyways, most important thing, thanks! Hopefully we can help move this to a release soon.
Comment #12
srivalli commentedYes @mgifford,
I need some one help to rolling the patch of this module. I run the code through coder module while upgrading to D7.
Comment #13
mgiffordHave you looked at the description here?
http://drupal.org/node/306118/git-instructions
You can probably just pull down the git implementation and then copy over your new files over the ones you pulled down from git.
Comment #14
srivalli commentedHi mgifford,
I installed Git and did the following instructions which are given in the link "http://drupal.org/node/306118/git-instructions"
1. git clone --branch 6.x-1.x http://git.drupal.org/project/draft.git
2. cd draft
3. git status
4. git branch -a
Gave the following result
*6.x-1.x
remotes/origin/6.x-1.x
remotes/origin/HEAD -> origin/master
remotes/origin/master
Next command is:
git checkout [branchname]
Out of 3(mentioned in bold letters) which one has to use, Instead of [branchname]. How can I copy my new files(D7 version files)?
Regards,
Srivalli
Comment #15
mgiffordIn dealing with most projects the code to follow is HEAD. This is usually the default, but not always.
I usually do steps 1 & 2 and just as you have described.
Since you've already got a working set of files I'd just copy them over, so step 3 would be:
3. cp -r ../my_version_of_draft/* .
And then you'd want to create the patch, ideally with a file name that follows [description]-[issue-number]-[comment-number].patch:
4. git diff > D7_upgrade-1120336-16.patch
Then upload it here and set the project status to needs review. There must be simpler descriptions though somewhere else...
Comment #16
srivalli commentedHi,
I am uploading D7 version patch for draft(D6) module. Please review this module.
While adding content in D7 version by enabling draft module, some notices are coming as below (After adding content click on the "Save as draft" button, close the layer window and refresh the page. now we can see the following notices)
* Notice: Array to string conversion in drupal_attributes() (line 2264 of C:\wamp\www\drupal7\includes\common.inc).
* Notice: Array to string conversion in drupal_attributes() (line 2264 of C:\wamp\www\drupal7\includes\common.inc).
So I am trying to resolve this. If any one wants to resolve this notices, please do the needful.
Regards,
Srivalli
Comment #17
mgiffordSome minor whitespace errors in that patch.
Ran it through coder and:
Coder found 2 projects, 22 files, 41 normal warnings, 0 warnings were flagged to be ignoredOne of them might affect translation
Javascript strings should be passed through Drupal.t(). The rest are pretty trivial, but should still be taken care of.Comment #18
dan_metille commentedAny news on this? Could the #16 patch be updated?
Many thanks.
Comment #19
mgiffordI think it might be time to call for a new maintainer. Anyone want to take on the job?
@darren.ferguson hasn't posted for a while on d.o... Hopefully he can be re-engaged, but doesn't seem to be at the moment.
There was an page somewhere describing this process, but it was too long ago.. Anyone know where it is?
Comment #20
okeedoak commentedDealing with unsupported (abandoned) projects