Pulse rebuilds entire xml cache when banning a wallbase image?


It seems that whenever I ban an image from rotation, pulse will rebuild the entire cache for all entries. Upon banning an image pulse hung for an approximate 10-15 mins before regenerating caches for all 21 of my wallbase image sources.


patricker wrote Dec 23, 2013 at 6:26 PM

I'll need to test this more, but it shouldn't be happening that way.

From what I see in the code, banning an image should have the same effect is manually skipping to the next picture. Does manually skipping to the next picture have this kind of effect on you?

medievalcuisine wrote Dec 24, 2013 at 12:36 AM

Manually skipping works fine, I'll test banning an image again just to confirm that is what caused the cache rebuild.

medievalcuisine wrote Dec 24, 2013 at 12:43 AM

Yep, confirmed that banning an image causes pulse to rebuild the entire xml cache for all of my image sources. I'm not sure if this only affects wallbase collection sources, as that is the only source type I use... (I have 21 sources and it rebuilds 21 cache files for them).