Heyyy, what’s up beautiful people! I’m just here to leave a bit of useful information about stretching the limits of Finsweet’s amazing solutions.
I started a project for a real estate agency a couple months ago and decided to put those functionalities to test in a very robust and complex project (based on my previous experience), and I did.
A lot of anxiety came along with the immediate fall in performance of the “Amazing Three”, specifically the CMS Nest. A bit of testing and guessing helped me figure out the problem, but the solution seemed to be gated behind either A) Finsweet+ or B) A developer and a lot of work.
But when hopes were fading, I FOUND IT! It was on Finsweet’s forum (read-only for free users) a post (mostly) solving the performance problem and I just want to put it here for future reference. This has been a pain for a while and I hope it helps who needs it.
Post copy
If your collection to nest is 100+ items you can try this:
For the CMS Nest script use this script:
<!-- [Attributes by Finsweet] CMS Nest -->
<script defer fs-attributes-preventload="true" src="https://cdn.jsdelivr.net/npm/@finsweet/attributes-cmsnest@1/cmsnest.js"></script>
Child collection (COLLECTION TO NEST)
Use CMS Load set to render-all
- Enable pagination with 100 items per page
- Activate Speed Boost
Use CMS Load callback to reinitialize CMS Nest
Add this snippet to </body>
tag
<script>
window.fsAttributes = window.fsAttributes || [];
window.fsAttributes.push([
'cmsload',
(listInstances) => {
window.fsAttributes.cmsnest.init();
},
]);
</script>
Original post
Bye bye