Details

    • Fix Priority:
      4
    • Liferay Contributor's Agreement:
      Accept

      Description

      List View in Document Library (in SO 2.0 site) does not use the file_entry_action.jsp file from so-hook as expected. Stock JSP is always used.

      Cause of this is that when using following construct in JSP (the key is the method ResultRow.addJSP(), taken from /html/portlet/document_library/view_entries.jsp):

        List resultRows = searchContainer.getResultRows();
        ResultRow row = new ResultRow(curFolder, curFolder.getPrimaryKey(), i);
        ...
      
        row.addJSP("/html/portlet/document_library/file_entry_action.jsp");
      
        ...
        resultRows.add(row);
      

      the JSP file being actually used is always the stock JSP (or standard-hook-overridden one, whatever file is physically in the ROOT webapp under given path). But it will never be the one coming from Application Adapter applied to given group. In the case of SO 2.0, so-hook is used as an adapter for all SO sites. Hook so-hook contains override of /html/portlet/document_library/file_entry_action.jsp, but it's used only in Icon and Descriptiove view, as those are using another way to render the search container (<liferay-util:include />).

      All ResultRow.addJSP() methods should somehow support Application Adapters, the same way as <liferay-util:include /> does (I've looked into portal-service -> com.liferay.taglib.util.IncludeTag.getCustomPage()).

        Attachments

          Activity

            People

            • Votes:
              4 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Days since last comment:
                4 years, 14 weeks, 1 day ago