Pro license panel shows “Expired on” for a future expiration date
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 2/5
- Tempo stimato
- 1-3 ore
- Idoneità per principianti
- 78/100
Direzione di ricerca
Inizia in includes/admin/class-rop-global-settings.php a get_license_data_view() (righe 578–603), dove uno stato non valid sceglie la stringa al passato senza confrontare la data expires con oggi; le due formulazioni provengono da Rop_I18n::get_labels() alle righe 445–446. Estendi tests/test-license-mask.php (Test_RopLicenseMask::get_view(), righe 42–136) con date di scadenza future e passate per gli stati valid, invalid, inactive ed expired. Fatto significa che una data futura sotto uno stato non valid mostra "Expires on" e la suite passa in un ambiente di test PHP/WordPress; controlla vue/src/vue-elements/main-page-panel.vue righe 179–217 per confermare che il pannello mostri solo ciò che restituisce il formatter.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
The Revive Social dashboard can label a Pro license as expired while displaying a future expiration date. The reported panel shows “Expired on November 10, 2046” alongside an Activate button.
Expected behavior: an activation or validation problem is not presented as proof that the license expiration date has passed.
Actual behavior: the panel presents the future date as a past expiration, misleading the customer about their license entitlement and complicating activation troubleshooting.
Customer context
- Product / area: Revive Social dashboard, Revive Old Posts Pro Add-on license panel.
- Version: Customer versions not provided; affected display logic verified in the current free-plugin release, v9.4.6.
- Environment: WordPress; WordPress and PHP versions not provided.
- Reported symptom: License panel displays “Expired on November 10, 2046” with an Activate button in a November 2026 report.
- Impact: Incorrect expiration information during license activation; the underlying activation failure remains unexplained.
Reproduction notes
Reported workflow: attempt to activate the Pro license on a site, then inspect the Revive Social dashboard license panel. The supplied image shows a future date labeled “Expired on” and an Activate button.
Source-derived local check, not executed: with Pro installed, provide license metadata containing a non-valid status and a future expires date, then load the dashboard. The formatter selects the expired wording for that state. Exact customer versions and the activation response are missing.
Diagnosis
Conclusion
The misleading expiration wording is confirmed by the ticket image and direct source inspection. The formatter selects “Expired on” whenever the stored license status differs from valid, without comparing the expiration date with the current date. This logic remains present in release v9.4.6. Searches of the free and Pro repositories' GitHub issues found no matching open issue.
Where this likely occurs
includes/admin/class-rop-global-settings.php—Rop_Global_Settings::get_license_data()lines 552–567 reads stored Pro license metadata when Pro is installed;get_license_data_view()lines 578–603 formats a supplied expiration date and selects past-tense wording for non-validstatus.includes/class-rop-i18n.php—Rop_I18n::get_labels()lines 445–446 supplies the distinct “Expires on” and “Expired on” strings.includes/admin/class-rop-admin.php—Rop_Admin::enqueue_scripts()lines 351–357 exposes the formatted license data to the dashboard.vue/src/vue-elements/main-page-panel.vue—MainPagePaneltemplate lines 179–217 renders the supplied expiration string when Pro is installed;is_license_valid()lines 281–282 independently controls activation state using thevalidstatus.- Git blame and
git showidentify commit64090979b9161d8cb23e90256a94155b22a9d921as introducing the status-based wording. No previously working released version was established, so regression status remains false.
Engineering notes
The defect belongs to the free plugin's dashboard formatter even though it is visible for the Pro add-on. The Pro companion's tweet-old-post-pro.php — run_rop_pro() lines 57–71 registers the product with the SDK and its rop namespace; the inspected wording is generated in the free repository, not that registration.
The image corroborates the future-date contradiction and the inactive-looking panel state. The customer's exact stored license status, activation response, and entitlement were not available. The display defect does not establish that activation rejection is itself defective. No WordPress-core behavior is required to establish the faulty conditional.
Test coverage status
tests/test-license-mask.php — Test_RopLicenseMask::get_view() lines 42–51 exercises this formatter with stored license metadata. Its tests at lines 60–136 cover masking and short or empty keys, not expiration wording. No relevant expiry-status coverage was found during inspection. Tests were not executed because the PHP executable is unavailable in this environment.
What to verify or explore next
- In a local WordPress test environment with Pro installed, supply non-
validlicense metadata with a future expiration date and inspect the dashboard text. - Compare future and past dates across valid, invalid, inactive, and expired statuses supported by the licensing service.
- Run the existing license-display test suite in a PHP/WordPress test environment.
Unknowns / follow-up
The customer's plugin versions, activation-service response, and stored license metadata are unknown. The suggested reactivation procedure has no reported outcome in this thread.
Confidence
Confidence: 99/100
The ticket image directly shows the contradiction, and the current released formatter contains a reachable conditional that explains it without a date comparison.
Source: HelpScout #3515732204
Generated by bug-report-triage (ID: bug-report-triage_6afa47a1aead00.27706403)
- Lingua principale
- PHP
- Stelle
- 13
- Fork
- 15
- Merge medio
- 2g 12h
- PR unite (30g)
- 15
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di Codeinwp/tweet-old-post
-
Difficoltà 3/5 1-2 giorni Idoneità per principianti 35/100
Codeinwp/tweet-old-post#1053 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
Codeinwp/tweet-old-post#957 ·
I maintainer di solito rispondono entro 1 giorno
-
Chronological orderApertaquestion
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
Codeinwp/tweet-old-post#950 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
customer report new feature
Difficoltà 5/5 Più di una settimana Idoneità per principianti 25/100
Codeinwp/tweet-old-post#946 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
customer report new feature
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
Codeinwp/tweet-old-post#912 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di Codeinwp/tweet-old-post
Issue simili
-
[Sync EN] Pdo\Pgsql: document session state reset on persistent connections (PHP 8.6) (#6084)Forse già presa @lacatoire l’ha presa oggi. Apertasync-en
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
Potential Bug To Triage
Difficoltà 2/5 1-3 ore Idoneità per principianti 63/100
matomo-org/matomo#25740 ·
I maintainer di solito rispondono entro 1 giorno
-
[Type] Bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
WordPress/ai#1386 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
E2E setup scripts seed the legacy `payment_request` settings keys instead of `express_checkout`Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
woocommerce/woocommerce-gateway-stripe#6201 ·
I maintainer di solito rispondono entro 2 giorni
-
bug status: unverified
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno