PUBLIC - Liferay Portal Community Edition

Portlets depoloyed to non-standard context fails to load resources when added to page via ajax

Details

  • Branch Version/s:
    6.1.x
  • Backported to Branch:
    Committed
  • Story Points:
    4
  • Similar Issues:
    Show 5 results 

Description

When a plugin portlet is deployed to a non-standard context (e.g. by setting recommended-deployment-context=) adding the portlet via the add menu (which uses an ajax render portlet request, will fail to properly load js/css resources.

Subsequent rendering of the portlet with a full page refresh does not result in the same issue.

  • What you need is a portlet with some resources defined in one or more of these liferay-portlet.xml settings (microblogs-portlet is ideal):

header-portal-css
header-portal-javascript
header-portlet-css
header-portlet-javascript
footer-portal-css
footer-portal-javascript
footer-portlet-css
footer-portlet-javascript

  • in that portlet edit the liferay-plugin-package.properties file
  • add recommended-deployment-context=<some different context name> property
  • deploy the plugin
  • then add the portlet to the page via the "Add menu"
  • it should result in 404 errors in the browser (you may have to use a network debuging tool to see the network errors)
  • the result of the error will be that the dependent js and or css in those resources is not loaded which may cause either js errors or UI to not render how it should

Issue Links

testing discovered

Bug - A problem which impairs or prevents the functions of the product. LPS-32210 Microblogs-portlet deployed to non-standard context will be temporarily unavailable.

  • Minor - Minor loss of function, or other problem where easy workaround is present.
  • Verified - Verified by QA (for IDE project)

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Tammy Fong added a comment -

Committed on:
Portal 6.2.x GIT ID: b7a45878b5b1164a771df0bd53cb1337a5b15afe.

Show
Tammy Fong added a comment - Committed on: Portal 6.2.x GIT ID: b7a45878b5b1164a771df0bd53cb1337a5b15afe.
Hide
Permalink
Serena Song added a comment - - edited

PASSED Manual Testing using the following steps:

  1. Navigate to Youtube-portlet\docroot\WEB-INF.
  2. Open liferay-plugin-package.properties file.
  3. Add 'recommended-deployment-context= {desired-context-name}

    ' this property to the file.

  4. Start Liferay instance and deploy the plugin.
  5. Add a page and add the portlet to the page via the "Add menu".
  6. Use debug tool firebug to see the network information.

Fixed on:
Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: e2bed399a4375b34494593a40f5737dbe26c9f51.
Plugin 6.1.x EE GIT ID: 230f250c414c47b28f52b6ad95ea5b8bd9235b2d.
Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 81a915de9df6778d3a0624def6906a7a3f2b1416.
Plugin 6.2.x EE GIT ID: a1c1e45aa19c63f31023deb7b6ccf4249b89bbc9.

There is no error about resources is not loaded causes either js errors or UI to not render in the browser and the resources is loaded successfully.

Show
Serena Song added a comment - - edited PASSED Manual Testing using the following steps: Navigate to Youtube-portlet\docroot\WEB-INF. Open liferay-plugin-package.properties file. Add 'recommended-deployment-context= {desired-context-name} ' this property to the file. Start Liferay instance and deploy the plugin. Add a page and add the portlet to the page via the "Add menu". Use debug tool firebug to see the network information. Fixed on: Tomcat 7.0 + MySQL 5. Portal 6.1.x EE GIT ID: e2bed399a4375b34494593a40f5737dbe26c9f51. Plugin 6.1.x EE GIT ID: 230f250c414c47b28f52b6ad95ea5b8bd9235b2d. Tomcat 7.0 + MySQL 5. Portal 6.2.x GIT ID: 81a915de9df6778d3a0624def6906a7a3f2b1416. Plugin 6.2.x EE GIT ID: a1c1e45aa19c63f31023deb7b6ccf4249b89bbc9. There is no error about resources is not loaded causes either js errors or UI to not render in the browser and the resources is loaded successfully.

People

Vote (0)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved:
    Days since last comment:
    8 weeks, 5 days ago