Community
Participate
Working Groups
This is using build 2002-04-12 When creating a new repository location, a dialog comes up to collect the necessary information. At the bottom there is a check box to validate on Finish. If the validate fails (say wrong user id), an information dialog comes up. 1) The message is too vague ("Invalid username, password, host, or repository"). Can it be more specific about which information is incorrect? 2) The "Keep location anyway?" with Yes/No is too confusing to understand. I keep hitting yes thinking it will keep the dialog box open so I can make changes, but it closes instead. Then I have a location which is broken but can't edit anymore. Instead of an information dialog, it should be an warning dialog. Also, it should just have the Ok button. I could then correct the info, or uncheck the validate option and hit finish.
1) The repository gives us back a very vague message... we can't tell what really happened because it doesn't tell us. 2) Keep location anyway is intended for cases where the server is just temporarily down, or you're working in a disconnected fashion and want to create a repository that you can't contact right now. We already have a separate PR asking for editable repository locations, which I plan to fix soon. The problem with just having an Ok button is that often the user needs to correct information immediately (because they mistyped it, for example), and forcing them to go hunting for it later is problematic.
1) I sort of figured that was the case :-( 2) Here is the flow I was proposing (probably not clear in my original message). The new repo location dialog opens up, user types in information, clicks finish. If all is well, close dialog. If validate fails, the show warning dialog with only OK button and drop sentence saying "Keep location anyway?". Upon reading the message, user clicks ok to dismiss warning dialog. Then user can either fix the problem right away (the repo location dialog is still open) and try again, or can uncheck validate option and hit finish again.
Suggested workflow has merit, but moving post 2.0
Reopening
This bug has not been touched in 2 years. Closing as WONTFIX. If you feel this bug is important, feel free to reopen it.
