Hacktoberfest 2026: những issue maintainer đã đánh dấu cho tháng Mười, đang mở và phù hợp người mới. Xem issue Hacktoberfest

Automatically restore site API connection status when account status returns to active

Đang mở
  • Có gì không ổn?
#1,179 0 bình luận 0 reaction 0 người được giao Xem trên GitHub

Maintainer thường phản hồi trong vòng 1 ngày

Chưa có ai nhận issue này.

Đánh giá

Độ khó
5/5
Thời gian dự kiến
Hơn một tuần
Mức phù hợp với người mới
35/100
Loại issue
Tính năng
Độ rõ ràng
Khá rõ ràng
Mức độ hoạt động
Sôi nổi
Công nghệ
php, wordpress
Lĩnh vực
api, backend

Hướng nghiên cứu

Start by reading the plugin’s connection and account status handling, then trace how the backend reports quota or inactive states to connected sites; the issue does not name specific files or tests. Define how sites detect an account returning to active and how restoration is shown in the WordPress admin. Done means previously connected sites resume optimized image delivery automatically after reactivation, with a clear dashboard indication.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.

Mô tả

customer report feature-request-triage

Impact: 85 · Confidence: 90 · Complexity: 55

Description

Problem: When an Optimole account is upgraded or reactivated after exceeding quota/suspension, connected WordPress sites remain in 'Not connected' state and serve unoptimized original images until site administrators manually re-enter the API key on each site individually. For multi-site network agency users with dozens of connected sites, this creates significant operational overhead and service downtime after an upgrade.

Desired Behavior: When an account subscription is upgraded or returns to active status, the Optimole service and client plugin should automatically re-validate/ping backend status and reconnect active sites without requiring manual API key re-keying on each site.

Acceptance Criteria:

  • Client plugin periodically polls account status or handles account status recovery pings from backend service when account state changes from over-quota/inactive to active.
  • Connected WordPress sites automatically resume optimized image delivery upon detecting active account status without administrative manual intervention.
  • Clear UI indication in WordPress admin dashboard when connection state is automatically restored.

Customer Context

Mario Luna (Founder at Clariable, Business plan, 36 sites) experienced account quota overage where 36 connected sites were disconnected and served original unoptimized images. After upgrading the account to active status, all 36 sites required manual API key re-entry on each WordPress site to reconnect and restore image optimization.

Root Cause Analysis

The root cause of the customer's pain is that when an Optimole account's status is disabled/disconnected due to quota exhaustion, the client WordPress plugin updates its stored connection state to disconnected. Upon account upgrade or renewal, there is no automated background handshake or periodic status polling mechanism that automatically transitions connected sites back to an active state. As a result, administrators managing multi-site portfolios must manually re-verify/re-enter the API key on every connected site to restore image optimization service.

Reasoning

The customer (Business plan, 36 WordPress sites) reported two key issues after exceeding their visit quota: 1) Why sites were disconnected instead of auto-upgrading as expected, and 2) When account status is restored/upgraded to active, sites remain in 'Not connected' status serving uncompressed original images until every site's API key is manually re-entered.

Analyzing the underlying system behavior: when an account's status transitions back from suspended/over-quota to active (after plan upgrade or renewal), the connected WordPress plugins/sites do not automatically sync account active status or auto-reconnect without manual API key re-entry across all sites. This represents a clear net-new feature request (or functional improvement) in the Optimole WordPress plugin / cloud service integration to automatically restore active API connection status across connected sites once the backend account transitions back to active.

Source: HelpScout #3480528673
Generated by feature-request-triage workflow (ID: feature-request-triage_6acd1263a00ca9.43669419)

Ngôn ngữ chính
PHP
Star
74
Fork
14
Merge trung bình
2 ngày 6 giờ
Pull request đã merge (30 ngày)
18

Chuẩn bị môi trường

Bắt đầu từ đâu

  1. Đọc hết issue, rồi đọc hướng dẫn đóng góp của dự án.
  2. Bình luận trên issue rằng bạn sẽ nhận — tránh hai người làm cùng một việc.
  3. Fork repository và làm thay đổi trên một nhánh.
  4. Mở pull request có tham chiếu số hiệu của issue.

Issue khác của Codeinwp/optimole-wp

Tất cả issue của Codeinwp/optimole-wp

Issue tương tự

Thêm issue về PHP

Nhận issue mới trong hộp thư của bạn

Bản tóm tắt ngắn những issue GitHub phù hợp với người mới.