Posting from Pages
A post can be written from a page of the site. UmbSocial fills it in from the page (its link, title, description and image) and ties the post to that page, so the post shows on the page’s own UmbSocial tab. A post tied to a page can also wait for the page to go live: it goes out once the page is published, however long that takes, and pauses if the page is taken down again before it has gone out.
Nothing on this page publishes or saves the page itself. Sharing a page needs UmbSocial’s Write permission and Umbraco’s Browse permission on the page, never its Publish permission.
Share on social…
Section titled “Share on social…”Open a page in the Content section and choose Share on social…. It is in three places:
- the menu of Save and publish, beside Schedule publish and Unpublish;
- the page’s … menu in the content tree, and the workspace’s Actions menu;
- the UmbSocial box on the page’s Info tab.
It opens a new post in the composer, filled in from the page:
| Field | Comes from |
|---|---|
| Text | The page’s link. |
| Link title | The page’s name, in the language being shared. |
| Link description | The page’s description property: Meta description (metaDescription) by default, or the property chosen for its document type (see Choosing the properties). Rich text is turned into plain text and cut to 500 characters. |
| Link image | The page’s image property: Open Graph image (ogImage) by default, or the property chosen for its document type. A media picker with several images gives the first. The image is left out if it is outside your media start nodes. |
| Campaign | The campaign chosen for the page’s document type, if any. |
| Page | The page itself, and its language. |
| When | When the page goes live if the page isn’t published yet; Add to queue if it is. |
The page is read as it is now, including changes that haven’t been published yet. Everything can be changed before you save, and nothing is saved until you choose to save. Leaving the composer without saving asks whether to discard the new post, as with any post.
Share on social… is hidden on a page that hasn’t been saved yet and on a page in the recycle bin.
Which language
Section titled “Which language”On a page that varies by language, a post is about one language of the page. Share on social… from Save and publish and from the UmbSocial box shares the language you are editing; from the content tree it shares the language you are using the backoffice in, or the page’s default language if the page doesn’t have that one. To share the page in other languages, write a post for each.
The composer shows the language under the page. Changing it fills the link, title, description and image in again from that language. On a new post it also changes the timing to suit the language: When the page goes live if that language isn’t published, Add to queue if it is. On a saved post the timing you chose is kept.
The page in the composer
Section titled “The page in the composer”A post with a page shows it above the editor:
- Page: the page’s name, tagged Live or Not live yet, and when it is not live, Planned to go live with the page’s release date if one is set in Umbraco’s Schedule publish. Remove page takes the page off the post: its text and link stay, and a post timed to the page goes to Add to queue instead.
- Language: the page’s language, for a page that varies by language.
- After the page goes live: shown while the post is timed to the page (see below).
A page that isn’t published yet has no address, so Share on social… writes its link as a placeholder, https://page.umbsocial.invalid/{page key}/{language} (no language for a page that doesn’t vary by language), which no browser or network can open. The composer’s previews show the address the page will have, and the Queue, the Calendar, Published and the page’s UmbSocial tab show the page’s address, or its name, in its place. The placeholder is never read for a link card: the card is filled from the page’s own values. When the post goes out, the placeholder is replaced with the page’s address at that moment, as any link to a page of the site is. (Insert link only inserts pages that are already published.)
A post keeps up to 50 links to pages of the site. Keep a post’s links to pages within that, so every one is followed.
How long the text is
Section titled “How long the text is”While the page isn’t live, it has no address yet, so the composer counts the link at the address the page would have if it were published as it is now. If you can’t browse the page, or Umbraco can’t work out that address (for example, a language with no domain of its own), the link is counted at the placeholder’s length instead.
The real address is fixed only when the page is published. If its name or its place in the tree changes before then, the address, and the post’s length, change with it. Leave a few characters to spare under a network’s limit.
When the page goes live
Section titled “When the page goes live”On a post with a page, the composer’s main button is When the page goes live while the post is timed to the page. On a post with a page that isn’t timed to it, When the page goes live is in the menu of Add to queue or Schedule: it sets the timing without saving. Add to queue, Schedule for a time… and Publish now stay available in the menu, and choosing one of them unties the timing from the page (the post keeps its page).
After the page goes live chooses when the post goes out once the page is published:
| Choice | Goes out |
|---|---|
| In the queue’s next free slot (the default) | At the first free slot in the posting schedule after the page goes live. |
| Straight away | At the next check after the page goes live (every 30 seconds by default). |
| 1 hour after | An hour after the page goes live. |
| 1 day after | A day after the page goes live. |
Saving it as When the page goes live needs Write and Schedule, like any other timing that isn’t a draft.
- If the page isn’t live yet, the post’s status is Waiting for its page and it has no time. Its History tab shows Waiting for the page to go live.
- If the page is already live when you save, the post is given its time at once, by its choice: the next free slot (refused with
schedule.no_free_slotif there is none), now, or an hour or a day from now.
When the page is published, every post waiting for it (in that language) is given its time, and its History tab shows The page went live, with that time, by System (or by you, when the page was already live as you saved). From then on it is a scheduled post like any other. A post is placed once: saving it again for the same page, language and choice keeps the time it was given. Saving it for another page or another language makes it wait for that one instead (or places it at once if that one is live).
On a page that varies by language, publishing one language releases only the posts for that language.
UmbSocial hears about the publish from Umbraco as it happens. As a safety net, the publisher also checks every minute for a page that went live without its posts being placed (for example, if the site was restarting as the page was published), and places them then. When one publish releases more than 50 posts at once, the first 50 are placed straight away and the rest within the next few minutes. If no free slot is found, the post stays waiting and UmbSocial tries again every minute; the site’s log says how many posts are waiting for a slot.
On a load-balanced site the page is published on one server, and the other servers’ published content catches up a moment later, so a post released straight away can fall due on a server that doesn’t have the page’s address yet. When the page is published in Umbraco’s database (in the language of the post’s link to it), the publisher doesn’t fail it: it tries that channel again every 30 seconds, for up to 10 minutes after the post’s time, and sends it once the address is there. After 10 minutes it fails with link.content_unavailable, as a page that isn’t live does.
A moved release date changes nothing
Section titled “A moved release date changes nothing”The post waits for the page to be published, not for a date. If someone moves the page’s release date in Umbraco’s Schedule publish, or removes it, the post simply waits until the page is actually published. Planned to go live in the composer, the Queue and the Calendar always shows the page’s current release date, for information only.
Drafts and autosave
Section titled “Drafts and autosave”A draft remembers the choice under After the page goes live. Autosave saves a new post as a draft, but the composer still offers When the page goes live and the choice you made, so nothing is lost; the post only starts waiting for the page when you save it with When the page goes live. A draft never waits for its page, and publishing or unpublishing the page never changes a draft or a post awaiting approval.
When the page is taken down
Section titled “When the page is taken down”A post timed to its page pauses if the page goes away before the post has gone out on any channel:
| What happens to the page | The post |
|---|---|
| Unpublished (or the post’s language is unpublished, or a page above it is unpublished) | Paused. It goes back to Waiting for its page, loses its time, and its History tab shows Paused: the page was unpublished. When the page is published again, it is placed again from that moment, by its choice. |
| Moved to the recycle bin (the page or a page above it) | Paused, with Paused: the page was moved to the recycle bin. Restored from the recycle bin, the page isn’t published, so the post stays paused as unpublished until the page is published again. |
| Deleted from the recycle bin | Paused for good, with Paused: the page was deleted. It is never released. Edit it to remove the page, or tie it to another page, and save it with another timing. |
A post still waiting for a page that never went live gets the same entry when the page (or its language) is unpublished or moved to the recycle bin, so its history says why it waits now. It was never given a time, so nothing says it waits “again”.
Only a post that hasn’t gone out anywhere yet pauses: every channel must still be waiting. A post with a failed, paused or published channel is left as it is. A post with a fixed time (queued, scheduled or published now) that merely has a page is never paused: if its page is unpublished when it is due, that channel fails with link.content_unavailable, and you can retry once the page is published again.
A post that went out and whose page has since been unpublished shows Page no longer published on the page’s UmbSocial tab, because its link now leads nowhere.
On the page: the UmbSocial tab and the Info box
Section titled “On the page: the UmbSocial tab and the Info box”A saved page has a UmbSocial tab in its workspace, for anyone with the UmbSocial section and View or Write in UmbSocial, and Browse on the page. It lists every post tied to the page, newest first, 20 at a time:
- when each goes out (or When the page goes live), its text (which opens the post), its status and, on a page that varies by language, its language;
- each channel, with its status and Open post for a channel where it is live;
- Page no longer published on a post that went out on at least one channel when that language of the page is no longer published;
- Write a post, which shares the page in the language being edited.
The tab follows the page as you publish and unpublish it, without a reload.
The Info tab has a UmbSocial box, for anyone with Write in UmbSocial: how many posts share the page and the next to go out, such as “3 posts · next:” and its time, or “1 post · next: when the page goes live”, with Share on social….
The tab and the box stay on a page in the recycle bin, so you can see its paused posts; Share on social… and Write a post don’t.
In the Queue and the Calendar
Section titled “In the Queue and the Calendar”- The Queue lists posts waiting for their page in a Waiting for a page group, after Drafts and Awaiting approval and above the dated days. Each says Waiting for and the page’s name, then planned and the page’s release date, or why it is paused. The status filter has Waiting for its page.
- The Queue’s group shows at most 500 posts; when more are waiting, it says how many more (“and 112 more”).
- The Calendar shows a waiting post on its page’s planned release date, with a dashed outline and a Waiting for tag naming the page in place of a time. It asks for exactly the waiting posts whose page is planned in the weeks on screen, however many posts are waiting in all. Posts whose page has no planned date are counted instead (“1 post is waiting for a page with no planned date”), with a button to that group in the Queue. A planned date counts only on a page you may browse: a post whose page you can’t browse is among the ones counted. A waiting post can’t be dragged to a day: open it and choose a time instead.
- Moving a post on the Calendar gives it that time: it keeps its page, but no longer waits for it. It keeps everything else too, including each channel’s first comment, content warning and thread.
- Published never lists a waiting post.
Permissions
Section titled “Permissions”| To | Needs |
|---|---|
| Share on social…, Write a post and the UmbSocial box | The UmbSocial section, UmbSocial’s Write and Umbraco’s Browse on the page |
| The UmbSocial tab | The UmbSocial section, UmbSocial’s View or Write, and Browse on the page |
| Save a post as When the page goes live | UmbSocial’s Write and Schedule, as any timing but a draft |
| Tie a post to a page, or change its page or language | Browse on the page (page.no_access) |
| Change the properties that describe a page | UmbSocial’s ManageSettings |
Umbraco’s Publish permission is never needed: UmbSocial never publishes or saves a page.
Someone who can’t browse a post’s page still sees the post, but not its page: the composer shows A page you don’t have access to, with no name, release date or link to it, and lists of posts show “a page” in place of its name. They do see why their post waits (Waiting for a page, and Paused: with the reason when the page was taken down): that is about their own post, not the page’s identity. They can still edit the post (when they may change it), and the page stays on it when they save; they can’t remove it, because they were never shown it. Someone who can browse the page removes it by choosing Remove page and saving.
A page link in a post’s text is part of the post, so anyone who can read the post sees it, including the placeholder of a page that isn’t live yet. A placeholder carries only the page’s key and language: not its name, its address or when it goes live.
The management API answers page.not_found (404) before page.no_access (403): a page that doesn’t exist is reported as such even to someone who couldn’t browse it, as Umbraco’s own content endpoints do. Asking needs the page’s key.
Posts written with AI
Section titled “Posts written with AI”A post written with AI waits for its page only when someone who may review it saves it so: for them the main button reads Review and post when the page goes live. Anyone else can save it as a draft, and When the page goes live is refused (ai.needs_review). If AI is used on a post that is waiting for its page, the post goes back to being a draft, as a scheduled one does, and a reviewer saves it with When the page goes live again. UmbSocial never releases a post written with AI that nobody has reviewed.
Choosing which properties describe a page
Section titled “Choosing which properties describe a page”By default, Share on social… reads a page’s description from a Meta description property (alias metaDescription) and its image from an Open Graph image property (alias ogImage), where the page’s document type, or one of its compositions, has them. To read other properties, or to start every post about a type of page in a campaign, add the document type under Pages on social in Settings › UmbSocial › Schedule & writing. See Posting schedule and time zone.
With UmbSocial Pro
Section titled “With UmbSocial Pro”- A template can be tied to document types, so Share on social… on a page of one of those types starts from the template.
- Pages of a document type can post automatically each time they’re published, once for each page and language, and an editor can turn it off for a page on its UmbSocial tab.
- An approver can approve a post to wait for its page.
Error codes
Section titled “Error codes”| Code | Meaning | What to do |
|---|---|---|
page.not_found |
The page doesn’t exist any more, or it is in the recycle bin. | Choose another page, or restore the page. |
page.no_access |
You don’t have Browse on the page, so a post can’t be tied to it. | Ask an administrator for Browse access to the page. |
page.culture_invalid |
The page doesn’t have that language, or a language was given for a page that doesn’t vary by language. | Choose one of the page’s languages (or none for an invariant page). |
field.required:culture |
The page varies by language, and no language was given. | Choose the page’s language. |
schedule.needs_page |
When the page goes live was chosen for a post with no page. | Share the post from a page, or choose another time. |
schedule.delay_invalid |
The choice under After the page goes live isn’t one of the four. | Choose the next free slot, straight away, 1 hour or 1 day. |
post.live |
The post is already live on a channel, so it can’t wait for a page. | Leave its timing as it is. |
Every code is in Error codes.