search

lostb1t / replex

Remix your Plex hubs
204 stars 7 forks source link

Playlists break recommended on web #122

Closed sahara101 closed 3 months ago

sahara101 commented 6 months ago

Hi, if I click on Movies recommended I get the error Something went wrong An unexpected error occurred. Log says Response status=401 Unauthorized

Also, is it possible to maintain a trakt list order? I have a collection with same name on 2 libraries and are merged.

image

But the order is not the same as on the trakt list

billyors commented 6 months ago

I thought I was alone here. I'm seeing the same error and I think it started with one of the latest plex releases. Which client do you see the error with? Mine is only on the Web client. I haven't seen the issue with any other clients (Mobile, Roku, Android). This only applies to Replex. Hitting Plex directly doesn't seem to be an issue.

The trakt list thing, you should be able to append something like ?sort=released,desc to the end of the URL that you're pulling from. This works pretty well for playlists, I would imagine the same applies for collections. @lostb1t could probably identify the issue quicker, I think the caching in replex plays a factor with the sort order too.

sahara101 commented 6 months ago

I only tried the web one. ?sort=released,desc would not work here as the list is created with future releases in order.

billyors commented 6 months ago

It looks like there might be a fix to this that was just released today. Once the docker version is pushed I can verify. https://forums.plex.tv/t/plex-media-server/30447/616

(Web) Home Screen content would not load when unauthenticated. (DISCO-1547)

billyors commented 5 months ago

Took a while to circle back to this. Updating PMS didn't resolve this. But I think I figured it out.

@lostb1t if you're still monitoring this channel. There seems to be an issue with the Web browser client where if you have pinned Playlists to the Home page, Replex displays "Something went wrong/ Unexpected Error". Unpinning Playlists from the Home page fixes the issue. This only seems to apply to the Web client.

lostb1t commented 3 months ago

@billyors thanks for the headsup, marked this as a bug

lostb1t commented 3 months ago

:tada: This issue has been resolved in version 0.20.1 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: