Using a Child Page as a Page Include is not Showing the Page Region

  • 1
  • Question
  • Updated 2 months ago
  • In Progress
  • (Edited)
The include scripts seem to be trying to populate the page region (appending  from both child and master) but the result is empty html tag. 


Steps to reproduce:


Barebones Main Page (cleanPI), Master Page (cleanMaster), and Child Page (cleanChild) (below). No models, no query string. 

Main Page includes Child Page, 2 page titles (have tried including more components/models).

API: v1 Skuid 12.1.7

Expected:

Boo

Hello World

Actual:

Hello World

Thanks in advance for the help! 
________________________________________________________________
cleanPI (Main Page)
<skuidpage unsavedchangeswarning="yes" personalizationmode="server" showsidebar="true" showheader="true">
<models/>
<components>
<includepanel type="skuid" uniqueid="sk-1_9X-443" pagename="cleanChild"/>
</components> <resources> <labels/> <javascript/> <css/> <actionsequences/> </resources> <styles> <styleitem type="background" bgtype="none"/> </styles> <interactions/> </skuidpage>
cleanChild (Child Page)
<skuidpage unsavedchangeswarning="yes">
	<models/>
	<pageregioncontents>
<pageregioncontent regionid="onlyRegion" uniqueid="RegContent">
	<components>
		<pagetitle uniqueid="sk-1_Iw-389">
			<maintitle>Boo</maintitle>
			<actions/>
		</pagetitle>
	</components>
</pageregioncontent>
</pageregioncontents>
	<components/>
	<resources>
		<labels/>
		<javascript/>
		<css/>
		<actionsequences/>
	</resources>
	<styles>
		<styleitem type="background" bgtype="none"/>
	</styles>
</skuidpage>
cleanMaster (Master Page)
<skuidpage unsavedchangeswarning="yes" personalizationmode="server" showsidebar="false" showheader="false" cachepage="false">
	<models/>
	<components>
<pageregion uniqueid="onlyRegion">
	<styles>
		<styleitem type="background" bgtype="none"/>
	</styles>
</pageregion>
<pagetitle uniqueid="sk-1zyY-369">
	<maintitle>Hello World</maintitle>
	<actions/>
</pagetitle>
</components>
	<resources>
		<labels/>
		<javascript/>
		<css/>
		<actionsequences/>
	</resources>
	<styles>
		<styleitem type="background" bgtype="none"/>
	</styles>
<interactions/>
</skuidpage> 

Photo of Arne-Per Heurberg

Arne-Per Heurberg

  • 3,068 Points 3k badge 2x thumb
  • sure we'll figure it out

Posted 4 months ago

  • 1
Photo of Clark Cregg

Clark Cregg, Solutions Engineer

  • 1,290 Points 1k badge 2x thumb
Hello!

We have encountered this internally and logged it with the Product team. I will circle back here with any info once its made available.


Thanks for the clear reproduction of the issue and reporting it!

Clark
Photo of Arne-Per Heurberg

Arne-Per Heurberg

  • 3,068 Points 3k badge 2x thumb
Clark, any word on this? We have to start building this out soon. Thanks
Photo of Clark Cregg

Clark Cregg, Solutions Engineer

  • 1,290 Points 1k badge 2x thumb
Hello,

It is currently being reviewed by our product team. I cannot provide an ETA at this time.

I am assuming you are using Skuid Native Package on SFDC... How are you deploying your Skuid Pages?
Photo of Arne-Per Heurberg

Arne-Per Heurberg

  • 3,068 Points 3k badge 2x thumb
Thanks Clark. Yes skuid on SFDC.
Photo of Arne-Per Heurberg

Arne-Per Heurberg

  • 3,068 Points 3k badge 2x thumb
Nautilus was fun yesterday! Any word on this? Meeting this week with client and then build starts mid october. Thanks!
Photo of Arne-Per Heurberg

Arne-Per Heurberg

  • 3,068 Points 3k badge 2x thumb
Nice Timing. You should take the bow. I appreciate the fix!!
Photo of Brian Lee

Brian Lee, Official Rep

  • 620 Points 500 badge 2x thumb
Official Response
Thank you for your patience! Skuid has fixed the issue you raised regarding Child pages loaded in a Page Include component do not render as expected (issue CORE-2530) in the new 12.2.8 release which is now available on the Skuid Releases page.


As a reminder, Salesforce does NOT allow reverting back to prior versions of managed packages. Skuid always recommends installing new versions in a non-business critical sandbox environment to test all mission critical functionality before installing into a production environment. We also recommend that you update out of date themes after you upgrade. Please let us know if you continue to encounter any problems with this issue after upgrading.
 
Thanks again for alerting us of this issue!