-
Notifications
You must be signed in to change notification settings - Fork 120
Plugin being moved to Deactivated directory #762
Comments
More details:
|
Cloned again, this time keeping it root owned, so PMS can't remove it and noticed these logs. It seems to pull this version:
... seems it's trying to auto update and fails...? |
When I copied the contents from Staged directory as Plugins/Sub-Zero.bundle, it still tries to update and move it:
|
How are you installing Sub-Zero? Which version do you use? |
@pannal with git clone and master branch, likely 3f47c1b, as the other instructions do not work, there's no install method that I could find from https://app.plex.tv/desktop. And my second note also indicates that I use the git clone mechanism: Here's another problem that should be addressed separately, hash length difference triggers re-install: (2cc5463 => 2cc5463), but I'm not sure if that problem is of publishing this bundle or Plex itself, I'm not familiar with the ecosystem. |
My install methods is setup that i clone as root to:
cloning as Please indicate what is the correct way of installing, and ensure those instructions are present in README. |
Which branch do you checkout? If it's not a develop branch, Plex will auto-upgrade/downgrade. Try this branch: https://github.com/pannal/Sub-Zero.bundle/tree/develop-2.6 It has a flag set so that Plex doesn't handle it automatically. |
Or you can set the flag yourself for the version you desire - it's in Contents/Info.plist |
@pannal, I checked out the default branch:
|
@pannal do the install instructions in the readme work in any setup anymore?
I don't even have a search option there... How the plugin must be installed today? |
Installation instructions were not up to date, you're right. Fixed that. Nowadays, as Plex removed most of their Plugin features, you'll have to do a manual installation. If you stay with an official release of Sub-Zero, it will still get auto updates via the plugin repository. For the non-official stuff you need to set the dev flag. |
@pannal but the problem reported here is that once auto-update is completed, the plugin is deactivated. |
Yeah I have no idea to be honest. You'd need to checkout either the develop-2.6 branch or the master branch and set the Dev flag to skip the auto update. |
@pannal thanks for the answer. I've done so for now. But the issue can be kept open, to be fixed properly in the future. |
Something fishy is happening with Plex.
I noticed such logs in my system:
I checked the container, indeed the directory was empty. Ok, I had docker restart, maybe that's fault. Cloned again.
And at some time later, again, the directory is emptied.
Seems it's moved to
Plug-in Support/Data/com.plexapp.system/DataItems/Deactivated/com.plexapp.agents.subzero/Sub-Zero.bundle/Sub-Zero.bundle
Why? how to prevent this from happening?
I've kept my plex media server to old version due the new agenda problem:
so, it's not related to some recent Plex update and plan to kill plugin support?
My current version is this docker image:
linuxserver/plex:1.20.3.3437-f1f08d65b-ls119
The text was updated successfully, but these errors were encountered: