Skip to content

Publishing changes

A change you save in the CMS is stored immediately, but not yet visible on the screens. Only once you publish does the player get a new version of the content.

Why a separate publish step

While editing you want to check how your playlist looks without the player jumping along at every intermediate step. The publish step makes the difference between “I am editing” and “this may go on the screen”.

When you publish, the CMS takes a snapshot of everything the screen needs: the linked playlist or sequence, the media files, the templates and the configuration. The player fetches this snapshot and plays from it. Until you publish a new version, the old one stays active.

When to publish

Publishing applies per screen. If you change a playlist that runs on five screens, all five have to be published again. In practice you do not have to do this one by one. This is how you see and publish what is pending:

  • At the top of the CMS is the Publish N screens button as soon as changes are pending anywhere. One click publishes all screens with changes in your organisation. When everything is live, the button shows Everything published.
  • In the screens list, each screen shows its status, see below.
  • On the screen itself (in Screens, open the screen) you publish with Re-publish only that one screen.

A change in Brand style (a new logo, other colours or another font) puts all screens of your organisation on Pending changes. Publish them with the button at the top. How to set the style is in Setting up brand style.

Automatic publishing

In two cases the CMS publishes without you having to do anything:

  • When you activate a new screen, the chosen content is put live automatically.
  • When a data connection refreshes automatically (for example new properties from your CRM), the CMS publishes the new data without any action from you.

Status of a screen

In the screens list, each screen has a status next to it:

  • Up to date: the player runs on the most recent publication.
  • Pending changes: there are changes ready that have not been published yet.
  • Never published: the screen is activated but nothing has been published to it yet.
  • Publishing…: a publication is running.
  • Failed: the last publication failed. Publish again with the button at the top or on the screen itself.

What if it does not work

I published but the screen still shows the old version

Online screens pick up a new publication within a minute. If the screen stays on the old version after a few minutes, it is probably offline (check the heartbeat in the screens list). It then picks up the change as soon as it is back online.

Publishing failed, now what

The banner shows Publish failed with a Try again button. Most errors are network glitches that succeed on a second attempt. If the error persists, email [email protected] with the screen name.

Can I roll back a publication

Not through the UI. After a wrong publication: change the content and publish again. The player fetches the newest version and the old one disappears.

The player shows an error saying there is no content

This happens when a screen tries to fetch content that has never been published. Open the screen in the CMS, link content and publish.

Was this helpful?