Tags don't work for exhibits created after 2022

Hi there.

I’m wondering if this might be a bug.

I am in the process of creating a browse page to allow users to filter our 50+ exhibits using tags at the top of the page. Users can select the topics that interest them to see the filtered list. I thought I had it working, but then I noticed some of the exhibits were missing. After much gritting and gnashing of teeth, I eventually realized that only the most recent exhibits were missing. Specifically, all exhibits created after January 2022.

Even though all of our exhibits each include tags on their config pages, the returned HTML is missing the “data-tags=x,y,z” for the exhibits added after 2022-01. You can see what I mean in this screenshot from Chrome dev tools:

And here is a screenshot showing the tags for the same exhibit via the Admin UI, where you can clearly see that the tags have been added.

I’ve looked at how these recent exhibits are configured, and I don’t see any differences from the older exhibits that work correctly. I should point out that after a long time without a systems person, it was right around 2022-01 that we began keeping up with Omeka updates. That included migrating everything to a new server. Did I miss some setting along the way? Or did the tagging feature break at some point?

I don’t see anything there to really suggest that there’s a problem with the tagging system; if the tags are showing up on the edit form, then they’re in the database.

Looking at the stock exhibits browse page for your site it shows the tags just fine for everything (specifically that’s a link to just the ones with the “Culture” tag.

I suspect the problem lies in the custom JS you’re using to pull in the tags from the API. Specifically, the problem is probably that you have 59 exhibits, but the API page limit is set to 50, so the 9 most recent exhibits are on “page 2” of the API response, which you’re not fetching. Though now that I look you may have found this out while I was typing this message?

1 Like

Doh! There was a 50-item limit set to API calls.

Sorry, I replied just as your message showed up. Yes, that was it. I needed to increase the number of items allowed for API calls.