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

require_activation now defaults to false, update and clarify README #534

Merged
1 commit merged into from
Oct 31, 2022

Conversation

aghoulcoder
Copy link
Contributor

@aghoulcoder aghoulcoder commented Oct 16, 2022

Previously, require_activation was set to true by default, resulting in this warning message:

RequireActivation is set to true, but the following required settings are missing: EmailFrom, EmailHost, HostURL

Default behavior producing warning or error messages is confusing and should not happen. The only benefit of defaulting to true is if the error message helps point to the additinal settings. But a better way to inform the user is to clarify it in the README.

Previously, require_activation was set to true by default, resulting in
this warning message:

RequireActivation is set to true, but the following required settings are missing: EmailFrom, EmailHost, HostURL

Default behavior producing warning or error messages is confusing and
should not happen. The only benefit of defaulting to true is if the
error message helps point to the additinal settings. But a better way to
inform the user is to clarify it in the README.
@ghost ghost merged commit 9f873df into stashapp:master Oct 31, 2022
@aghoulcoder aghoulcoder deleted the require-activation-false branch October 31, 2022 22:58
InfiniteStash pushed a commit that referenced this pull request Nov 9, 2022
…534)

Previously, require_activation was set to true by default, resulting in
this warning message:

RequireActivation is set to true, but the following required settings are missing: EmailFrom, EmailHost, HostURL

Default behavior producing warning or error messages is confusing and
should not happen. The only benefit of defaulting to true is if the
error message helps point to the additinal settings. But a better way to
inform the user is to clarify it in the README.
InfiniteStash pushed a commit that referenced this pull request Nov 9, 2022
…534)

Previously, require_activation was set to true by default, resulting in
this warning message:

RequireActivation is set to true, but the following required settings are missing: EmailFrom, EmailHost, HostURL

Default behavior producing warning or error messages is confusing and
should not happen. The only benefit of defaulting to true is if the
error message helps point to the additinal settings. But a better way to
inform the user is to clarify it in the README.
Maista6969 pushed a commit to Maista6969/stash-box that referenced this pull request Jun 24, 2023
…tashapp#534)

Previously, require_activation was set to true by default, resulting in
this warning message:

RequireActivation is set to true, but the following required settings are missing: EmailFrom, EmailHost, HostURL

Default behavior producing warning or error messages is confusing and
should not happen. The only benefit of defaulting to true is if the
error message helps point to the additinal settings. But a better way to
inform the user is to clarify it in the README.
feederbox826 pushed a commit to feederbox826/stash-box that referenced this pull request Nov 15, 2023
…tashapp#534)

Previously, require_activation was set to true by default, resulting in
this warning message:

RequireActivation is set to true, but the following required settings are missing: EmailFrom, EmailHost, HostURL

Default behavior producing warning or error messages is confusing and
should not happen. The only benefit of defaulting to true is if the
error message helps point to the additinal settings. But a better way to
inform the user is to clarify it in the README.
This pull request was closed.
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

Successfully merging this pull request may close these issues.

1 participant