causefx / Organizr

HTPC/Homelab Services Organizer - Written in PHP
GNU General Public License v3.0
5.17k stars 291 forks source link

random media wallpaper doesn't ever change #1937

Open killarny opened 1 year ago

killarny commented 1 year ago
Organizr Version: V 2.1.2430
Branch: Master
WebServer: Nginx
Operating System: Ubuntu (docker)

Problem Description:

I've had the "Use Random Media Wallpaper From Media Server" setting enabled for weeks now, and it doesn't ever change. It has been showing the same image the whole time of Tulsa King that it (presumably) picked up from my Plex configuration when I enabled it. As much as I like seeing Sylvester Stallone every time I log in 😁, I do have other stuff on my Plex that it could be using, but for some reason isn't.

image


Reproduction Steps:

Toggle the options I have showing in that screenshot above, I guess. Sorry, I wish I could be more helpful, but I honestly have no idea what would cause this.

Is there any other information I can provide to help figure this out?


Errors on screen? If so paste here:

causefx commented 1 year ago

are there a lot of images inside your data/cache folder?

killarny commented 1 year ago

Yes, the /config/www/organizr/data/cache folder has 85 images in it that appear to be covers from Plex. All but one of them are ####-list.jpg and one image is named 6044-np.jpg.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

killarny commented 1 year ago

Is there anything else I can provide to give insight into this issue? @causefx were you implying that I should clear the cache? (I haven't changed anything yet, in case I can be of further assistance here.)

causefx commented 1 year ago

it only creates -np files once someone watches a movie or item on plex while organizr is open. i will look into fixing this. thanks.

github-actions[bot] commented 1 year ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

killarny commented 1 year ago

Bumping so the overzealous GitHub bot doesn't close it prematurely.

causefx commented 1 year ago

I still haven't thought of or decided how I want to implement this yet.