Pro license panel shows “Expired on” for a future expiration date
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
Research direction
Start in includes/admin/class-rop-global-settings.php at get_license_data_view() (lines 578–603), where a non-valid status picks the past-tense string without comparing the expires date to today; the two wordings come from Rop_I18n::get_labels() at lines 445–446. Extend tests/test-license-mask.php (Test_RopLicenseMask::get_view(), lines 42–136) with future and past expiration dates across valid, invalid, inactive and expired statuses. Done means a future date under a non-valid status renders "Expires on" and the suite passes in a PHP/WordPress test environment; check vue/src/vue-elements/main-page-panel.vue lines 179–217 to confirm the panel only displays what the formatter returns.
Written by the indexing model from the issue text.
Description
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)
- Dominant language
- PHP
- Stars
- 13
- Forks
- 15
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 15
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Codeinwp/tweet-old-post
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
Codeinwp/tweet-old-post#1053 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Codeinwp/tweet-old-post#957 ·
Maintainers usually reply within 1 day
-
Chronological orderOpenquestion
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Codeinwp/tweet-old-post#950 · 1 comment ·
Maintainers usually reply within 1 day
-
customer report new feature
Difficulty 5/5 Over a week Newbie friendliness 25/100
Codeinwp/tweet-old-post#946 · 1 comment ·
Maintainers usually reply within 1 day
-
customer report new feature
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Codeinwp/tweet-old-post#912 ·
Maintainers usually reply within 1 day
All issues in Codeinwp/tweet-old-post
Similar issues
-
Difficulty 2/5 Half a day Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
sonata-project/dev-kit#3119 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
🧠 Admin
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
RSA PKCS#1 v1.5 verify fails for SHA-512/224, SHA-512/256 and SHA-3 (UnhandledMatchError on 4.x)Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day