We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy. (Last updated on: June 24, 2019).
Unfortunately, activation email could not send to your email. Please try again.
Syncfusion Feedback

Tab content does not display in production build using ng-template content with separate component.

Thread ID:

Created:

Updated:

Platform:

Replies:

145982 Jul 16,2019 04:26 PM UTC Nov 20,2019 07:37 AM UTC Angular - EJ 2 4
loading
Tags: Tab
Scott Eaton
Asked On July 16, 2019 04:26 PM UTC

Tab content does not display in the production build (ng build --prod).  Everything works fine in the dev build (ng build).  The headers do display but no content.  Here is the ejs-tab html.  Any recommendations?  Let me know if you need anything else.

<ejs-tab id="tab_default" heightAdjustMode='Auto'>
<e-tabitems>
<e-tabitem [header]='headerText[0]'>
<ng-template #content>
<app-p-demo-view></app-p-demo-view>
</ng-template>
</e-tabitem>
<e-tabitem [header]='headerText[1]'>
<ng-template #content>
<app-p-prior-gift-view></app-p-prior-gift-view>
</ng-template>
</e-tabitem>
<e-tabitem [header]='headerText[2]'>
<ng-template #content>
<app-p-education-view></app-p-education-view>
</ng-template>
</e-tabitem>
<e-tabitem [header]='headerText[3]'>
<ng-template #content>
<app-p-custom-view></app-p-custom-view>
</ng-template>
</e-tabitem>
<e-tabitem [header]='headerText[4]'>
<ng-template #content>
<app-p-ticket-view></app-p-ticket-view>
</ng-template>
</e-tabitem>
</e-tabitems>
</ejs-tab>

Scott Eaton
Replied On July 16, 2019 06:17 PM UTC

Please disregard.  After upgrading the Syncfusion packages via npm everything seems to work fine!

Thank you,
SE

Karthigeyan Krishnamurthi [Syncfusion]
Replied On July 17, 2019 03:54 AM UTC

Hi Scott, 
 
Syncfusion greetings. 
 
We are happy that our latest version resolved your issue. 
 
Regards, 
Karthi 


marilyn winkler
Replied On November 19, 2019 08:59 AM UTC

Please disregard.  After upgrading the Syncfusion packages via npm everything seems to work fine!

Thank you,
SE

Updating to the last build version almost always resolves such issues as I've noticed from my own experience with multiple mistakes on builds not working.

Vinitha Devi Murugan [Syncfusion]
Replied On November 20, 2019 07:37 AM UTC

Hi Wioletta, 
 
Thanks for your update. 
 
We suspect that before updating the npm modules, packages will be loaded from npm cache. So it didn't work on building the project and might solved once the npm is updated with latest version. Please let us know if you require any further assistance. 
 
Regards, 
M. Vinitha devi 


CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

Please sign in to access our forum

This page will automatically be redirected to the sign-in page in 10 seconds.

Warning Icon You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.Close Icon

Live Chat Icon For mobile
Live Chat Icon