I have three environments set up: Production (Live), UAT, and Development.
After our account was recently renewed, I noticed that everything works fine on both Production and UAT—there are no issues with the plugin renewal there. For the UAT environment, I was able to successfully renew by generating a new token and reactivating the plugin using the usual steps.
However, I’m facing an issue with the Development environment. Although all three environments are configured in exactly the same way, the renewal is not being recognized on Dev. I’ve already tried the following steps:
Deleted the old token and generated a new one
Inserted the new token into the database
Deactivated and reactivated the plugin
Followed the same steps that worked in UAT
Despite this, the issue persists on the Dev site, and the renewal message is still showing.
Under Installer Support, everything appears to be fine (all checks are green), including API connectivity and required PHP libraries.
This issue started only after the account renewal. Both UAT and Dev are internal development environments that were set up last year and were working correctly before renewal.
Could you please advise on what additional steps I might need to take—such as clearing caches or resetting any settings—to ensure the new token is properly recognized and to remove the renewal message on the Development site?
Hello. There was no answer in the chat so we turned it to this ticket.
The latest conversation was that changing a ley from MySQL will not cut it and you will need to do it from the WP Dashboard or alternatively you can use this method:
