CMS Load strange behaviour (support gives all green but it only retrieves 104 item

Attributes
1

as you can see here there’s a temporary label with the items count
also you’ll see all the labels with values i use for filtering, those fields are normally hidden, i’m showing it for debug purpose

what i’ve done (but i’m not sure if it’s the reason behind the problem)
was moving the initialization code in a separate js file (it was becoming difficult to read)

here’s the script
https://alporifesta.com/mlk-js/finsweet-loader/finsweet-loader.js

filtering, nesting etc… work just fine, i trigger the finsweetLoadComplete event so i know when to activate some element (like the full text search and another integration we have that needs finsweet to finish first)

the product in the table are 273, now items-count it’s showing 104 (and is showing a strange behaviour on the bottom, it shows some “nested” element out of context, only if the page is not filtered. if i look at the code thought developer tools i can see that those strange links are on the same level of the collection items, this is pretty strange, there’s no way to create something at the same level of the collection item in webflow

i’d really appreciate your help here

thank you as always

2

hey @gianluca! Can you share a read-only link?

3

hi Luis

https://preview.webflow.com/preview/alpori-festa?utm_medium=preview_link&utm_source=designer&utm_content=alpori-festa&preview=c6fc4858d7836a1036dcce7f1f616ae2&workflow=preview

4

Hey @gianluca! I’m afraid no matter what I do or how I set up the list I always get this error. I’ve traced it down to CMS Load being the culprit with the current setup.

Screenshot 2024-07-24 at 14.33.09
Screenshot 2024-07-24 at 14.33.093420×674 132 KB

Could we try some changes?

Could you please:

  • Remove the script where we load the scripts dynamically.
  • Add all the scripts that you need to the <head> one by one, start by adding CMS Load and testing.
  • Ideally rebuild the page from scratch, if not possible, please take the list out of the form.
  • Check if the new setup also causes the same error on the console.
5

Hi Luiss,

sorry i havent had time to work on this project in the past few days.

I found some other info on the problem by accident, i was working with an alternate global search version inside the dropdown header but now our customer want another feature with priority, so i stashed my changes and restored the previous version of the dropdown search, now the load is working fine. I think it may have somethign to do with instances with wrong names, i will do more research an let you know, i will try you suggestion also

thank you for your time as always

6

Thank you for letting me know @gianluca!

Let me know if you need help with any other issue! :muscle: