<?xml version="1.0" encoding="utf-8"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Screenly 26.7.0 | Screenly</title><description>What has shipped across Screenly, newest first.</description><link>https://www.screenly.io/releases/screenly/26.7.0/</link><language>en</language><atom:link href="https://www.screenly.io/releases/screenly/26.7.0/rss.xml" rel="self" type="application/rss+xml"/><lastBuildDate>Fri, 24 Jul 2026 00:00:00 +0000</lastBuildDate><item><title>Screenly 26.7.0: Playlist schedules are now built from rules you can read</title><link>https://www.screenly.io/releases/screenly/26.7.0/playlist-schedule-rules/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.7.0/playlist-schedule-rules/</guid><pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate><category>release</category><category>content-management</category><description>&lt;p&gt;Scheduling a playlist used to mean filling in a condition builder and then trusting that the
result said what you meant. If a playlist had three rules, working out when it actually played
took some reading.&lt;/p&gt;
&lt;p&gt;The Schedule tab (Playlists &amp;gt; a playlist &amp;gt; Schedule) now lists each rule as a line of plain
text, naming the dates it covers, the days of the week it runs on, and the hours it plays,
instead of a form you have to read back to yourself. Above the list, an Effective schedule block
states when the playlist plays once every rule is taken together. A playlist with no rules says
so directly: &amp;ldquo;Always active. This playlist plays on every screen, every day, all day.&amp;rdquo;&lt;/p&gt;
&lt;p&gt;Editing a rule opens a dialog split into Dates, Time of day, and Days of week, so you work on one
part of the schedule at a time and watch the sentence update as you go.&lt;/p&gt;
&lt;h2 id="rules-that-will-not-do-what-you-meant-say-so"&gt;Rules that will not do what you meant say so&lt;/h2&gt;
&lt;p&gt;A schedule can be self-contradictory in ways that are invisible until nothing plays. Each rule
now carries its own status:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Never plays, for a rule whose conditions cannot all be true at once, such as a date range that
contains none of the weekdays it allows&lt;/li&gt;
&lt;li&gt;Expired, for a rule whose end date has passed&lt;/li&gt;
&lt;li&gt;Pending, for a rule that has not started yet&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id="dates-can-have-exceptions"&gt;Dates can have exceptions&lt;/h2&gt;
&lt;p&gt;A rule can now exclude individual days inside its own range, which is the difference between a
QSR menu board that runs every day of the year and one that runs every day except December 25.
Excluded dates show as removable labels under the date range, so a closure that moves is one
label to swap rather than a schedule to rebuild.&lt;/p&gt;
&lt;h2 id="schedules-the-rules-cant-show"&gt;Schedules the rules can&amp;rsquo;t show&lt;/h2&gt;
&lt;p&gt;A schedule created through the API that the dashboard can&amp;rsquo;t read at all stays read-only, as
before, with the same notice. A schedule the dashboard can read but can&amp;rsquo;t turn into rules, or
one too large for the editor, is now read-only too, with a notice saying it is too complex to
show as rules. The old condition builder let you edit some of these in the dashboard; now they
can only be changed through the API. Either way the playlist keeps playing exactly as it did.&lt;/p&gt;</description></item><item><title>Screenly 26.7.0: Installed app settings open instantly</title><link>https://www.screenly.io/releases/screenly/26.7.0/installed-app-settings/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.7.0/installed-app-settings/</guid><pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate><category>improvement</category><category>apps</category><description>&lt;p&gt;Installed app settings open right away now. Go to Apps &amp;gt; My Apps &amp;gt; an app and the settings are
simply there, with no page reload between you and them. Adding a new app works the same way.&lt;/p&gt;
&lt;p&gt;You feel it most when setting up several apps in a row, or when adjusting one app and checking
the result: what used to be a stack of page loads is one continuous flow.&lt;/p&gt;</description></item><item><title>Screenly 26.7.0: Subscription changes now say how many seats or screens were disabled</title><link>https://www.screenly.io/releases/screenly/26.7.0/subscription-change-notifications/</link><guid isPermaLink="true">https://www.screenly.io/releases/screenly/26.7.0/subscription-change-notifications/</guid><pubDate>Fri, 24 Jul 2026 00:00:00 +0000</pubDate><category>fix</category><description>&lt;p&gt;When a subscription&amp;rsquo;s member or screen count is reduced, Screenly disables the excess seats or
screens automatically, so a workspace over its new limit does not have to be sorted out by hand.&lt;/p&gt;
&lt;p&gt;The dashboard notification about it failed to post, so the change happened without an
explanation attached. That notification now appears, with the new subscription size and how many
members or screens were disabled, for example &amp;ldquo;Subscription updated to 1 screen. 1 screen
disabled.&amp;rdquo;&lt;/p&gt;</description></item></channel></rss>