| 开发者 | yinga |
|---|---|
| 更新时间 | 2026年11月4日 17:31 |
| PHP版本: | 8.1 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
object-position value. That is 0 KB of CSS and 0 KB of JavaScript for your visitors, and it is safe by construction: object-position only has an effect where your theme already crops. An image that is fully visible today cannot shift.wp_get_attachment_image() — every block theme, GeneratePress, Astra, and friends.yinga_focus_get(), yinga_focus_css_position(), yinga_focus_resolve() and more.No. The plugin only writes an object-position, which has no effect on images that are not being cropped by your theme. Nothing moves until you set a focal point, and even then only images that were already being cropped shift — toward the subject.
As regular WordPress post meta on the attachment, with a schema version and a migration path. Deactivating or removing the plugin never touches your images or your data.
The admin-bar report on that page will tell you. The usual causes: the theme writes its own <img> tags, the image is a CSS background, or the file is a hard-cropped size. None of those pass through the WordPress image functions, so there is nothing for this plugin to filter. The paid add-on reaches them with a page scanner.
Yes. The engine only cares about aspect ratios, not file formats.
wp_add_inline_style() instead of being printed in the footer.Update URI header; it is meant for plugins hosted outside WordPress.org.inherit was being treated as public, which it is not.breakpoints is now declared in the REST route schema; it was already accepted and sanitised.yinga_focus/...) and every file guards against direct access in the standard form, so the plugin passes the WordPress.org Plugin Check without warnings on those points.wp.i18n, so its buttons and hints are translatable as well — they used to be hard-coded.