Kuali Rice Development
  1. Kuali Rice Development
  2. KULRICE-3985

portalTop tag only works with a single portal CSS/JS file

    Details

    • Type: Bug Fix Bug Fix
    • Status: Open Open
    • Priority: Major Major
    • Resolution: Unresolved
    • Affects Version/s: 1.0.1
    • Fix Version/s: Backlog
    • Component/s: User Interface
    • Labels:
    • Similar issues:
      KULRICE-5143Figure out what other applications are doing about requiring css and js to exist in external portal windows
      KULRICE-3125Fix paths of Rice portal pieces so that they don't conflict with KFS portal locations
      KULRICE-3120Remove references to KFS classes from the Rice portal
      KULRICE-3298The Rice jsp/tag files for KIM throw errors when a KIM Type is using the KimNonDataDictionaryAttributeDefinition class
      KULRICE-7250Reference to KimAttributeImpl should be removed from tag files
      KULRICE-3550Rice portal improvements
      KULRICE-4972DataDictionary uses a single spring context for all DD files which can result in unknown bean id conflicts
      KULRICE-11426Ability to view KNS pages within the KRAD portal
      KULRICE-384Rice Tag Cleanup
    • Rice Module:
      Rice Core
    • Application Requirement:
      KC

      Description

      In portalTop.tag, there is a section

      <link href="$

      {ConfigProperties.application.url}/${ConfigProperties.portal.css.files}" rel="stylesheet" type="text/css" />
      <script language="JavaScript" type="text/javascript" src="${ConfigProperties.application.url}

      /$

      {ConfigProperties.portal.javascript.files}

      "></script>

      This assumes that portal.css.files and portal.javascript.files each reference only one file. From the name of the properties (files,) they should support multiple files. This functionality was previously supported in KRA and apparently did not get merged back into Rice.

        Activity

        Hide
        Ken Geis added a comment -

        In addition, if these configuration properties are not defined, browsers will get a 404 upon trying to get those resources. 404s are not cacheable, and the browser will unsuccessfully attempt to download that resource with every page load.

        Show
        Ken Geis added a comment - In addition, if these configuration properties are not defined, browsers will get a 404 upon trying to get those resources. 404s are not cacheable, and the browser will unsuccessfully attempt to download that resource with every page load.

          People

          • Assignee:
            Unassigned
            Reporter:
            Ken Geis
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:

              Structure Helper Panel