Source evidence

Using custom post meta date fields

iCal Feeds · support · 2018-12-13T12:02:00+00:00

iCal Feeds plugin evidence original source source API

complaintsentiment

mediumseverity

0.69relevance

0replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

6 / 31 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

25 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

Guido unresolved

Hi again, You can overrule the default date(s) and use your own date field(s) by adding an extra parameter “datefield” and “enddatefield”. So I’ve added these parameters to the URL but I notice this isn’t working in my case, because the date format of my post meta fields do not match the iCal date format. My date format is the default PHP date format (Unix Epoch). How can I meet the date conditions of your plugin? Guido

Commercial Context

Opportunity

content publishing operations

content publishing operations for keeping publishing, media, and editorial handoffs consistent

Buyer: publishers, content teams, and agencies

Wedge: audit publishing workflows, detect inconsistent content operations, and package fix-ready editorial reports

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Using custom post meta date fields: users show compatibility pain that may indicate a product gap.

Evidence quote: So I’ve added these parameters to the URL but I notice this isn’t working in my case, because the date format of my post meta fields do not match the iCal date format.

Affected feature: form

compatibility form

Plugin

API

iCal Feeds

100 active installs · 10.6K downloads · rating 80.0

feed future ical posts uri.lv

Comments

0 shown

No comments were stored for this source.