Posted: 20 Nov 2018 2:30 EST Last activity: 11 Dec 2018 18:18 EST
Issue with Skin Inheritance
We are trying to refactor the application skin rules to have one skin at Enterprise level and make different skin rule for each user portal which has different custom styles to present the content.All user portal skin rules are inherited from Enterprise skin which is inherited from pyEndUser skin rule .
As of today, All custom styles of user portals are configured at one place and tagged to Enterprise skin. If enterprise skin is tagged to user portals then all styles are being loaded perfectly but when trying to make new skin (inherited from enterprise skin) for user portal then few of styles are not loading like tabs are not coming .
Am I missing any configurations with skin inheritance ?
***Edited by Moderator Marissa to update platform capability tags****
Basically, when we inherited any rule first priority gave to child level and move forward to parent level so can you please check Parent skin level(Enterprise level) formats or mixins overridden in child level skin.
I would double check that you are using the correct skin - if you point to the tab, the styling should come from a CSS file called pzskin_xxxx where xxx is your skin name. Other thing to try is put the same 2 skins into the same ruleset and version - check if it helps.
Sorry i didn't get your point on styling should come from CSS file . If a portal is configured with a skin rule which is configured to inherit styles from other skin rule then All UI components in user portal should able to access the styles in skin inheritance path.
All skin rules are lies in same ruleset but may not be in same version ,I don't think so that would be an issue ,however I'll give try to keep both of them in same version .
if you use developer tools and select the tab header element, find where the css settings are coming from - in the screenshot below, you can see that the font-size is 11px comes from pzskin_pzDesignerStudio skin