# I have more than one instance of CMS load but it's not working

**URL:** <https://forum.finsweet.com/t/i-have-more-than-one-instance-of-cms-load-but-its-not-working/3162>\
**Category:** Attributes\
**Tags:** cmsload\
**Created:** [July 23, 2024, 4:23pm UTC](https://forum.finsweet.com/t/i-have-more-than-one-instance-of-cms-load-but-its-not-working/3162 "2024-07-23T16:23:03Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![cpalma121](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/cpalma121/32/1215_2.png) [@cpalma121](https://forum.finsweet.com/u/cpalma121)\
**Post date:** [July 23, 2024, 4:23pm UTC](https://forum.finsweet.com/t/i-have-more-than-one-instance-of-cms-load-but-its-not-working/3162/1 "2024-07-23T16:23:03Z")

</div>

On this page, I have two instances of CMS load for Articles and Press: [Expert Insights and Personal Stories | Betterleave Resources](https://www.betterleave.com/blog)

I utilized the documentation to lay them out like this:  
fs-cmsload-element = “list”  
fs-cmsload-element = “list-2”

fs-cmsload-element = “page-button”  
fs-cmsload-element = “page-button-2”

The pagination under “Press” doesn’t function correctly. Can you help fix?

---

<div class="post-metadata">

**Author:** ![Support-Luis](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/support-luis/32/53_2.png) [@Support-Luis](https://forum.finsweet.com/u/Support-Luis)\
**Post date:** [July 23, 2024, 7:41pm UTC](https://forum.finsweet.com/t/i-have-more-than-one-instance-of-cms-load-but-its-not-working/3162/2 "2024-07-23T19:41:04Z")

</div>

hey @cpalma121! The load mode attribute does not need an `-x` identifier.

Removing the number from the second list load mode attribute should do the trick.

Let me know how it goes 😉

---

<div class="post-metadata">

**Author:** ![cpalma121](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/cpalma121/32/1215_2.png) [@cpalma121](https://forum.finsweet.com/u/cpalma121)\
**Post date:** [July 24, 2024, 4:30pm UTC](https://forum.finsweet.com/t/i-have-more-than-one-instance-of-cms-load-but-its-not-working/3162/3 "2024-07-24T16:30:41Z")

</div>

That worked! The only thing is when I click on the pagination for the Press section, it scrolls up to the top of the Blog Section. Is there a way to adjust this so it scrolls up to Press Only?

[https://preview.webflow.com/preview/betterleave-client-first?utm\_medium=preview\_link&utm\_source=designer&utm\_content=betterleave-client-first&preview=b7ceb2da671121d1cc602a9d816681ef&pageId=654d8277058b6fd5b3ecc869&locale=en&workflow=preview](https://preview.webflow.com/preview/betterleave-client-first?utm_medium=preview_link&utm_source=designer&utm_content=betterleave-client-first&preview=b7ceb2da671121d1cc602a9d816681ef&pageId=654d8277058b6fd5b3ecc869&locale=en&workflow=preview)

---

<div class="post-metadata">

**Author:** ![Support-Luis](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/support-luis/32/53_2.png) [@Support-Luis](https://forum.finsweet.com/u/Support-Luis)\
**Post date:** [July 24, 2024, 5:47pm UTC](https://forum.finsweet.com/t/i-have-more-than-one-instance-of-cms-load-but-its-not-working/3162/4 "2024-07-24T17:47:39Z")

</div>

Sure! So I see you also removed the `-2` from the list element attribute.

My instructions may have been confusing. You do need the `-2` for the list element and the scroll anchor elements. Only the load mode does not require this suffix.

Check this video →   
[Expert Insights and Personal Stories | Betterleave Resources - 24 July 2024 | Loom](https://www.loom.com/share/0a9aafbaa4f84f5192b5dfe99c5bf362)

Both lists scroll to their own anchor

---

<div class="post-metadata">

**Author:** ![cpalma121](https://dub1.discourse-cdn.com/flex013/user_avatar/forum.finsweet.com/cpalma121/32/1215_2.png) [@cpalma121](https://forum.finsweet.com/u/cpalma121)\
**Post date:** [July 25, 2024, 7:58pm UTC](https://forum.finsweet.com/t/i-have-more-than-one-instance-of-cms-load-but-its-not-working/3162/5 "2024-07-25T19:58:48Z")

</div>

Ah Thank you! It’s working like it should now.
