<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Screenly 26.8.3 | Screenly</title><description>What has shipped across Screenly, newest first.</description><link>https://www.screenly.io/releases/screenly/26.8.3/</link><language>en</language><atom:link href="https://www.screenly.io/releases/screenly/26.8.3/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Mon, 17 Aug 2026 00:00:00 +0000</lastBuildDate><item><title>Screenly 26.8.3: Landscape, Portrait, Full HD, UHD and Anywhere are no longer automatic labels</title><link>https://www.screenly.io/releases/screenly/26.8.3/system-labels-are-now-ordinary-labels/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.8.3/system-labels-are-now-ordinary-labels/</guid><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><category>removed</category><category>device-management</category><description>&lt;p&gt;Screenly used to put 5 labels on screens by itself: Landscape, Portrait, Full HD, UHD and Anywhere.
Screenly maintained them from each screen&amp;rsquo;s own properties, which meant you could not rename
them, delete them, or decide which screens carried them.&lt;/p&gt;
&lt;p&gt;They were not describing screens well enough to earn that. All but one of them stood in for
properties a screen already reports, and the two resolution labels were thresholds rather than
descriptions: Full HD went on anything from 1920x1080 up to just below 4K, so a 1440p display and
a 1080p one carried the same label, and a display below 1080p got neither. Displays that aren&amp;rsquo;t
16:9 fared worse, because both edges had to clear the bar: a 3840x1600 ultrawide counted as Full HD
rather than UHD, and a 1680x1050 display got no resolution label at all.&lt;/p&gt;
&lt;p&gt;The groupings were also seldom a useful target. Every portrait screen, or every Anywhere screen,
spans different sites, rooms and purposes that have nothing else in common.&lt;/p&gt;
&lt;p&gt;So they are ordinary labels now. The ones in your workspace keep the screens they were on, and
you can rename, delete or apply them like any label you made yourself.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;If a playlist plays on one of these labels:&lt;/strong&gt; it now plays on the screens that carried the
label at this release, and that set no longer updates by itself. A new landscape screen will not
join the Landscape label on its own, and a screen you rotate will not change labels. Check any
playlist that targets these five, and either maintain the label yourself or assign the screens
directly.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;p&gt;If your workspace already had its own label with one of those five names, the two are now a
single label holding both sets of screens.&lt;/p&gt;
&lt;p&gt;Targeting content by a screen&amp;rsquo;s own properties, rather than through a label standing in for them,
is what we are working on instead.&lt;/p&gt;
&lt;h2 id="for-developers"&gt;For developers&lt;/h2&gt;
&lt;p&gt;The label &lt;code&gt;type&lt;/code&gt; field on API v4 and v4.1 changes with this, and filtering by a removed type now
returns an error. &lt;a href="https://www.screenly.io/releases/screenly/26.8.3/label-type-api-values/"&gt;The API side of this change&lt;/a&gt;
lists the values that remain and what to update.&lt;/p&gt;</description></item><item><title>Screenly 26.8.3: The label type field on the API now has three values instead of nine</title><link>https://www.screenly.io/releases/screenly/26.8.3/label-type-api-values/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.8.3/label-type-api-values/</guid><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><category>removed</category><category>developers</category><category>api</category><description>&lt;p&gt;Labels on API v4 and v4.1 carry a &lt;code&gt;type&lt;/code&gt;, and that field described how a label was maintained.
With Screenly
&lt;a href="https://www.screenly.io/releases/screenly/26.8.3/system-labels-are-now-ordinary-labels/"&gt;no longer maintaining any label automatically&lt;/a&gt;,
6 of its 9 values no longer exist: &lt;code&gt;landscape&lt;/code&gt;, &lt;code&gt;portrait&lt;/code&gt;, &lt;code&gt;full_hd&lt;/code&gt;, &lt;code&gt;uhd&lt;/code&gt;, &lt;code&gt;anywhere&lt;/code&gt; and &lt;code&gt;virtual&lt;/code&gt;. What remains is
&lt;code&gt;all-screens&lt;/code&gt;, &lt;code&gt;manual&lt;/code&gt; and &lt;code&gt;screen&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Labels that reported one of the removed types now report &lt;code&gt;manual&lt;/code&gt;, since that is what they have
become, and keep their id. The exception is a workspace that already had a label of its own with
the same name, such as its own Landscape: the two were merged into that existing label, and the
former automatic label&amp;rsquo;s id no longer exists.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;If this affects you:&lt;/strong&gt; an integration that filters labels by &lt;code&gt;type=landscape&lt;/code&gt;, or any of the
other five, now gets an error back, because the value is no longer valid for the field. Filter
by label name instead, or read the screen&amp;rsquo;s own resolution and orientation where you were using
the label as a proxy for hardware. If you stored the id of an automatic label, look the label up
by name again.&lt;/p&gt;
&lt;/blockquote&gt;</description></item><item><title>Screenly 26.8.3: The App Store and your installed apps are now separate sections</title><link>https://www.screenly.io/releases/screenly/26.8.3/app-store-and-apps-split/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.8.3/app-store-and-apps-split/</guid><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><category>improvement</category><category>apps</category><description>&lt;p&gt;Apps was one page doing two jobs. It opened on the apps you could add, with a My Apps button
leading to the ones you had already installed, so anyone coming in to adjust an app already
running on their screens started among the ones they did not have.&lt;/p&gt;
&lt;p&gt;They are now two sidebar entries. App store is for finding and adding apps, Apps is for the ones
you have installed, and each opens where you meant to go.&lt;/p&gt;
&lt;p&gt;Both moved address as part of this, so a bookmark straight to the old Apps page needs updating to
the section you want.&lt;/p&gt;</description></item><item><title>Screenly 26.8.3: Pages behind a login are no longer turned away before they load</title><link>https://www.screenly.io/releases/screenly/26.8.3/authenticated-web-assets-capture/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.8.3/authenticated-web-assets-capture/</guid><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><category>fix</category><category>content-management</category><description>&lt;p&gt;This finishes the work on pages behind a login that Screenly renders on its own servers, which we
&lt;a href="https://www.screenly.io/releases/screenly/26.8.1/authenticated-web-assets/"&gt;started earlier this month&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Pages that took more than 2 seconds to respond once signed in were still being turned away before
they loaded, so the screens showing them displayed nothing at all. A blank screen is harder to
work out than a login page, because there is nothing on it to tell you what went wrong.&lt;/p&gt;
&lt;p&gt;Those pages are captured and reach the screen now.&lt;/p&gt;</description></item><item><title>Screenly 26.8.3: Sidebar and sign-in icons show up in Safari</title><link>https://www.screenly.io/releases/screenly/26.8.3/fixes-and-improvements/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.8.3/fixes-and-improvements/</guid><pubDate>Mon, 17 Aug 2026 00:00:00 +0000</pubDate><category>roundup</category><description>&lt;ul&gt;
&lt;li&gt;Icons that appeared blank in Safari, in the sidebar and on the sign-in buttons, now show up.&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>