Skip to main content

Custom Content in Paper Lantern - Specific Pages Only

Comments

4 comments

  • cPanelAdamF
    Let's check a couple of things first before we draw conclusions like those. Could you verify the filename and location of the UI Includes you're expecting to see show up in your interface? For example, the full path should be either
    /var/cpanel/customizations/includes/addon_domains_page_header.html.tt
    for a global include or
    /home/$reseller/var/cpanel/reseller/includes/addon_domains_page_header.html.tt
    for an include that should only be applied to $reseller's users. It may be helpful to make the content of these includes colorful so that it stands out against the interface while you're working on it. Here's how the example UI Includes look that our QA people came up with when testing this feature out: .vB The next thing to verify would be the chain of account ownership. Right now, cPanel will always show the end-user the customizations (styles, brand, includes, etc) that their account owner specifies. This can trip you up when you log in to cpanel as a reseller and expect to see your own customizations. We had to make a hard design decision with this one and we're not against changing the implementation in the future if it causes un-due confusion. So the thing to verify with this concern is that the account you're logging into cpanel with is indeed owned by either itself or by the correct reseller. Let me know the answers to those questions so that we can figure out why you're seeing the misbehavior. After we get you straightened out, I'll queue up additional work on the areas of the documentation so that other users can avoid the same conundrum.
    0
  • JamesOakley
    Thanks Adam I wrote a great long reply to you, splitting your post into multiple parts to answer each question. Then I spotted what had happened, so I don't need my long reply. [QUOTE=http://blog.cpanel.net/customizing-paper-lantern/]To target footers on the pages inside Addon Domains only, create an addon_domains_footer.html.tt file
    Compare to
    ]For example, the full path should be either /var/cpanel/customizations/includes/addon_domains_page_header.html.tt for a global include

    Sure enough, with "page_" in the filename, it works. So the documentation work needed is: (i) correct that blog post (ii) add a section to
    0
  • cPanelAdamF
    Glad to hear you found the problem.
    ](i) correct that blog post

    The blogpost has been corrected, sorry for the confusion there.
    ](ii) add a section to
    0
  • cPanelAdamF
    For those looking for the list of filenames for the page-specific UI Includes, it can currently be found on
    0

Please sign in to leave a comment.