Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes to Playlist not updated in scheduled Layout #1871

Closed
DanielBW1 opened this issue Jul 12, 2019 · 2 comments
Closed

Changes to Playlist not updated in scheduled Layout #1871

DanielBW1 opened this issue Jul 12, 2019 · 2 comments
Labels
Milestone

Comments

@DanielBW1
Copy link

CMS Version: 2.0.3

Issue: Create a Playlist. Next create a Layout and use the Sub Playlist widget to add that Playlist you created to your Layout. Publish the Layout and schedule it to a Display.

If you now make a change to timeline for the Playlist that the Layout is using, the changes are not sent to the Display, which continue to play the original timeline the Playlist had when scheduled.

Notes:

  • When you make a change to the Playlist, the Status of the Display does not change.

  • If you make the change to the Playlist, then open the Layout in Designer, the changes will be acknowledged and the Display will change to cloud status. The Display will then download those changes on the next collect interval. You do not need to checkout the Layout, only open it in Designer.

@DanielBW1 DanielBW1 added the bug label Jul 12, 2019
@DanielBW1 DanielBW1 added this to the 2.0.4 milestone Jul 12, 2019
@exalate-issue-sync
Copy link

Dan Garner commented: This is not a bug, but we should verify the process works in full. There is supposed to be a disconnect between editing a playlist, and having that updated in layouts
The Regular Maintenance runs and builds the Layouts, which then marks the displays as requiring download.

We will test and confirm this is happening as expected.

@exalate-issue-sync
Copy link

Dan Garner commented: If the CMS has memcached configured we have an issue with settings.php file being loaded more than once, which means the task runner is using a different cache. This also explains: #1859

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant