The discussion revolves around a bug where the category color selector fails to display already-used colors correctly when lazy-loaded categories are enabled. Moin observes that the color picker only shows colors from categories visible in the sidebar until the parent category dropdown is opened, at which point the full data loads and colors display correctly. j.jaffeux acknowledges the limitation, noting that lazy loading is intended for sites with many categories — where users are unlikely to view hundreds of colors — and suggests that fixing this would require a new system, which is not currently a priority. Moin proposes disabling color separation entirely when lazy loading is active and notes that testing without the feature enabled is now difficult due to limited visibility of which groups have it turned on.
Continuing the discussion from Simplified category setup:
To me, it seems as if the data the color picker needs may not be available when lazy-loaded categories are enabled. It only shows the colors of the categories in my sidebar as used.
Once I open the dropdown to select a parent category, the category data is loaded, and the colors already in use show up correctly.
Yes Im aware there are limits with lazy loaded, Im not sure we are going to fix them though. Lazy loaded is designed for A LOT of categories, and no one is going to look at hundreds of colors. We need a different system here if we want to support this, which I dont think will be a priority, sites requiring lazy loading of categories are quite rare in the big scheme of things.
Is it possible to simply not separate the colors when lazy loaded categories are enabled?
Testing with lazy loaded categories is also more of an oversight. It’s now difficult to test without the setting being enabled because I can’t easily see which groups it’s enabled for.
