| 开发者 | rtpde |
|---|---|
| 更新时间 | 2026年9月1日 04:26 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
/wp-content/plugins/, or upload the ZIP file via "Plugins > Add New".No. The label is rendered purely through HTML and CSS while the page is being output. The original file is never touched.
Yes. The labelling hooks into WordPress core (wp_get_attachment_image, the_content, render_block) and is therefore independent of the theme in use. For themes that only output images by their URL (for example via get_the_post_thumbnail_url), an optional JavaScript fallback detection is available, as well as helper functions for theme developers.
Yes, on upload. Many generators (for example DALL-E and Adobe Firefly) embed the IPTC standard value digitalSourceType into the file. If the plugin finds this marker, the status is applied automatically. Images without metadata (for example screenshots taken from AI tools) still have to be labelled manually.
Yes. Badge texts, position, background colour and opacity are configurable on the settings page, with a live preview. The text colour is chosen automatically for sufficient contrast. For anything beyond that, developer filters are available, among them subreal_ai_badge_renderer for a completely custom badge design.
The label status stays stored, but no visible label is rendered in the frontend. The machine-readable label (the data-ai-status attribute) is still applied, provided that option is enabled.
The admin interface is in English. Translations are delivered through translate.wordpress.org and are installed automatically, and every string is translatable, so contributions are welcome. The badge texts shown in the frontend can be edited freely on the settings page as well, so the visible label can be in any language regardless of the interface language.
data-ai-status attribute on every labelled image, even when the badge is hidden.digitalSourceType; existing labels are never overwritten.