Open bahiirwa opened 5 years ago
Transients should always expire on their own if wp-cron is configured correctly. For very low-traffic sites you may need to visit pages manually in order to execute the wp-cron tasks.
Still, if you are interested in making this work, the right way would be to run a database query like this:
DELETE FROM {$wpdb->options}
WHERE option_name like '\_transient\_timeout\_lgr\_%'
OR option_name like '\_transient\_lgr\_%';
You can also install WP-CLI and use the following commands to debug proper operation of this query and of the caching mechanism:
wp transient list
- lists all current transients.wp db query "select * from cp_options where option_name like '%lgr%';"
- shows the values stored in the options table for this plugin's transients. Each transient stores 2 option values, one for the data and one for its expiration time. You may need to edit the table name if your install uses a different table prefix.
The plugin's deactivation hook did not work. Transients stay on deactivation and delete. Even though transients expire on their own. It would be prudent to delete them on deactivation so that it is a simple refresh for a quick fetch of the new releases.
Also to leave the DB clean. Sometimes the transients don't expire on their own.