Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

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

Aperta
  • Qualcosa non va?
#1,179 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
php, wordpress
Ambito
api, backend

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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)

Lingua principale
PHP
Stelle
74
Fork
14
Merge medio
2g 6h
PR unite (30g)
18

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di Codeinwp/optimole-wp

Tutte le issue di Codeinwp/optimole-wp

Issue simili

Altre issue su PHP

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.