| 开发者 | senzastile |
|---|---|
| 更新时间 | 2026年6月30日 19:42 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/senzastile-featured-image-fallbacks directory, or install the plugin through the WordPress Plugins screen.No. The plugin filters featured image data on the frontend only. It never edits your posts, never sets a real featured image, and never changes your database. If you deactivate the plugin, every post returns to its original state immediately.
Yes. The plugin supports standard posts, pages, and any public Custom Post Type (CPT) registered on your site. You choose exactly which post types use fallback images on the settings page.
Yes. The plugin hooks into the standard WordPress featured image APIs (such as get_post_thumbnail_id(), has_post_thumbnail(), and the_post_thumbnail()), which are used by both classic themes and modern block themes. As long as your theme displays featured images through these standard functions, fallbacks appear automatically.
Yes. WooCommerce products are a custom post type, so you can enable fallbacks for them on the settings page and a placeholder will be shown for any product without a product image on the frontend. Note that WooCommerce also ships its own built-in product placeholder; if you prefer this plugin's images for shop and archive grids, enable the product post type here. The plugin does not modify product data.
Yes. Open any post in the block editor, find the Featured Image Fallbacks panel in the document sidebar, and check Do not use fallback images for this content. Developers can also use the senzfif_enabled filter, which takes precedence over the per-post checkbox.
Yes. In Settings → Image Fallbacks, scroll to Category Pools and assign a dedicated set of images to any category. A post uses the pool of its first matching category; if no category pool matches, the global pool is used.
Stable Random assigns the same fallback image to the same post every time, keeping your layouts consistent and working perfectly with page caching and CDNs (recommended). Pure Random picks a different image on each uncached page load for more variety. If you use a caching plugin or CDN, choose Stable Random — cached pages will otherwise "freeze" whichever random image was stored at cache time.
Uninstalling cleanly removes everything the plugin created: its settings, the per-post opt-out data, and any legacy settings from previous versions. Your posts, pages, products, and real featured images are never touched. Simply deactivating (without deleting) keeps your settings for later.
Yes. Developers can use the senzfif_placeholder_id filter to change the attachment ID returned for a given post.
class-post-meta.php file was missing from the published package).editor.js) is now correctly included in the package._senzfif_disabled post meta, REST-registered with an auth callback).admin_init (guarded by an option flag) instead of on every front-end request; the activation hook is unchanged.senzfif_enabled filter still applies and can override the per-post checkbox.fip to senzfif for WordPress.org guidelines compliance.fip_settings to senzfif_settings on upgrade.fip_enabled, fip_placeholder_id.