Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

wgd config - Bad parameter provided. #19

Open
knowmad opened this issue Apr 6, 2011 · 4 comments
Open

wgd config - Bad parameter provided. #19

knowmad opened this issue Apr 6, 2011 · 4 comments

Comments

@knowmad
Copy link
Contributor

knowmad commented Apr 6, 2011

While trying to set my commands, I mistyped one of the config options. Now I keep getting the error and cannot find a way to reset the config or remove that setting. If there is a way to find out where the config file is being stored, I haven't seen it. My wgd is fubared until this is resolved :(.

@haarg
Copy link
Owner

haarg commented Apr 6, 2011

What was the command you ran that caused the issue?

The config file is stored at $ENV{HOME}/.wgdevcfg

@knowmad
Copy link
Contributor Author

knowmad commented Apr 6, 2011

I meant to set the root and ran the following:

wgd config command.webgui_config /data/WebGUI

BTW, I couldn't find that path to the config file documented anywhere and because of the error, I couldn't re-set the value. I've fixed the erroneous entry by editing the config to be the name of the site. I now have wgdev working correctly.

Thanks,
William

@knowmad knowmad closed this as completed Apr 6, 2011
@haarg haarg reopened this May 10, 2011
@sbaur
Copy link

sbaur commented Oct 20, 2011

This just got me as well. Had to hand edit ~/.wgdevcfg to fix it

@haarg
Copy link
Owner

haarg commented Nov 7, 2011

There's a number of things that should be done that would help with this:

  1. Options pulled from the config file should probably be ignored if they are invalid.
  2. Commands that don't need a WebGUI root or config file should allow invalid root/config options to be specified.
  3. There should be an option to ignore the wgdevcfg file
  4. The documentation should be improved so that people don't make this error

I've started working on issue 6, which is the first step to doing #3. #1 and #2 are probably the most helpful things, but they are significantly harder to fix. sbaur suggested better examples for the documentation, so I'll work on that when I get a chance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants