Agreement Drupal 7 port

Rewrote patch, branched from git master (latest master changes).

• All tests pass
• Manual check of agreement functionality
• Didn't test views

Oh, I somehow deleted the hook_install(). Probably need to revert that.

There we go... updated to dbtng for that as well. (this patch is a commit ahead of the last patch)

subscribe

Maybe they want to see who didn't agree? I don't plan on using it.

@good_man, I've been keeping an eye on this issue, don't worry :). I'll review the D7 port and publish it as soon as I get a chance; hopefully sometime this week.

subscribe

I'm also looking forward to when this module will be ported and released as a Drupal 7 module.
In the meantime, there is another way to have a make-shift User's Agreement, which I've described here: http://drupal.org/node/1180404.

Best Wishes,
Stephen

Old patches needed to be re-rolled and I was also experiencing some problems related to the input format. Here is a consolidated patch from the above ones. There is one difference which is I removed input format filter stuff on the agreement text because I could not get it to work properly, other than that I have it running on D7 without problem so far.

Here are updated git patches. I rebased from the branch I have, and then a couple of additional commits to fix things like the text format on agreement text. I tested that they applied to origin/6.x-2.x branch.

git clone --branch 6.x-2.x http://git.drupal.org/project/agreement.git 
cd agreement
git checkout -b 7.x-2.x
tar zxf agreement-7.x-patches.tar.gz
git am *.patch

Oops, another fix there.

Argh, file didn't actually attach. :(

Any chance we can have access to a public release? (no git knowledge needed). Perhaps you can give access to mradcliffe to upload as pre-apha or what ever name seem reasonable, that way as D7 users can move forward from patch on a thread.

Thanks in advance!

Hi. Please can someone post the full 7.x version, as I could not get it out of git. Thanks.

I'm getting ready to roll a Drupal 7 release but the patches in #16 won't apply (errors starting with #3).

That looks like it's because I rebased to 6.x-2.x branch seeing Yuriy's last commit.

I rebased my local dev branch back to origin/master and generated new patches. It also includes Yuriy's "temp commit" patch from last year (rebasing injects into a branch's history to maintain it).

Here's a straight git diff patch, but this won't maintain any history so you can't cherry pick the commits. It would be useful looking at all the changes at once.

Patches in #20 committed and dev release published. All tests pass. Thanks much mradcliffe & good_man!

Follow-up question. When submitting patches to you should I submit via the 7.x-2.x branch and create a backport to 6.x-2.x branch as well? Or base it off of the master branch, 7.x-2.x branch, and then 6.x-2.x branch?

If you could base them off the 7.x-2.x branch that would be great. Backporting to 6.x-2.x would be a bonus! I've removed the master branch. Thanks much...