Hi Team, hope you’re doing well.
I’m running into an issue with the new facet-count feature on my Webflow site.
On initial page load, every filter’s count displays “0” and only updates to the correct numbers once
I manually check or uncheck a filter option. After refreshing, they go back to zero again.
Can you help me understand why the facet-count script isn’t executing on page load, and advise how to get it to calculate and display counts automatically without requiring a filter interaction first? Would really appreciate your guidance!
Hey @olegrij90! Could you share a read-only link? I’ll have a look!
Sure thanks!
And @Support-Luis , since you’re already checking could you also take a look at the tags?
For some reason, the same tag appears under multiple categories, even ones it shouldn’t be linked to.
Not sure why that’s happening.
@Support-Luis or should i open new one also for tags?
Hey @olegrij90, we have noticed an issue with the nested lists and filter. We are taking a look at it and will be pushing a fix soon. Your issue may be related to this.
Apologies for the inconvenience.
On another note, I noticed there are some V1 attributes for filtering still on the page. I recommend you remove them so as not to cause any conflict between versions.
Hi @Support-Luis, thank you very much for the quick response!
I actually discovered that if I remove the entire nested CMS wrapper, the facet counts start showing correctly again but I still have the same tag/filter issue demonstrated in my video.
In Attributes v1, I could include a nested CMS list directly on the page alongside the main CMS and filtering worked flawlessly.
Is there any guide or documentation on filtering nested CMS items in Attributes v2?
I know v1 had a detailed how-to and I’d love to see the equivalent for v2 if it’s available.
Thanks again for your help!
@Support-Luis just to clarify do you expect the nested-list/filter issue to be resolved on your end, or is it something in my implementation that I need to adjust?
This is a large new project where the filter + nested CMS system was built with Attributes V1 and worked flawlessly.
If the V2 fix is coming soon, I’m happy to wait and continue upgrading.
Otherwise, I’ll revert back to V1 for now.
Appreciate any guidance you can share!
Best,
Oleg
Correct, we are looking into the root of the issue. The fix should come by next week.
Reagrding the tag issue, seems that an operator is being added to the tag-value something that I cannot replicate on this example, even if the tag setup is identical.. I’ll keep digging and I’ll get back to you
