Uploaded image for project: 'OpenAM'
  1. OpenAM
  2. OPENAM-13457

AM 6 XUI favicon icon not being recognised

    XMLWordPrintable

    Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Fixed
    • 6.0.0, 6.0.0.3
    • 6.0.0.5, 6.5.0, 6.0.1
    • XUI
    • 2018.10 "Squid" Turing

      Description

      Bug description

      The favicon icon uses the path variable and icon variable in the ThemeConfigrator.js. This path variable now prepends the themes folder to load partials and templates etc but not for loading the favicon.

      How to reproduce the issue

      1. checked out am-external and the releases/6.0.0.3 branch
      2.  copy the favicon.ico from src/main/resources/favicon.ico to src/main/resources/themes/dark/favicon.ico
      3. edited the main/js/config/ThemeConfiguration.js so the dark theme has the path variable e.g. path: "dark/" and the icon variable e.g. icon: "favicon.ico". Then add the mapping for the theme to the route realm
      4.  run a mvn clean install on the openam-ui-ria project
      5.  copy the contents of the outputted build folder into my running AM/XUI folder
      6. attempted to access the the mapped realm to the dark theme it fails to load any favicon
      Expected behaviour
      Expect the favicon to be loaded from the themes/dark/favicon.ico path
      Current behaviour
      It attempts to load the favicon from a non existent XUI/dark folder 
      

      Work around

       

      Put the favicon in the XUI folder with a new name e.g. XUI/dark-favicion.ico and edit the ThemeConfuration.js to have icon: "../dark-favicon.ico",

       

        Attachments

          Issue Links

            Activity

              People

              phil.ostler Phil Ostler [X] (Inactive)
              eliot.kerslake Eliot Kerslake [X] (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: