Image Hotspots by Pleaseup – Interactive Image Map & Tooltips
| 开发者 | bypleaseup |
|---|---|
| 更新时间 | 2026年6月16日 23:09 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
安装:
- Upload the
pleaseup-hotspotsfolder to the/wp-content/plugins/directory, or install the plugin directly from the WordPress plugin repository. - Activate the plugin through the Plugins menu in WordPress.
- Navigate to Image Hotspots → Editor in the admin sidebar.
- Select an image from the Media Library and start adding hotspots.
常见问题:
How do I add a hotspot to an image?
Go to Image Hotspots → Editor, select an image from the Media Library, then click anywhere on the image preview to create a hotspot. Drag it to reposition it, then click the hotspot to edit the HTML content of the popup layer.
How do I display the image with hotspots on the front end?
Use the shortcode [wphs_image id="123"] where 123 is the attachment ID of the image. You can also use the shortcode in any post, page, or widget area that supports shortcodes.
Does it work with Gutenberg image blocks?
Yes. Hotspots are stored against the attachment ID, so any block that references that attachment (image block, gallery block, ACF image fields) inherits the configured hotspots when rendered through the [wphs_image] shortcode.
Does it work with page builders (Elementor, Divi, Beaver Builder)?
Yes via the [wphs_image] and [wphs_gallery] shortcodes. CSS and JS are enqueued defensively for builders that render shortcodes after wp_head.
Are hotspot positions responsive?
Yes. Coordinates are stored as percentages of the natural image dimensions, so they scale with any rendered image size.
Can I use a custom icon instead of the default dot?
Yes. In the per-image settings, switch the hotspot style to Image, upload or choose your custom icon from the Media Library, and save.
Does it work with ACF?
Yes. The plugin stores hotspot data as post meta on the attachment, so any image displayed via wp_get_attachment_image() — including ACF image, gallery, and repeater fields — can use the shortcode to render with hotspots.
Will uninstalling the plugin delete my data?
Yes. When you uninstall the plugin (not just deactivate it), all hotspot settings, attachment meta, and the plugin's custom post type contents (galleries and tooltips) are removed from the database.
更新日志:
- Release pipeline hotfix: forces a clean re-deploy. The 3.1.1 tag landed on WordPress.org SVN with the pre-bump code due to a release-event race condition that fired before the version-coherence sanity check. Plugin payload is identical to the intended 3.1.1.
- Compatibility: declared "Tested up to" WordPress 7.0. No code changes — the plugin uses only long-stable WordPress Core APIs and was verified compatible with the 7.0 release.
- Rebranded plugin display name to "Image Hotspots by Pleaseup" for better discoverability on WordPress.org search.
- Updated readme tags and short description for clarity.
- Admin menu label updated to "Image Hotspots" (page title remains in the same location).
- No functional or breaking changes — existing shortcodes, settings, hooks, post types, and stored data remain fully compatible.
- Build: excluded
.gitkeepplaceholder files from the distribution zip (WordPress.org plugin scanner flags any hidden file). - readme.txt: bumped "Tested up to" to 6.9.
- Admin: renamed the admin sidebar menu label and the in-page hero
<h1>from "WP Hotspots" / "WP Image HotSpots" to "Pleaseup Hotspots" to match the plugin name. - readme.txt: updated installation and FAQ instructions to refer to the new menu label.
- Translations: POT regenerated for the renamed strings.
- Renamed plugin to "Pleaseup Hotspots" (slug
pleaseup-hotspots) for the WordPress.org Plugin Directory. - Frontend: extracted the gallery carousel JavaScript and dynamic CSS to enqueued assets (no more inline
<script>or<style>blocks in the rendered shortcode HTML). The dynamic per-instance values are now passed as CSS custom properties on the wrapper. - Admin: the gallery preview now reuses the same enqueued frontend assets so the in-editor preview matches the public render exactly.