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

Simplify install database settings screen #216

Closed
markkap opened this Issue Jan 9, 2019 · 1 comment

Comments

Projects
None yet
1 participant
@markkap
Copy link

markkap commented Jan 9, 2019

The suggestion regarding DB usage is to have a different DB per site. For people that follow this advice, the table prefix setting is just noise during the install process.

Probably need to still have the option around, but show it only to people that host more than one site on the DB.

@markkap markkap added the install label Jan 9, 2019

@markkap markkap added this to the 1.0.0 milestone Jan 9, 2019

@markkap markkap changed the title Do not require the user to select a table prefix on install Simplify install database settings screen Mar 6, 2019

@markkap

This comment has been minimized.

Copy link
Author

markkap commented Mar 6, 2019

In addition to the prefix, the host is also a setting which most users will have a hard time to figure out, especially since for many hosting setups, especially VPS oriented, the answer is simply localhost. Both setting should be hidden by default and displayed only when the user specifically asks for it.

For the prefix itself, the default should be some random string which will make it easier to host multiple calmPress on the same DB.

Another thing that can be improved is to remove the pre-set values in the input fields. At best they require extra work to remove them, at worst they are causing confusion.

@markkap markkap added the UX label Mar 6, 2019

markkap added a commit that referenced this issue Mar 6, 2019

markkap added a commit that referenced this issue Mar 6, 2019

@markkap markkap closed this Mar 6, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.