Visual glitch with default photos on taxon pages

Hello. I’m not sure how well I could explain this, but up until recently, the pages for higher-level taxa would display seven images like so:

If a taxon page has less than 8 images manually assigned to it, it will still display seven with the additional images coming from the subordinate taxa. For example, even though Solanaceae has only two photos set to its page, it still displays seven, with the additional five coming from the subordinate the subordinate genera and species. But recently I noticed that if a taxon page has less than eight images custom set to the page, it will display it like this:

This really should not be happening, and this may seem like a small issue, but it’s personally a little irksome because I have spent a lot of time arranging photos for higher-level taxa, and now a lot of that work is being obscured.

Anyone else notice this? What’s going on?


I’m not seeing this for anymore. If you have more examples, please provide URLs and screenshots.

If there are 8 or fewer photos, it displays with a main, large photo.
If there are 9 or more photos, it displays the grid mode.

Higher taxa should always display the grid mode, IMO, and pull from the default subordinate taxa photos when available, as before.

Another example


whereas adding a photo


1 Like

@kueda Any chance restoring grid view for higher taxa as it was before? Most higher taxon pages now just show one main image instead of a nice selection from the descendant taxa default photos.

Nope. We removed the backfill photos in an effort to reduce the time we spend re-indexing taxa (which we do a lot) and reduce the average size of the taxon responses from the API, which has pretty serious impacts on the amount of data transferred and memory usage in the apps, particularly when getting vision results. We think these benefits outweigh the benefits of grid vs. not grid on higher-rank taxon pages.

As I think I’ve written elsewhere, the best way to address the response size issue is to overhaul our API so clients can request smaller responses, which we’re starting to think about, but that’s a ways off, and even without that, the performance gains of not backfilling probably still outweigh the benefits of the grid view.

If you really want that grid back, just choose 9 or more photos for a taxon.

1 Like

lol you make this sound like a quick fix.

but, alright, that’s disappointing. won’t waste time with a feature request.