WPIntell

Source evidence

Setting the expiration date programmatically

Content Scheduler · support · 2016-04-28T16:05:00+00:00

complaintsentiment
mediumseverity
0.81relevance
1replies
Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

5 / 33 rows with source links

15.2% 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
feed_sheep unresolved
Hi, I’m trying to set _cs-enable-schedule and _cs-expire-date programmatically, but when I check the post, it is not displaying that it is set. I’m not sure if I’m doing something wrong or what. For the first custom value, I have “Enable”. For the second I have “2016-05-02 00:00:00”. No quotes, of course. https://wordpress.org/plugins/content-scheduler/ I’ve been playing with this recently as well and it looks like somewhere down the road between versions the required datetime format changed from a string that looks like “YYYY-MM-DD HH:MM:SS” to an epoch value (the number of seconds since Jan 01, 1970 00:00:00 UTC) I’m having issues with timezone support (CS is converting all my input to UTC despite it being input in my local timezone) but hopefully this will help you.

Comments

1 shown
alien8 2016-06-14T20:05:00+00:00

I’ve been playing with this recently as well and it looks like somewhere down the road between versions the required datetime format changed from a string that looks like “YYYY-MM-DD HH:MM:SS” to an epoch value (the number of seconds since Jan 01, 1970 00:00:00 UTC) I’m having issues with timezone support (CS is converting all my input to UTC despite it being input in my local timezone) but hopefully this will help you.