Add "Disconnect" or "Change API key" option to the disabled account screen
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 3/5
- 预计耗时
- 1-2 天
- 新手友好度
- 58/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 冷清
调研方向
首先定位 Account Disabled 屏幕、存储或清除 API key 的代码，以及默认的 onboarding 视图。跟踪禁用状态的渲染方式，以及现有的断开连接或设置流程如何处理凭据。完成的标准是：屏幕提供该操作，已保存的 key 被移除，并且用户返回 onboarding 以输入替换用的 key。
由索引模型根据 Issue 内容生成。
描述
Impact: 75 · Confidence: 95 · Complexity: 25
Description
Problem: When an Optimole account is disabled (e.g., due to quota limits), the WordPress plugin gets locked into a disabled state that only prompts the user to upgrade. If a user purchases a subscription under a new account, they have no clear way to enter their new API key because the normal settings are inaccessible and there is no disconnect button on the blocked screen.
Desired Behavior: The "Account Disabled" screen should feature a secondary action, such as a "Disconnect" or "Use a different API key" button/link. Clicking this should clear the current API key and redirect the user back to the initial setup screen.
Acceptance Criteria:
- The disabled account screen displays a visible "Disconnect" or "Change API key" button.
- Clicking the button successfully removes the saved API key from the database.
- The user is seamlessly returned to the default onboarding view where they can input a new API key.
Customer Context
Fiona (a pro-user/managing editor) purchased an annual Optimole subscription but inadvertently created a new account to do so. Her WordPress plugin is still tied to her old disabled account, and the plugin's UI is locked on a disabled message. She is frustrated because she cannot find any way to input her new activation code or disconnect the old account to sync the plugin with her newly paid dashboard.
Root Cause Analysis
The root cause of this issue is that the plugin's UI assumes users will always upgrade their existing connected account when hitting a quota limit and becoming disabled. It fails to account for the real-world flow where a user might create a new account to purchase a subscription. Once locked in the 'disabled' view, the plugin hides normal settings and lacks a manual escape hatch (like a 'Disconnect' button), forcing users into a dead-end UI.
Alternative Suggestions
Improve the existing 'Account Disabled' view by adding a 'Disconnect' or 'Log into a different account' button. This changes the current blocking behavior into a flexible workflow, empowering users to clear their old API credentials and re-authenticate using a different account without needing technical workarounds like reinstalling the plugin or touching the database.
Reasoning
The customer purchased a paid tier by creating a new account (as shown in the forwarded email) rather than upgrading their existing account. The plugin is displaying an 'account disabled' block since it's still synced to the old account. Because the plugin's disabled UI state only provides an upgrade link and hides or omits the ability to disconnect or enter a new API key, the customer is stuck. Providing a way to disconnect or update the API key from this screen will solve the user's issue without requiring them to reinstall the plugin or have support manually intervene.
Source: HelpScout #3320787612
Generated by feature-request-triage workflow (ID: feature-request-triage_6a0459ca6bab28.93408751)
- 主要语言
- PHP
- 星标
- 74
- 派生
- 14
- 平均合并
- 2 天 9 小时
- 30 天内合并 PR
- 22
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
Codeinwp/optimole-wp 的其他 Issue
-
Image URL replacement passes an integer cache token to the Optimole SDK可能已有人在做 @selul 于 3 天前认领。 未关闭bug bug-report bug-report-triage crash-report
难度 3/5 1-2 天 新手友好度 55/100
Codeinwp/optimole-wp#1187 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
Image parser uses a data: placeholder from data-src as the image URL, so the real src misses srcset enhancement可能已有人在做 @selul 于 3 天前认领。 未关闭bug bug-report
难度 4/5 1-2 天 新手友好度 56/100
Codeinwp/optimole-wp#1186 · 2 条评论 · 已指派 1 人 ·
维护者通常 1 天内回复
-
customer report feature-request-triage
难度 5/5 一周以上 新手友好度 35/100
Codeinwp/optimole-wp#1179 ·
维护者通常 1 天内回复
-
customer report feature-request-triage
难度 4/5 3-5 天 新手友好度 54/100
Codeinwp/optimole-wp#1178 ·
维护者通常 1 天内回复
-
bug bug-report bug-report-triage crash-report
难度 4/5 3-5 天 新手友好度 45/100
Codeinwp/optimole-wp#1163 · 4 条评论 ·
维护者通常 1 天内回复
查看 Codeinwp/optimole-wp 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
[2.x] extension-manager: translation keys that changed meaning keep their old names可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭type/bug
难度 2/5 1-3 小时 新手友好度 84/100
维护者通常 1 天内回复
-
needs-triage Technical TODO
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 2 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
MISP/misp-docker#478 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 84/100
glpi-project/glpi#26045 ·
维护者通常 1 天内回复