| @@ -588,8 +588,21 @@ | ||
| 588 | 588 | '/wp-json/notificationx/v1/notice', |
| 589 | 589 | '/wp-json/notificationx/v1/delete-cookies', |
| 590 | 590 | '/wp-json/notificationx/v1/import', |
| 591 | 591 | '/wp-json/notificationx/v1/export', |
| 592 | + | |
| 593 | + /* | |
| 594 | + * TRANSITIONAL — remove in the release after Pro ships its own | |
| 595 | + * NotificationXPro\Core\REST::jwt_whitelist() override. | |
| 596 | + * | |
| 597 | + * These four routes belong to Pro: the licensing library registers them | |
| 598 | + * into this namespace, and Pro now whitelists all six itself. They stay | |
| 599 | + * here for one release only because Free auto-updates from wp.org while | |
| 600 | + * Pro updates through the licensed channel, so "new Free + old Pro" is a | |
| 601 | + * normal state for a site, and an old Pro carries no override. Dropping | |
| 602 | + * them before Pro has propagated would take the entries to zero for those | |
| 603 | + * sites. Pro's override calls array_unique(), so the overlap is harmless. | |
| 604 | + */ | |
| 592 | 605 | '/wp-json/notificationx/v1/license/activate', |
| 593 | 606 | '/wp-json/notificationx/v1/license/deactivate', |
| 594 | 607 | '/wp-json/notificationx/v1/license/submit-otp', |
| 595 | 608 | '/wp-json/notificationx/v1/license/resend-otp', |
