WPIntell

Source evidence

Not Expiring Posts

TIEexpire Automated Post Expiry · support · 2013-10-07T20:22:00+00:00

TIEexpire Automated Post Expiry plugin evidence original source source API
mixedsentiment
mediumseverity
0.78relevance
3replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

Commercial opportunities need traceable source links before they are treated as build-worthy.

2 / 30 rows with source links

6.7% of this page's analysis has direct source links.

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

28 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support
ModularBase resolved
Installed plugin. Have these fields: Expiry by age & Expiry post limit. Set Expiry by age to “90” and Expiry post limit to “0”, yet no posts are being moved to trash, even though I have posts way older than 90 days. http://wordpress.org/plugins/tieexpire-automated-post-expiry/ So, I de-activated, then re-activated the plugin and it worked as expected. Curious. Hmmm. That is VERY odd indeed. The automatic cron job is set up on activation, so maybe something odd happened there. I’ve had similar things occur on my own blogs, apparently randomly. Glad to hear it worked after a reactivation and thanks for letting me know. I’ll put a note in the FAQ and keep an eye out for occurrences, see if there’s a particular reason. Marked resolved as this is not a reproducable error, but has a solid workaround. Note added to both the FAQ and the plugin development page on my own site.

Comments

3 shown
ModularBase 2013-10-07T20:30:00+00:00

So, I de-activated, then re-activated the plugin and it worked as expected. Curious.

TIEro 2013-10-08T09:26:00+00:00

Hmmm. That is VERY odd indeed. The automatic cron job is set up on activation, so maybe something odd happened there. I’ve had similar things occur on my own blogs, apparently randomly. Glad to hear it worked after a reactivation and thanks for letting me know. I’ll put a note in the FAQ and keep an eye out for occurrences, see if there’s a particular reason.

TIEro 2013-11-06T10:20:00+00:00

Marked resolved as this is not a reproducable error, but has a solid workaround. Note added to both the FAQ and the plugin development page on my own site.