Source evidence

Error for custom post types

Static Site Exporter · support · 2018-07-04T19:45:00+00:00

Static Site Exporter plugin evidence original source source API

complaintsentiment

mediumseverity

0.81relevance

0replies

Evidence linked to opportunitycommercial context

Proof Health

Open evidence

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

5 / 25 rows with source links

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

0 build-decision rows missing links

0 rows here require auditable proof before promotion.

20 rows with no attached evidence

0 rows have source counts but still need direct links.

Conversation

support

polyfade unresolved

Specifying add_filter( 'jekyll_export_post_types', array('posts', 'pages', 'my-post-type') ); exports an empty _posts directory, and without any pages markdown files. Even specifying this add_filter( 'jekyll_export_post_types', array('posts', 'pages') ); returns the same result. Using PHPv7, WordPress 4.9.6, unmodified Twenty Seventeen theme

Commercial Context

Opportunity

migration and recovery assurance

Export preflight and recovery verification for moving, restoring, or rolling back sites without failed handoffs

Buyer: site owners, agencies, and maintenance teams

Wedge: preflight export jobs, verify restore/import output, and flag failed handoffs

Proof Blocked card complete market

Analysis

heuristic-v1

Summary: Error for custom post types: users show bugs, compatibility, migration pain that may indicate a product gap.

Evidence quote: Error for custom post types Specifying add_filter( 'jekyll_export_post_types', array('posts', 'pages', 'my-post-type') ); exports an empty _posts directory, and without any pages markdown files.

Error for custom post types

Proof Health

Conversation

Comments