-
Notifications
You must be signed in to change notification settings - Fork 292
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
Reload the .m3u file automatically every time you connect #116
Comments
Playlist is reloaded automatically every time starting the plug-in if option in preferences "At what hour should plug-in automatically reload the M3U files?" is set to "never", however please keep in mind that Plex likes to keep plug-ins in the background so it might require to restart the Plex Media Server for playlist to reload. You can always force playlist reload manually by enabling manual reload in preferences (11th option) and clicking new button in the main menu: |
In the previous updates, the .m3u file is updated automatically. |
I can not reproduce the problem You are having. Maybe You are misunderstanding the concept: in version 1.x playlist was reloaded every time entering the menu (like now in IPTVLite) but it was inconvenient to browse the channels with bigger playlists because after every click user had to wait for plug-in to read whole playlist again and again. Because of that in version 2.x playlist is cached and reloads only on set time once per day or when plug-in is started (for most users this is enough, they just set the playlist and use it without constant edits). However plug-in start is not always registered by Plex Server so it might require to restart the server. If you need to constantly edit the playlist, just use manual reload button. If You're dying to cripple Your usage experience, change line 95 in init.pty file from |
Hello I would like to be able to reload the .m3u file automatically with each connection.
I should edit code but I tested a lot in m3u_parser.py but nothing works.
help me please
The text was updated successfully, but these errors were encountered: