Single Post
Renders one post: its title, featured image, content and comments.
This is a background feature. It has no place in navigation, because members reach it by tapping a post rather than by choosing it.
Before you start
Section titled “Before you start”| Plugin | None. WordPress core |
| Endpoint group | Content |
| Plan | Every plan |
Add it to your app
Section titled “Add it to your app”- Open the Background tab on the canvas.
- Drag Single Post onto it.
Only one is allowed. A second is refused with “already added”.
It is also added for you alongside Category Posts, whenever a placed screen holds a Categories block, because a post tapped there opens here.
Settings
Section titled “Settings”| Setting | What it does | Default |
|---|---|---|
| Rendered by | Whether the app draws the post, or your site does | The app |
| Comments | Whether comments are shown, and whether members can post | Read-only |
| Appearance | Content styling for the post body | Inherits app tokens |
Comment permissions still come from WordPress. A post with comments closed on your site has them closed in the app, whatever this setting says.
Rendered by
Section titled “Rendered by”The app draws the post from your site’s content: it matches your app’s design, loads faster, and a page-builder layout arrives without its styling. This is the default and what every app did before the setting existed.
Your site draws it instead, in a webview with your theme’s header and footer stripped, so an Elementor or Beaver layout keeps its own CSS and JS. It needs Memberside 2.22 or newer, and it changes what else this screen can do: the bookmark button, the comments list and the comment form are all things the app draws, and it stops drawing them. The settings above are hidden while it is on rather than left looking adjustable. Your theme’s own comment form still renders if it prints one.
Choosing it also reveals Padding and Margin on the same panel. Your site’s wrapper markup goes with its header and footer, so without them the content sits hard against both edges of the screen. Both need Memberside 2.24 or newer.
With Memberside 2.50 or newer, a link in the post to another post or page on the same site opens the same way — stripped and with the same spacing — so a member reading through a blog keeps the one look. External links are untouched. See Links to your other posts and pages.
See Webview Post for the same rendering as a navigation tab of its own.
What your members see
Section titled “What your members see”The post, rendered natively rather than in a webview. Links inside the content are handled: a link to another post opens Single Post, a link to a page opens Single Page, and a link to a member opens their Profile. Links in comments are handled the same way, and a link the app has no screen for opens in the in-app browser — see Links in posts.
That routing is why placing this feature matters beyond the posts screen — it is also what makes links inside feed posts work.
Where members arrive from
Section titled “Where members arrive from”Several places, which is why one instance serves the whole app:
- Tapping an item in Posts.
- Tapping a linked post inside feed content.
- Tapping a post result in Search.
- A Remote link profile tab pointing at a post.
When it does not work
Section titled “When it does not work”| Symptom | Cause | Fix |
|---|---|---|
| Tapping a post does nothing | This feature is not placed | Add it on the Background tab |
| It will not drop | One is already placed | Check the Background tab |
| The post is empty | The Content group is off | Enable it |
| Comments are missing | Closed on the post, or disabled in settings | Check both |
| Members cannot comment | The setting is read-only, or they are signed out | Allow comments, and check sign-in |
| A link inside the post opens a browser | It points outside your site | Expected |