Forum Discussion

AbhishekIlindra's avatar
8 years ago

Lithium SDK Clarifications

Hi All,

 

Can anyone explain how Lithium SDK is going to work. Following topics need clarification on it.

 

1. We create new components and pushed to Stage Environment. What are the steps need to perform while pushing code to Production.

2. We have both SDK push Components and New components created in the Stage Environment(with out SDK)  is it going to effect while pushing code via Studio push.

  • Hi AbhishekIlindra,

    Here is a screenshot to help illustrate. Notice the message at the top. (I highlighted it with the red outline.) That message will help notify you if a component exists in multiple plugins.

     


    As for the two categories (Custom and SDK) in the Components section of the tab...

     

    If you see a component with an SDK icon in the "Custom section, it means that you have two versions of the component -- one in Studio and one in the Community Plugin SDK. If there are any differences in the contents of the component code, then the Studio version is used. If you want to use the SDK version, click the X next to the component (in the Custom section). After you click that X button, the component will appear in the SDK section of the tab. The version in the Studio plugin will be deleted. 

     

     

    If a component only appears in the SDK section, it only exists in the SDK plugin. 

    If a component only appears in the Custom section and does not have an SDK icon next to it, then the component only exists in the Studio plugin.

     

    I suspect what happened is that a set of custom components were originally created in Studio, and then were exported into the SDK using the li export-studio-plugin command. Then, when new components were created and submitted via the SDK with li submit-plugin , the originally-exported components (created in Studio) were submitted back to Stage, resulting in duplicate copies.

     

    If you want all component development to go through the SDK, I would recommend clicking the X button next to duplicate copies in the Custom section so that all components appear under the SDK section. That might help remove confusion when Studio users are looking at the Components tab. 

20 Replies

  • cike We are seeing same components in both Custom as well as in SDK and it is just adding .widget to the end of the component name in the SDK tab. Did we are in any wrong approach.

     

    What will happen if we move this all to the Production via studio Publish option

  • cike's avatar
    cike
    Champion
    8 years ago

    Did you add the .widget suffix by yourself? If so, you just created a new component.

     

    A push to production will only use those components which have been added to your pages. All other components wont effect your production instance in any way.

  • cike: As per knowledge we didn't add .widget  suffix in the community. If it is a setting can you guide me how to eliminate it.

  • cike's avatar
    cike
    Champion
    8 years ago

    Well, I also see the SDK and the custom path in our stage environment. But in our case the custom path is empty (We actually have all our customizations in the SDK).

    I think you see your components twice, because you have them in your SDK and modified them through studio directly. This behavior I described in one of my former posts. As described in the SDK documentation, all modifications through studio will prevail your customizations made via the SDK.

     

    You may take a look at this site. There you'll find information how to handle your customizations and reset your studio adjustments.

  • SuzieH's avatar
    SuzieH
    Khoros Alumni (Retired)
    8 years ago

    Hi AbhishekIlindra,

    Here is a screenshot to help illustrate. Notice the message at the top. (I highlighted it with the red outline.) That message will help notify you if a component exists in multiple plugins.

     


    As for the two categories (Custom and SDK) in the Components section of the tab...

     

    If you see a component with an SDK icon in the "Custom section, it means that you have two versions of the component -- one in Studio and one in the Community Plugin SDK. If there are any differences in the contents of the component code, then the Studio version is used. If you want to use the SDK version, click the X next to the component (in the Custom section). After you click that X button, the component will appear in the SDK section of the tab. The version in the Studio plugin will be deleted. 

     

     

    If a component only appears in the SDK section, it only exists in the SDK plugin. 

    If a component only appears in the Custom section and does not have an SDK icon next to it, then the component only exists in the Studio plugin.

     

    I suspect what happened is that a set of custom components were originally created in Studio, and then were exported into the SDK using the li export-studio-plugin command. Then, when new components were created and submitted via the SDK with li submit-plugin , the originally-exported components (created in Studio) were submitted back to Stage, resulting in duplicate copies.

     

    If you want all component development to go through the SDK, I would recommend clicking the X button next to duplicate copies in the Custom section so that all components appear under the SDK section. That might help remove confusion when Studio users are looking at the Components tab. 

  • SuzieH : If we go with Same approach(Component present in both SDK and Custom tab) and published to Production using Studio Publish also there won't be any effect only the component placed in the page quilt will be appear in the Community Pages. Let correct me if i'm in wrong direction 

  • SuzieH's avatar
    SuzieH
    Khoros Alumni (Retired)
    8 years ago

    Hi AbhishekIlindra

    The component will render in your quilt, even if it exists both plugins. The only potential effect of having the component exists in both plugins is that if the component code differs between locations, you might not have the correct version of the component display. 

  • AbhishekIlindra's avatar
    AbhishekIlindra
    Boss
    8 years ago

    SuzieH cike : We uploaded font files in the Assets library and can able able to use them and it is showing Delete option nee to the font and for remaining it is showing as Revert to SDK. Is it wrong approach if not we can able to push this Changes via Studio push.

     

    Attaching the screenshot for your reference.

     

     


    Assests.PNG
  • SuzieH's avatar
    SuzieH
    Khoros Alumni (Retired)
    8 years ago

    Hi AbhishekIlindra

    The assets that say Delete next to them only exist in the Studio plugin. They will be pushed to production with Studio Publish. The assets that say Revert to the SDK Version exist in both plugins (Studio and the SDK). If you push to production, the version in Studio is the version that will be pushed with Studio Publish.