Only way it is wrong is if Plex is lying or if when you turn off reporting to Plex it does not report those in the stats.
According to a post made by Elan, It was 2% of clients. So that means if you used a lot of plugins on the server itself but didnāt expose these plugins to any users then your system 100% used them but would have 0% usage according to their stats.
Also Iāll add from a developer standpoint there is not much difference between Python 2.7 and v3. Iāve never come across a 2.7 set of scripts I couldnāt quickly go through and get to work with v3 quickly as itās mostly semantical changes a trained monkey could do. The keyword there is āmostlyā. There could be some things done that could require a minor rewrite but even this would not be very difficult as 2.7 and V3 just arenāt that different in the way they were used for plugins.
Plex could literally put out a beta if it wanted to that included V3 python engine and every plugin thatās being used could be converted/changed by users within a week itās so trivial IMHO.
Iām so willing to provide a banana tree if they would just do it. 
Iāve been reading a lot on these forums and I see that plugins will soon stop working. What I would like to know is when will it break the Trakt plugin. It sounds like the new server update will remove the trakt GUI from the web client. Is that true?
And if I really on Trakt, can I just keep toy current PLEX server version, or will there come a point when the iOS Plex app will have an update that requires a minimum server version to continue working.
And lastly, I see that the web tools plugin has found a workaround to still work. Can you use trakt with this method?
Thanks in advance.
I imagine so.
Almost certainly the latter at some point.
Though I donāt know the workings behind getting webtools up and running again I imagine it involved some work from @dane22.
However the trakt plugin guy has only been seen or heard of once in around 3 years so I think itās sadly unlikely.
How much it affects you is mostly a matter of your current usage scenario.
If you are just wanting trakt for a single user on a single server and donāt need trakt outside of Plex then we are already covered with GitHub - XanderStrike/plaxt: Webhooks based Trakt.tv scrobbling for Plex
But I appreciate thatās a very big if.
Finally it would be really cool if (unbeknown to us) Plex were working on native Trakt integration in the way that Emby does.
2 Likes
Thanks for the info. Very sad indeed. I think Iāll just postpone any updates until Iām forced. Maybe then update Trakt manually on the web. So sad 
Hopefully some other solution will present itself.
1 Like
WebTools was never compromised, since it use itās own webserver
I did however found a workaround for ExportTools but not something Tract can use
Maybe Kitana can be used here?
2 Likes
Interesting! Thanks. Looks a little complicated but I suppose if it does the trick.
1 Like
Yeah way beyond me too.
Plaxt 2 seems to be the best option https://github.com/XanderStrike/goplaxt in case anyone stumbles upon this thread like I did looking for a trakt workaround. Additionally I found the developerās shoutout to be hilarious, " Shoutouts to Trakt for their great API, and to Plex for killing the plugin directory."
1 Like
Yep I agree, hence my link to it earlier in the thread.
TBH Plaxt is a far better option than the trakt plugin anyway, at least for those with single Plex servers and no need for trakt usage outside of Plex.
And announcing the end of support for a feature does not mean that it was going to be removed! I expected plugins to still be available, but they would not add any more functionality. They could still return them, my NAS still has plugins because I have not, and WILL NOT update the software. So plugins can still work, on FireTV you just canāt see the Plugins.
Correct, the plugins feature was not removed, but as mentioned in the announcement, as apps get rewrites (such as adding the UNO interface), the plugins feature will not be added in.
Good luck.
Unfortunately, some devices do not allow prevention of updates (Roku, etc).
Even more do not allow rolling back.
Add that to the fact that there have been times that updates to a Plex client REQUIRED a minimum server version (as in the Roku client update of December 2018), then, we Plug-in users are eventually forcefully pushed away.
Seriously, will you stop.
When you are in full āflowā (sorry couldnāt resist) I end up spitting coffee or Jim Beam all over my laptop screen and keyboard. I think you already owe me three. 
2 Likes
ā¦ and what about the āIllegalā part?
So, in your mind: Plex should stand, chest puffed out, naked and unafraid, inside the cage with the Rankor, shouting obscenities at it having to do with itās Momās Virtue - so you can continue to watch crappy, illegally obtained and transmitted material.
That sound about right?
Hey, manā¦ my deep, unconditional love for Plex has waned quite a bit over the years, but I hope they arenāt stupid enough to try something like that - until Emby evolves into something Iād actually want to useā¦
1 Like
Here i go again. Ive been triggered. Whether his method of protest is constructive or not (it wasnāt really), stop using 3rd party plugin legality as an argument.
If thats the reason for removal, then Plex needs to stop being available in the US and similiar MPAA countries because it doesnāt allow us to watch DRM protected content. Instead, Plex support pages link to 3rd party tools for decrypting and remuxing into a format Plex can read.
A prosecutor would easily say plex recommends piracy just as easily as some of its third party developers do.
And, there are several non questionable plug-ins not being matched in function or quality.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
