Tickets :: [#12997] horde-remove-user-data: accept command line paramaters

6.0.0-RC7

6/23/26

History
Attachments
Comment
Watch
Download

Summary	horde-remove-user-data: accept command line paramaters
Queue	Horde Base
Queue Version	Git master
Type	Enhancement
State	Resolved
Priority	1. Low
Owners	slusarz (at) horde (dot) org
Requester	skhorde (at) smail (dot) inf (dot) fh-bonn-rhein-sieg (dot) de
Created	2/27/14 (4499 days ago)
Due
Updated	6/9/14 (4397 days ago)
Assigned
Resolved	6/9/14 (4397 days ago)
Milestone
Patch	Yes

5210	Git Commit	Comment #7	Reply to this comment
Changes have been made in Git (master): commit 2a5e3d9d8a931c8be127201e238344694c55348a Author: Michael M Slusarz <slusarz@horde.org> Date: Mon Jun 9 16:30:13 2014 -0600 ~~Request #12997~~: Improved user deletion script horde/bin/horde-remove-user-data \| 80 ++++++++++++++++++++++++++++++------- 1 files changed, 65 insertions(+), 15 deletions(-) http://github.com/horde/horde/commit/2a5e3d9d8a931c8be127201e238344694c55348a

1510	Michael Slusarz	Comment #6 Assigned to Michael Slusarz State ⇒ Resolved	Reply to this comment
Edited and applied to Horde 5.2. Thanks.

3910	Michael Slusarz	Deleted Original Message

3310	Michael Slusarz	Deleted Original Message

2710	Michael Slusarz	Deleted Original Message

2312	skhorde (at) smail (dot) inf (dot) fh-bonn-rhein-sieg (dot) de	Comment #5 New Attachment: h5_horde-remove-user-data_horde-argv.diff.bz2	Reply to this comment
[Show Quoted Text - 9 lines][Hide Quoted Text] Please don't use print, use $cli->writeln() instead. And please use the spacing rules from our coding standards. I have updated the patch: + catch exceptions per user + let the use select with --continue option whether to terminate the script on exception or not + display username if to remove an user failed + use command line processing found in horde-vfs changed to use Horde_Argv_Parser as found inhorde-db-migrate + tried to comply with http://www.horde.org/apps/horde/docs/CODING_STANDARDS

311	skhorde (at) smail (dot) inf (dot) fh-bonn-rhein-sieg (dot) de	Comment #4 New Attachment: h5_horde-remove-user-data_argv.diff.bz2	Reply to this comment
Please don't use print, use $cli->writeln() instead. And please use the spacing rules from our coding standards. I have updated the patch: + catch exceptions per user + let the use select with --continue option whether to terminate the script on exception or not + display username if to remove an user failed + use command line processing found in horde-vfs + tried to comply with http://www.horde.org/apps/horde/docs/CODING_STANDARDS

134	skhorde (at) smail (dot) inf (dot) fh-bonn-rhein-sieg (dot) de	Comment #3 New Attachment: horde-remove-user-data_commandline.diff.bz2	Reply to this comment
Please don't use print, use $cli->writeln() instead. And please use the spacing rules from our coding standards. Here you go.

1610	Jan Schneider	Comment #2 State ⇒ Feedback Version ⇒ Git master	Reply to this comment
Please don't use print, use $cli->writeln() instead. And please use the spacing rules from our coding standards.

468	skhorde (at) smail (dot) inf (dot) fh-bonn-rhein-sieg (dot) de	Comment #1 State ⇒ New New Attachment: horde-remove-user-data.argv.diff.bz2 Patch ⇒ Yes Milestone ⇒ Queue ⇒ Horde Base Summary ⇒ horde-remove-user-data: accept command line paramaters Type ⇒ Enhancement Priority ⇒ 1. Low	Reply to this comment
Attached patch adds processing of command line arguments to the script: horde-remove-user-data [--force] [user...] If no user is given, one is prompted for one. If one user is specified, no prompt for users neither for the application are displayed. --force skips the yes/no prompt Please rewrite the help screen :-)