More than one Skuid page on a Single VisualForce Page

  • 1
  • Problem
  • Updated 4 years ago
  • In Progress
Hi Guys,

I want to run more than one Skuid page on a single VisualForce page (with multiple <skuid:page/> components).

Reading the commentary at http://help.skuidify.com/m/page-assignments-and-overrides/l/201793-using-the-skuid-page-visualforce-... it seems like this should be possible, however I can only ever get the first Skuid component within the VisualForce page to render.

Any ideas?
Photo of Dan Arnison

Dan Arnison

  • 320 Points 250 badge 2x thumb

Posted 4 years ago

  • 1
Photo of Irvin Waldman

Irvin Waldman, Champion

  • 9,006 Points 5k badge 2x thumb
Can you post your VF page markup?
Photo of Irvin Waldman

Irvin Waldman, Champion

  • 9,006 Points 5k badge 2x thumb
Rob, Just tried on my end and only the first Skuid page is loaded.  Checked the JS Console and no errors.  As you know, I am running RC1.
Photo of Rob Hatch

Rob Hatch, Official Rep

  • 44,006 Points 20k badge 2x thumb
Dan,  why are you not using a page include in the first Skuid page to include the second page - instead of trying to create a second page in VisualForce? 
Photo of Zach McElrath

Zach McElrath, Employee

  • 49,056 Points 20k badge 2x thumb
Dan,

You are correct, this does not currently work, as the tutorial would suggest --- any uses of <skuid:page/> after the first use will not result in any content for the subsequent pages appearing on the screen --- the first page's contents are shown, but not the second, third, etc.'s contents.

We are working to address this, we are treating it as a bug.

Zach
Photo of Dan Arnison

Dan Arnison

  • 320 Points 250 badge 2x thumb
Hi Guys,

Zack: Noted. Thanks for the heads up.

For context, this post is related to Glenn's previous post about cutting up a large page for performance. (https://community.skuidify.com/skuid/topics/how-to-structure-complex-related-pages-for-high-performa...).

A few months ago the page became unacceptably slow, so we implemented Zack's earlier suggestion to cache the page in VF and to load model data asynchronously. This has definitely helped.

Notwithstanding this, we are rapidly running out of headroom so I'm exploring our options. Regarding Rob's suggestion to use page includes- I've tried this in the past and found performance to be an issue. Additionally, splitting the page into multiple pages would have the added bonus of giving us back/forward buttons without implementing with history API- this is something we have wanted for a while and have not made time to do. Two birds with one stone as they say.

Thanks for your help and have a pleasant new years eve all,
Dan Arnison (PractiFI)
Photo of Zach McElrath

Zach McElrath, Employee

  • 49,056 Points 20k badge 2x thumb
This will be fixed in the next Superbank release candidate for Superbank (version 6.5+).