Codeinwp / Codeinwp/optimole-wp

Improve User Experience by Automatically Managing Notices After Issue Resolution

Open
#811 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
PHP
Stars
72
Forks
14
Avg merge
2d 9h
Merged PRs (30d)
15

Description

What problem does this address?

In Optimole, when there is a conflict with another plugin, we currently display notices to users, instructing them to make specific changes. For example, with the W3 Total Cache plugin, users need to exclude Optimole JS files from its settings. While this issue is straightforward and users can resolve it using a direct link, there is a problem with the user experience afterward.

Once users follow the instructions and make the necessary changes, they expect the notice to disappear automatically, indicating that the issue has been resolved. However, currently, users must manually dismiss the notification, which can lead to confusion as it's not written anywhere on the notice, and it can lead to a bad user experience.

What is your proposed solution?

To enhance this process, I propose the following improvements:

  1. Add a function that automatically detects when the user has made the necessary changes and dismisses the notification accordingly.

  2. If automatic detection is not feasible, modify the error message to inform users that they can manually dismiss the notification once the changes are made. Additionally, we can include a button within the notification that allows users to dismiss it directly, with a clear message explaining its function e.g - I have made the changes

Image

By implementing these improvements, we can reduce confusion, ensuring that users are confident their issues are resolved without additional manual steps.

References -

image
https://secure.helpscout.net/conversation/2601747066/419300/
https://secure.helpscout.net/conversation/2349518155/384145

Will this feature require documentation? (Optional)

None

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing conflict-notice entry points and the W3 Total Cache integration described in the issue. Determine whether the relevant settings can be detected reliably, or whether the notice needs an explicit dismissal action. Done means the notice no longer creates confusion after users resolve the conflict.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
backend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.