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

Standardize confirmation/error message placement in Admin Interface #5228

Open
eloquence opened this issue May 4, 2020 · 0 comments
Open
Labels

Comments

@eloquence
Copy link
Member

The web-based Admin Interface allows admins to send test OSSEC alerts, update a logo, and update submission preferences. In #5046 we added a confirmation message after changing the submission preferences, and in #5223 we removed duplicated display of that message.

The confirmation message for submission preferences is now displayed at the bottom of the page, where it is easy to miss.

We should standardize the confirmation/error message display in the Admin Interface, with an eye to ensuring that confirmation messages are clear and noticeable. Solutions could include:

  • always anchoring to the relevant section to ensure that the message is in view
  • always displaying confirmation/error messages at the top of the page

It's worth noting that the OSSEC test alert is not really a setting. It may make sense to organize the page(s) differently, which could influence how we want to handle confirmation/error message display.

Screenshots of current behavior

Test alert

Screen Shot 2020-05-04 at 10 29 07-fullpage

(Note how this confirmation message is displayed above even the "Back to admin interface" link)

Logo change

Screen Shot 2020-05-04 at 10 30 02-fullpage

Logo error

Screen Shot 2020-05-04 at 10 29 38-fullpage

Submission preferences change

Screen Shot 2020-05-04 at 10 29 25-fullpage

@eloquence eloquence added the UX label May 4, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant