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

Plugin	None. WordPress core
Endpoint group	Content
Plan	Every plan

Add it to your app

1. Open the Background tab on the canvas.
2. Drag Single Post onto it.

Only one is allowed. A second is refused with “already added”.

Settings

Setting	What it does	Default
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.

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.

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

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

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