Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.The special users should have CVS accounts, since some CVS-related functionality (e.g. the CVS access tab) depends on CVS accounts. Perhaps auth1 should have an account and auth2 should not, to ensure it's easy to test stuff in both cases.
| Comment | File | Size | Author |
|---|---|---|---|
| #3 | do_testing_cvs_accounts.patch_2.txt | 1.93 KB | dww |
| #2 | do_testing_cvs_accounts.patch_1.txt | 2.13 KB | dww |
| #1 | do_testing_cvs_accounts.patch.txt | 1.63 KB | dww |
Comments
Comment #1
dwwI needed this to debug http://drupal.org/node/161552 so I wrote it. ;) Attached patch isn't 100% beautiful (just doing a direct DB insert, not drupal_execute()) but it works like a charm.
Comment #2
dwwNew version using drupal_execute() on the cvs_account_import form. I don't like how the output is handled by cvs_account_import_submit(), since it does a drupal_set_message() with a header and that makes things look a little weird. :( Not sure this is really an improvement, but hunmonk wanted it. ;)
Comment #3
dwwAnd here's another version of the original, non-drupal_execute() patch with the fixed comment for D_O_NUM_CVS_USERS_PER_ROLE.
Comment #4
hunmonk commentedi like #3 better as well, now that i've seen the options :)
let's go with that one.
Comment #5
dwwCommitted #3 to HEAD. Thanks for the review. ;)
Comment #6
(not verified) commented