| 开发者 | kristoffbertram |
|---|---|
| 更新时间 | 2026年8月20日 20:14 |
| PHP版本: | 8.2 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
freshet_feeds( 'my-feed' ) returns normalized item objects; freshet_feeds_render( 'my-feed' ) runs the full template chain.item.php into {your-theme}/freshet-feeds/ and edit. An item hierarchy (item-{feed-slug}.php → item-{provider}.php → item.php) gives per-feed and per-type markup with clean fallbacks.layout-carousel.php in your theme, pass carousel — no registration.production.freshet_feeds_render( 'your-feed-slug' ) in your theme.Yes — that is what the Mock (fixture data) provider is for. Create a feed with it and you get a bundled set of realistic sample posts (single image, multi-image, shared article, text-only, an image-only post with no text, and a long multi-paragraph one) without any credentials or network call. It is also the fastest way to evaluate the plugin.
Mock posts run through exactly the same normalizer, item model and template chain as live posts, so everything you build against them works unchanged on real data — you switch the feed's provider and nothing else.
The provider is hidden in the provider dropdown on sites reporting a production environment type, and refuses to fetch there even for a feed created earlier, so fixture posts cannot end up on a live site.
X has no free read API and no RSS. We don't build on scraping. If that changes, we'll add it.
Copy any template from the plugin's templates/ folder into {your-theme}/freshet-feeds/ and edit it. See the template docs.
No. Feeds are fetched in the background and served from a local cache; pages never wait on a remote API (except the one-time first fetch of a newly created feed). Images are served from your own uploads directory.
wp freshet-feeds fetch, wp freshet-feeds status).