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

I/O Exception after importing layout with playlists from version 2.3.17 to 4.x.x #3535

Closed
ifarzana opened this issue Oct 24, 2024 · 0 comments
Assignees
Labels
Milestone

Comments

@ifarzana
Copy link

ifarzana commented Oct 24, 2024

When importing a layout with playlists containing a number of playlists from version 2.7 into version 4.x, the lkplaylistplaylist table does not correctly populate the necessary records, particularly for depth=1. As a result, the player reports that the layout is invalid and does not display it, generating the following error:

Prepare Image - I/O Exception, please check your selected storage.

Steps to Reproduce:

  • Export a layout with playlists from version 2.3.17
  • Import the layout into version 4.1.1.
  • Schedule the layout on the player.
  • Run the following query to check for missing records:
SELECT * FROM lkplaylistplaylist;
Observe that the table lacks the expected entries for depth=1.

Investigation:

  • The videos in question are present and can be downloaded from the CMS library.
  • The XLF in the layout editor shows the correct files.
  • Upon reviewing the closure table for the playlist, it seems incomplete.

Expected Behaviour: The lkplaylistplaylist table should be fully populated with the correct records, ensuring all playlists are properly associated with the layout and the layout plays without errors

Actual Behaviour: The table does not contain the expected records for depth=1, leading to incomplete playlist associations and potential layout failures.

Workaround: Manually removing and re-adding the playlists to the layout resolves the issue, as it regenerates the missing records.

The internal layout ID 2479 in development highlights the current issue.

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

2 participants