Bigfoot Open Wall
| 开发者 | ibigfoot |
|---|---|
| 更新时间 | 2026年11月10日 00:55 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
详情介绍:
- Mastodon RSS support
- Pixelfed Atom support
- Additional RSS/Atom feeds with custom display names
- Per-feed diagnostics for reachability, format, item count and media detection
- Manual feed validation from the WordPress admin
- Responsive masonry-style layout
- Centered source filter bar
- Full post text without automatic truncation
- Image and multi-image support when supplied by the source feed
- Source-aware client-side Load more pagination
- Native dynamic Gutenberg block
- Shortcode support
- Original-item links
- WordPress transient caching
- Configurable wall width, cache duration, initial post count and batch size
- Bundled German interface translation
- No bundled analytics or tracking
- No third-party JavaScript dependencies
安装:
- Install and activate Bigfoot Open Wall.
- Go to Settings > Bigfoot Open Wall.
- Add a Mastodon RSS feed, Pixelfed Atom feed or another public RSS/Atom feed.
- Adjust display and caching options if needed.
- Add the Bigfoot Open Wall block to a page or post. Alternatively, add
[open_social_wall].
屏幕截图:
常见问题:
Does it require an API key?
No. Bigfoot Open Wall uses public RSS/Atom feeds and does not require an API key for the currently supported sources.
How do I use the Gutenberg block?
Add the Bigfoot Open Wall block from the block inserter. Feed URLs remain configured globally under Settings > Bigfoot Open Wall. In the block inspector you can choose the number of posts shown initially and whether source filters are displayed. The block is rendered dynamically on the frontend and uses the same feed and cache logic as the shortcode.
Is the shortcode still supported?
Yes. [open_social_wall] remains fully supported and can be used alongside the Gutenberg block. The shortcode name is preserved for backward compatibility.
Can I add feeds other than Mastodon or Pixelfed?
Yes. Use Additional feeds in Settings > Bigfoot Open Wall. Each additional source can have its own display name, which is shown in the source filter bar and on its cards.
How can I check whether a configured feed works?
Open Settings > Bigfoot Open Wall and use the Feed diagnostics section. It shows the latest validation result for each configured source, including feed format, item count, media detection and an actionable error state where available. Use Check feeds now to run an explicit server-side validation.
How does caching work?
Feed data is fetched server-side and cached locally using WordPress transients. The default cache duration is 30 minutes. Normal page views use the cached data until it expires, so configured feed sources are not contacted on every page load.
Are images cached locally?
No. Media files are currently loaded from the URLs supplied by the source feed. This means a visitor's browser may contact the remote media host when an image is displayed. See the External services section for details.
Does Bigfoot Open Wall use embeds or third-party JavaScript?
No. Posts are normalized from their RSS/Atom data and rendered by the plugin. Bigfoot Open Wall does not bundle third-party JavaScript, analytics or tracking scripts. The Gutenberg editor integration uses JavaScript APIs provided by WordPress itself.
Does it support Instagram?
No. Instagram support is currently deprioritized. If it is explored later, it would use an official API where practical; the project does not scrape Instagram.
Why can I not load older posts?
RSS and Atom sources often publish only a limited number of recent items. Bigfoot Open Wall cannot retrieve history that is not present in the source feed.
Do cards link back to the original item?
Cards link to the item URLs provided by their source feeds and open them in a new tab. A known edge case involving later thread posts can link to the first post of the thread; this is being investigated.
更新日志:
- Clarified plugin author identity and WordPress.org contributor metadata. No functional changes.
- Aligned the WordPress.org plugin slug, PHP/JavaScript text domain and Gutenberg block metadata with
bigfoot-open-wall. - Renamed the installable plugin folder and entry file for the review-requested directory slug.
- Renamed and rebuilt bundled German translations for the new text domain.
- Preserved all
ibfosw_*settings and diagnostics, the[open_social_wall]shortcode, and the existing Gutenberg block name. - Documented the manual upgrade from the old directory to avoid simultaneous activation.
- Limited source-filter and Load more button styling to the plugin component to avoid theme CSS overrides.
- Renamed the public product to Bigfoot Open Wall.
- Replaced short global runtime identifiers with the unique IBFOSW_/ibfosw_ prefix for WordPress.org review readiness.
- Added automatic migration of existing pre-0.3.1 settings, diagnostics, status options and cache metadata.
- Updated Gutenberg, admin, privacy-policy helper and documentation names consistently.
- Preserved the existing
[open_social_wall]shortcode and block name for backward compatibility. - Updated roadmap language to reflect the current priority order and the deprioritization of proprietary platform connectors such as Instagram.
- Added per-feed diagnostics in Settings > Open Social Wall with reachability, detected format, item count, media detection, timestamp and concise errors.
- Added a manual Check feeds now action with WordPress capability and nonce protection.
- Added bundled German translations for the plugin settings, diagnostics, Gutenberg controls and frontend labels.
- Improved source filtering so Load more works against the complete loaded pool for the selected source.
- Improved the Gutenberg block inspector so the effective plugin default is always visible and can be restored explicitly.
- Fixed the Gutenberg settings link so it opens the full Open Social Wall settings page instead of a mixed editor view.
- Improved format display for configured Mastodon and Pixelfed feeds when automatic detection cannot complete.
- Kept diagnostics local to WordPress and added no analytics, tracking or external diagnostic service.
- Added a native dynamic Gutenberg block as an alternative to the shortcode.
- Added block controls for initial post count and source-filter visibility.
- Added a lightweight editor placeholder with a link to the global plugin settings.
- Kept feed configuration centralized under Settings > Open Social Wall.
- Reused the existing server-side feed, cache and rendering logic without adding a Node/npm build step.
- Kept the existing
[open_social_wall]shortcode fully supported.
- Added clearer external-service and privacy documentation.
- Added WordPress privacy-policy helper text.
- Moved admin CSS and JavaScript into enqueued assets.
- Improved card accessibility by avoiding nested interactive semantics.
- Replaced direct database transient cleanup with WordPress transient APIs.
- Prepared metadata for WordPress.org submission.
- Initial public release.
- Mastodon RSS and Pixelfed Atom aggregation.
- Additional RSS/Atom sources with custom display names.
- Responsive masonry layout.
- Centered source filters and client-side Load more pagination.
- WordPress transient caching.