ICEfaces
  1. ICEfaces
  2. ICE-6837

Portlets: ACE components integration issues with Liferay

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0.0, 2.0.1, EE-2.0.0.GA
          • Fix Version/s: 2.0.2, EE-2.0.0.GA_P01
          • Component/s: ACE-Components
          • Labels:
            None
          • Environment:
            Liferay 5
          • Affects:
            Documentation (User Guide, Ref. Guide, etc.), Sample App./Tutorial, Compatibility/Configuration

            Description

            There are a number of issues with ACE components on Liferay 5, these range from simply not looking right, to having odd behaviours and not being able to have more than one component/portlet on a single page. This requires further testing and documenting each specific issue.

              Activity

              Ascending order - Click to sort in descending order
              Hide
              Permalink
              Arturo Zambrano added a comment -

              After testing the portlets individually and in various combinations, there don't seem to be any fundamental issues with the portlets integration anymore. Only three issues were found in the ace-showcase-portlet application. Two of them are app-code related and the other is not exclusive to portlets as it is also visible in the regular ace-showcase app. Those issues are the following:

              • A FileNotFound exception when trying to load the PushButton portlet, which prevents the portlet from loading.
              • An image not being displayed in the LinkButton portlet.
              • The rime theme not being applied to the TabSet component.

              The first two issues are app-code related. The first one is fixed by supplying the right .xhtml file in portlet.xml. The second one has to do with the path to the image in the graphicImage component in the LinkButton portlet. It is fixed by adding a slash ('/') at the beginning in the 'value' attribute in order to make it an absolute path and make the framework produce the right URL in the portlets format, rather than being a reative path that appears as a URL in the standard format. The last issue is also visible in the regular ace-showcase app. At some point something got broken in the rime theme for tabset. This is currently being investigated.

              Show
              Arturo Zambrano added a comment - After testing the portlets individually and in various combinations, there don't seem to be any fundamental issues with the portlets integration anymore. Only three issues were found in the ace-showcase-portlet application. Two of them are app-code related and the other is not exclusive to portlets as it is also visible in the regular ace-showcase app. Those issues are the following: A FileNotFound exception when trying to load the PushButton portlet, which prevents the portlet from loading. An image not being displayed in the LinkButton portlet. The rime theme not being applied to the TabSet component. The first two issues are app-code related. The first one is fixed by supplying the right .xhtml file in portlet.xml. The second one has to do with the path to the image in the graphicImage component in the LinkButton portlet. It is fixed by adding a slash ('/') at the beginning in the 'value' attribute in order to make it an absolute path and make the framework produce the right URL in the portlets format, rather than being a reative path that appears as a URL in the standard format. The last issue is also visible in the regular ace-showcase app. At some point something got broken in the rime theme for tabset. This is currently being investigated.
              Hide
              Permalink
              Arturo Zambrano added a comment -

              Fixed...

              There were some Javascript errors related to the use of ':'s in IDs in the animation code. This was fixed by using document.getElementById() first and passing the element to the Y.one() function.

              The appearance issues were fixed at the app-code level.

              Show
              Arturo Zambrano added a comment - Fixed... There were some Javascript errors related to the use of ':'s in IDs in the animation code. This was fixed by using document.getElementById() first and passing the element to the Y.one() function. The appearance issues were fixed at the app-code level.

                People

                • Assignee:
                  Arturo Zambrano
                  Reporter:
                  Arturo Zambrano
                • Votes:
                  0 Vote for this issue
                  Watchers:
                  0 Start watching this issue

                  Dates

                  • Created:
                    Updated:
                    Resolved: