||
Skip to end of metadata
Go to start of metadata

Follow the instructions below to change a certain section of a page in the Store or Publisher:

For more information on asset extensions, see Introduction to Asset Extensions.

  1. Create the shell of an asset extension. For more information, see Creating the Shell of an Asset Extension.
  2. Determine the partial to be overridden in the default implementation. The default partials directory for the Publisher and Store are as follows. For more information, see Locating an asset type specific partial.

    ES ComponentDirectory
    Publisher<ES_HOME>/repository/deployment/server/jaggeryapps/publisher/themes/default/partials
    Store<ES_HOME>/repository/deployment/server/jaggeryapps/store/themes/store/partials

    Example:

    • For example, select the asset utilization partial (assets-utilization.hbs) to override. The following screenshot displays the asset view of the Store. This file is found in the following directory: <ES_HOME>/repository/deployment/server/jaggeryapps/store/themes/store/partials/asset.hbs 
    • The assets-utilization partial that was selected above, renders the following section of the view, which is highlighted in red: 
  3. Make a copy of the default partial file, which you wish to customize (e.g., make a copy of the assets-utilization.hbs file). If nested partials are defined within the main partial, make a copy of the nested partials as well. For more information on Identifying a nested partial.

  4. Move the copied partial files into the respective asset extension themes directory. Thereafter, edit the partials based on your requirement and save the files. The asset extension directories for the Publisher and Store are as follows:

    ES ComponentDirectory
    Publisher<ES_HOME>/repository/deployment/server/jaggeryapps/publisher/extensions/assets/<ASSET_TYPE_NAME>/themes/<THEME_NAME>/partials
    Store<ES_HOME>/repository/deployment/server/jaggeryapps/store/extensions/assets/<ASSET_TYPE_NAME>/themes/<THEME_NAME>/partials

    Currently, ES only maintains one theme for the Publisher and Store in the following directories:

    Default Theme
    Name
    Default Theme Directory
    default<ES_HOME>/repository/deployment/server/jaggeryapps/publisher/themes/default
    store<ES_HOME>/repository/deployment/server/jaggeryapps/store/themes/store 

    If you add a new customized theme in the respective themes directory, then the <THEME_NAME>in the latter mentioned asset extensions directory needs to reflect the respective theme, which is used when overriding a page.

    Example:
    Move the copy of the assets-utilization.hbs file into the <ES_HOME>/repository/deployment/server/jaggeryapps/store/extensions/assets/<ASSET_TYPE_NAME>/themes/store/partials directory as shown in the screenshot below and, edit the files.

  5. Refresh the page. Thereafter, check if the overridden partial was loaded after the page was refreshed. 

Try out the following sample to get an understanding on how you can partially override a view of an asset type:

Customizing the subscription process for a specific asset type

  • No labels