After the release is before the release.
0.8.0-beta1: script.plexmod.zip (2.8 MB)
Temporary Changelog:
This obviously severely changes how often we send timeline data. It should be fine™, but needs to be thoroughly tested.
Edit: Don’t expect many updates in the next few weeks, I’m taking a short break from the project 
- the last few weeks/months have been intense.
Enjoy your well deserved break! 
Thank you for everything done for us, we appreciate you and have a good time.
Thanks for another great release! Hope you have a good break away from the project!
@DimitarTsenev - now that the pm4k template system is out of beta, any chance you might revisit some of your theme enhancements (modern details screen, season screen, etc)?
He has an open PR on github which will need to be rebased on the latest version. In order for him to be able to actually provide the templates the way he’s shown, I also need to expose more data to them. From within PM4K.
I had an idea for dynamic python extensions from the userdata folder as well, but if we ever want to see PM4K updated in the official Kodi repository, we can forget that pretty much.
But we can certainly aim for 0.8.0 to support the templates he’s creating.
Food for thought when you come back: Rolling Release - happy holidays
Yeah not easy to do with how kodi repositories work, sadly.
Edit: Hmm, I think there is a way, and a pretty elegant one. The only caveat would be that you can only install the latest beta, not any previous ones.
Edit 2: Just a quick writeup of the idea:
Create a Service-Addon for Kodi (“PM4K Beta Updater” or something), that reads addon.xml from Github/Develop_kodi21 every X hours. If it finds a newer version, it sends a “signal” (sets an InfoLabel on Kodi Home window), which PM4K reads and offers an upgrade. If accepted, this pings back to the service and closes, which then waits for PM4K to close, downloads the raw repository zip, removes PM4K (not the data, only the addon) and unzips the zip, then starts PM4K again.
The crucial part is permissions, if a different addon can’t write to the addon folder of another one (which I doubt), PM4K’d need to do the final unpacking, which shouldn’t be a problem, either.
This should not take more than an evening to build.
Edit: Maybe add an option to instantly check for updates from within PM4K
to add to the updater idea:
branch picker: stable or testing so can flick between them
Hmm no. That would make this “quick solution” too complicated. I’d say a beta release setting inside PM4K controls whether the service does its thing, and when you want to go back to stable, you simply disable that and install the latest stable from the kodi repository again.
Also, I’ve just realized, I don’t need a separate addon for that. We already have a service endpoint for the kiosk/autostart functionality. I can just expand that one.
Edit: there is no stable/develop branch right now. We just tag a stable release.
Sure, that works too.
auto-update to 0.7.9-rev2
No servers found on start.
Cannot navigate within addon, all I can do is exit.
Fire TV stick (3rd gen) Fire OS 7.6.7.9
Kodi 18.9
Plex server 1.40.5.8897
Went back to 0.7.8 and working again.
Are there any settings I need to change prior to letting it update?
I had navigation issues after the upgrade to that version and after a restart it worked.
Kodi 18.9? isn’t that a very old version?
It’s from October 2020 so I’d say so yes.
Logs please (via DM ideally, or github). I don’t have a crystal ball
Edit: PM4K is supported and tested in kodi Leia (18). If it’s not working, something is wrong.
Okay if I can figure out where to find them. I’ll backup the user folder and see if I can find anything.
Edit: sent
Hmm. Now that I think of it, every stable version has a release on github. If we’re handling zip files, we can also offer the stable “branch”, easily.
Updating from 0.7.8 is a little problematic. If PM4K already runs, Kodi can start the upgrade in the background. That would normally be fine, but as we now dynamically compile the templates, we’re basically ripping them away from the already running addon (as the old one relies on static templates and those haven’t been built at that point in time), which results in undefined behavior. Not sure if I can fix that tbh.
Yeah it is. We officially still support it, though, and it’s a pain (because it’s the only version still supporting python 2.7, which is why I always have to make sure we’re py2/3 compatible). It seems like there’s enough users still out there using this version, due to some addons only available for that specific one.
I would like to thank panni for this incredible addon, it is impressive all the work he has behind, by the way a small question if anyone knows is there any way to synchronize what you have in plex to traktv somehow with the addon? Greetings
i was already running the beta’s when I upgraded.
