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

When a database connection error occurs, there is no way to report actual error #3182

Closed
netniV opened this issue Jan 12, 2020 · 0 comments
Closed
Assignees
Labels
enhancement General tag for an enhancement resolved A fixed issue
Milestone

Comments

@netniV
Copy link
Member

netniV commented Jan 12, 2020

Describe the bug
Releated to #3181, if a fatal database connection occurs, it would be useful to be able to display the errors being seen. However, this should be operated by a flag so that normal users do not see these by default.

@netniV netniV self-assigned this Jan 12, 2020
@netniV netniV added the enhancement General tag for an enhancement label Jan 12, 2020
@netniV netniV added this to the v1.2.9 milestone Jan 12, 2020
netniV added a commit that referenced this issue Jan 12, 2020
This commit adds a notice when configphp is present but unreadable.  It also adds the ability to display any database connection errors that occur within db_connect_real for diagnostic purposes.  These notices are only presented to the end user when the appropriate flag is set as most users do not need them.

Closes #3181 and closes #3182
@cigamit cigamit added the resolved A fixed issue label Jan 16, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Jun 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement General tag for an enhancement resolved A fixed issue
Projects
None yet
Development

No branches or pull requests

3 participants