SLG Guest Favorites – Save for Later & Wishlist
| 开发者 | quizpin |
|---|---|
| 更新时间 | 2026年5月4日 04:29 |
| PHP版本: | 8.0 及以上 |
| WordPress版本: | 6.9 |
| 版权: | GPL-2.0-or-later |
| 版权网址: | 版权信息 |
详情介绍:
- Favorite and unfavorite buttons on supported singular content.
- Guest favorites stored in the visitor’s browser on that device.
- Logged-in favorites stored in user meta.
- Instant save and remove toggles with built-in request protection.
- Automatic guest-to-user favorites merge after login.
- A
[slg_gf_favorites]shortcode for a saved posts page. - A
[slg_gf_favorite_button]shortcode for manual button placement. - A simple
slg_gf_favorite_button()template function for theme developers. - Settings for auto-insert, enabled post types, favorites page selection, and button labels.
- Shareable lists or multiple lists.
- Custom database tables.
- Block editor integrations.
- Analytics, remote APIs, or external services.
安装:
- Upload the
slg-guest-favoritesfolder to the/wp-content/plugins/directory. - Activate the plugin through the
Pluginsscreen in WordPress. - Create a page such as
My Favoritesand add the[slg_gf_favorites]shortcode. - Go to
Settings > SLG Guest Favoritesand select that page in the Favorites page dropdown. - Leave auto-insert enabled to show the save button on supported singular posts, or use
[slg_gf_favorite_button]manually. - Theme developers can also render the shared button markup directly with
slg_gf_favorite_button().
屏幕截图:
常见问题:
Where are favorites stored?
Guest favorites are stored in the visitor's browser on that device. Logged-in favorites are stored in user meta. If a visitor later logs in, the current plugin behavior can merge guest favorites into the account.
Is there a template function for theme developers?
Yes. Theme and plugin developers can call slg_gf_favorite_button() to render the same button markup used by the shortcode and public renderer. Pass a post ID when needed, or let the function resolve the current post where possible.
Which post types are supported?
Public post types selected in Settings > SLG Guest Favorites are supported. By default, only standard posts are enabled.
Is the plugin cache-compatible?
The plugin is designed to stay cache-friendly by keeping guest state in the browser and updating the UI client-side where needed. If your site uses aggressive full-page caching, a CDN, or security rules, make sure normal frontend AJAX requests can still reach admin-ajax.php.
What if browser storage is blocked?
Guest favorites rely on browser storage in the current version. If the browser is blocking saved items, heavily restricted, or cleared, guest favorites may not persist after reload. Logged-in favorites are stored in the user account and are not affected in the same way.
What happens on uninstall?
The plugin removes its own saved settings. User favorites stored in user meta are preserved by default to avoid destructive data loss.
Does it create database tables?
No. This plugin does not create custom database tables in the current version.
更新日志:
- Removed all remaining legacy ffg_ prefix runtime usage for WordPress.org compliance.
- Renamed all internal class files and asset files from ffg- to slg-gf- prefix.
- Fixed contributors field in readme.txt to use the correct WordPress.org username.
- Aligned the display name, slug, and banner wording for the final release package.
- Updated the block callbacks to use the current plugin slug consistently.
- Bumped all release metadata to the final release version.
- Refined the settings-page hero and wording so the top banner feels complete and more helpful for site owners.
- Simplified a few admin and readme descriptions to better match the plugin's user-facing purpose.
- Aligned packaging metadata and translation references with the final polished release state.
- Renamed the plugin to SLG Guest Favorites for WordPress.org resubmission compliance.
- Aligned plugin slug, text domain, branding, and internal prefixes with backward-compatible fallbacks for existing installs.
- Removed WordPress.org directory listing assets from the plugin package path and kept the admin screen styling without shipping banner files in the ZIP.
- Removed unfinished block scaffolding from the submission build and kept the shipped feature set aligned with the plugin readme.
- Simplified the admin settings screen and tightened release packaging rules for a cleaner WordPress.org submission.
- Improved the template-function integration path so manually rendered buttons can enqueue plugin assets safely.
- Added a final hardening pass for AJAX request handling, safer guest browser-storage failures, and more conservative uninstall cleanup.
- Fixed a settings-page markup issue and aligned final submission metadata.
- Added a documented
slg_gf_favorite_button()template function for theme developers. - Added practical support notes for cache behavior, browser storage limits, and guest versus logged-in favorites storage.
- Added WordPress.org readiness cleanup, including safer uninstall behavior and a Plugins screen Settings link.
- Tightened frontend hardening and reduced unnecessary asset loading.
- Updated plugin readme and packaging rules to better match the current feature set.
- Added admin settings for auto-insert, allowed post types, favorites page selection, and button labels.
- Added guest-to-user favorites merge after login.
- Initial plugin scaffold and development tooling setup.