List Nest + Tabs not working on production domain

Attributes
,
1

Hi Finsweet team,

I’m using the latest Finsweet Attributes script (v2) to load CMS content dynamically by using a combination of List Tabs and List Nest. My outer collection list serves as title for my dynamic tabs. My inner (nested) collection list should display al the articles which belong to a certain category. Everything worked perfectly on the Webflow staging domain (eccel-professional.webflow.io), but after switching to the live domain (eccel-professional.it), the nested collection list is no longer rendered.

Here’s what I’ve checked:

  • The attributes.js script loads successfully with a 200 OK status.
  • However, the script seems to not execute properly on the live domain.
  • List Tabs seems to work somehow - but still not 100%! The text with [fs-list-element=“tab-link”] gets injected correctly in the native Webflow Tab Links, but the text still shows up in Collection Item after the site is published.
  • The nested collection list does not show at all
  • No changes were made in Webflow between staging and production.
  • I’m seeing several Cloudflare-related CSP and console warnings on the live domain.
  • There are no proxies, Cloudflare or CSP in use, says the IT department from my client.

Read only: Webflow - Eccel Professional

Questions:

  1. Is there a chance that List Tabs and List Nest interfere, since they are sharing some identical attributes like [fs-list-element=“list”]
  2. Or what else could be blocking or interfering with the script execution?

Has anyone experienced similar behavior or knows a workaround?

Thanks in advance!
Lukas

2

Hi Lukas,

I’m facing the exact same problem, which is why I came to the forum. It was working perfectly until yesterday.

Hoping it’s a temporary issue.

image
image937×548 22 KB

1 Like
3

I am having the same issue. It started yesterday. It worked last week, nothing has changes but now it won’t load anything. I am getting the same error message.

image
image2626×766 140 KB

1 Like
4

Hi @lukasschorn23 @simona @eliezer.santos!

I will report this issue to the team. I’ll let you know when it’s fixed.
Thanks for sharing!

1 Like
5

I got it working again, my issue was that I had another div with nested collections. Once I removed that it works again. It would be great to if there is a way to make it work with nested collections as well.

6

Hi @simona!

Great to hear that you solved it, thanks!

@lukasschorn23, @eliezer.santos, could you try checking if it’s the same issue? If you need more assistance, please share a read-only link; my DMs are open!