<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Screenly 26.7.1 | Screenly</title><description>What has shipped across Screenly, newest first.</description><link>https://www.screenly.io/releases/screenly/26.7.1/</link><language>en</language><atom:link href="https://www.screenly.io/releases/screenly/26.7.1/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Mon, 27 Jul 2026 00:00:00 +0000</lastBuildDate><item><title>Screenly 26.7.1: Screens show connectivity and content status separately</title><link>https://www.screenly.io/releases/screenly/26.7.1/screen-status-and-content-status/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.7.1/screen-status-and-content-status/</guid><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><category>improvement</category><category>monitoring</category><description>&lt;p&gt;A screen&amp;rsquo;s status used to answer two questions at once: can we reach it, and does it have what it
is supposed to be playing? Those are different problems with different fixes, and a single column
could only ever tell you about one of them.&lt;/p&gt;
&lt;p&gt;They are now two columns on the Screens list. Status says whether the screen is reachable:
&amp;ldquo;Online&amp;rdquo;, or &amp;ldquo;Last seen 5 hours ago&amp;rdquo; for one that is not, with the exact time on hover, and the
date and time once it has been gone more than a day. Content status says whether the screen has
what it should be playing: &amp;ldquo;All content is up to date&amp;rdquo;, &amp;ldquo;Syncing content&amp;hellip;&amp;rdquo;, or &amp;ldquo;Updates
pending&amp;rdquo; for a screen that has changes waiting and needs to reconnect before it can collect them.
Both columns sort, so you can bring the screens that need attention to the top either way.&lt;/p&gt;
&lt;p&gt;The distinction is the point. A screen that went offline an hour ago after syncing everything is
fine until someone changes its playlist. Once someone does, it has updates pending, and it used to
read Offline exactly like the one with nothing waiting.&lt;/p&gt;
&lt;p&gt;A screen with nothing scheduled is also no longer singled out. It used to report Inactive, which
put &amp;ldquo;nothing scheduled yet&amp;rdquo; in the same bucket as a fault. A screen that is reachable and up to
date now reads Online whether or not it has anything to play.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;Your status counts will look different:&lt;/strong&gt; the cards above the Screens list, and the ones on
Home, are counted from connectivity and content separately, which means a screen can now appear
in more than one card. An offline screen with pending changes counts in both Offline and Pending
sync, so Pending sync will read higher than before, and the four cards no longer add up to your
total number of screens.&lt;/p&gt;
&lt;/blockquote&gt;</description></item><item><title>Screenly 26.7.1: Screens with nothing scheduled no longer report Inactive</title><link>https://www.screenly.io/releases/screenly/26.7.1/screen-statuses-api-change/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.7.1/screen-statuses-api-change/</guid><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><category>improvement</category><category>monitoring</category><category>developers</category><category>api</category><description>&lt;p&gt;The screen &lt;code&gt;status&lt;/code&gt; value changed on both v4 and v4.1. A screen that is reachable and in sync but
has nothing scheduled used to report &lt;code&gt;Inactive&lt;/code&gt;. It now reports &lt;code&gt;Online&lt;/code&gt;. Nothing else about the
field changed: &lt;code&gt;Out of sync&lt;/code&gt;, &lt;code&gt;Offline&lt;/code&gt; and the rest behave as they did, and a disabled screen
still reports &lt;code&gt;Inactive&lt;/code&gt;.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;If this affects you:&lt;/strong&gt; an integration that reads &lt;code&gt;status == &amp;quot;Inactive&amp;quot;&lt;/code&gt; to find screens with
nothing to play will now find none of them. Check for an empty playlist directly rather than
reading it off the status.&lt;/p&gt;
&lt;/blockquote&gt;</description></item><item><title>Screenly 26.7.1: Typing a status into the Screens search no longer filters by it</title><link>https://www.screenly.io/releases/screenly/26.7.1/status-search-removed/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.7.1/status-search-removed/</guid><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><category>removed</category><category>monitoring</category><description>&lt;p&gt;The search box on the Screens list used to match status words, so typing &amp;ldquo;offline&amp;rdquo; would narrow
the list to offline screens. It now matches screen names and label names only.&lt;/p&gt;
&lt;p&gt;The status cards above the Screens list do this job instead. Clicking Online, Pending sync,
Offline or Disabled filters the list to that group, which is also the only place where the counts
you are reading and the list you get are guaranteed to agree.&lt;/p&gt;</description></item><item><title>Screenly 26.7.1: Failed requests explain themselves in plain language</title><link>https://www.screenly.io/releases/screenly/26.7.1/clearer-failure-messages/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.7.1/clearer-failure-messages/</guid><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><category>fix</category><description>&lt;p&gt;When something failed in the dashboard, the notification sometimes showed a block of code instead
of an explanation. You knew something had gone wrong and nothing else.&lt;/p&gt;
&lt;p&gt;Failures now say what happened, in a sentence. A file over the size limit tells you the upload is
too large, and any other failure that comes back without a reason gets a plain sentence for its
kind, such as a missing permission or too many requests.&lt;/p&gt;</description></item><item><title>Screenly 26.7.1: Home loads even when its feeds don't, and other fixes</title><link>https://www.screenly.io/releases/screenly/26.7.1/fixes-and-improvements/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.7.1/fixes-and-improvements/</guid><pubDate>Mon, 27 Jul 2026 00:00:00 +0000</pubDate><category>roundup</category><description>&lt;ul&gt;
&lt;li&gt;Blog post titles on Home show apostrophes and punctuation correctly instead of codes like
&lt;code&gt;&amp;amp;#39;&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Home no longer fails to load when the YouTube feed behind its video panel returns an error.
The panel shows its fallback instead, and the blog panel stays empty if its feed can&amp;rsquo;t be
reached.&lt;/li&gt;
&lt;li&gt;The Go to Dashboard button on the dashboard&amp;rsquo;s error page works again.&lt;/li&gt;
&lt;/ul&gt;</description></item></channel></rss>