1. Liferay Help Center
  2. Knowledge Base
  3. Reference

Known Issues: Liferay DXP 7.0 Fix Packs and Service Packs

Avatar

Liferay Support

  • Updated
Note: This article is no longer maintained and is only made available for your reference. All the information in this article can now be found in the Liferay DXP Release Notes.

This article documents a list of known issues that exist in Liferay DXP 7.0 Fix Packs and Service Packs.

Resolution

Liferay DXP 7.0 Fix Packs and Service Packs contain the following known issues, which will either be resolved through workarounds or in future fix packs. See our downloads page for the latest Liferay DXP 7.0 Fix Packs and Service Packs.

Fix Pack 80

  • The content of a User's Web Content will be lost after reverting to a previous 7.0 Fix Pack from Liferay DXP 7.0 Fix Pack 80. The bundle will still start up and work as expected, but the Web Content data will be lost. The following error will be thrown: 
    2019-04-22 06:21:48.842 ERROR [http-nio-8080-exec-7][IncludeTag:128] Current URL /group/guest/~/control_panel/manage?p_p_id=com_liferay_journal_web_portlet_JournalPortlet&p_p_lifecycle=0&p_p_state=maximized&p_p_mode=view&_com_liferay_journal_web_portlet_JournalPortlet_mvcPath=%2Fedit_article.jsp&_com_liferay_journal_web_portlet_JournalPortlet_redirect=http%3A%2F%2Flocalhost%3A8080%2Fgroup%2Fguest%2F~%2Fcontrol_panel%2Fmanage%3Fp_p_id%3Dcom_liferay_journal_web_portlet_JournalPortlet%26p_p_lifecycle%3D0%26p_p_state%3Dmaximized%26p_p_mode%3Dview%26p_p_auth%3DdZB5qz3F&_com_liferay_journal_web_portlet_JournalPortlet_referringPortletResource=&_com_liferay_journal_web_portlet_JournalPortlet_groupId=20142&_com_liferay_journal_web_portlet_JournalPortlet_folderId=0&_com_liferay_journal_web_portlet_JournalPortlet_articleId=31906&_com_liferay_journal_web_portlet_JournalPortlet_version=1.0&p_p_auth=dZB5qz3F generates exception: java.lang.NoSuchMethodError: com.liferay.dynamic.data.mapping.taglib.servlet.taglib.HTMLTag.setDocumentLibrarySelectorURL(Ljava/lang/String;)V
java.lang.NoSuchMethodError: com.liferay.dynamic.data.mapping.taglib.servlet.taglib.HTMLTag.setDocumentLibrarySelectorURL(Ljava/lang/String;)V
	at org.apache.jsp.article.content_jsp._jspService(content_jsp:974)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:111)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
	at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:411)
	at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:473)
	at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:377)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
	at com.liferay.portal.osgi.web.servlet.jsp.compiler.JspServlet.service(JspServlet.java:417)
	at com.liferay.portal.osgi.web.servlet.jsp.compiler.JspServlet.service(JspServlet.java:428)
	at org.eclipse.equinox.http.servlet.internal.registration.EndpointRegistration.service(EndpointRegistration.java:153)
	at org.eclipse.equinox.http.servlet.internal.servlet.ResponseStateHandler.processRequest(ResponseStateHandler.java:62)
	at org.eclipse.equinox.http.servlet.internal.context.DispatchTargets.doDispatch(DispatchTargets.java:118)
	at org.eclipse.equinox.http.servlet.internal.servlet.RequestDispatcherAdaptor.include(RequestDispatcherAdaptor.java:48)
	at com.liferay.portal.kernel.servlet.taglib.ui.BaseJSPFormNavigatorEntry.include(BaseJSPFormNavigatorEntry.java:51)
	at org.apache.jsp.html.taglib.ui.form_005fnavigator.lexicon.page_jsp$5.renderHTML(page_jsp.java:2863)
	at com.liferay.taglib.util.PortalIncludeUtil.include(PortalIncludeUtil.java:43)
	at org.apache.jsp.html.taglib.ui.form_005fnavigator.lexicon.page_jsp._jspService(page_jsp.java:2858)
	at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
	at com.liferay.portal.servlet.DirectRequestDispatcher.include(DirectRequestDispatcher.java:64)

Fix Pack 75

  • LPS-91484: ClassNotFoundException error thrown when adding a web content on a reverted bundle
  • LPS-91475: Success message is not displayed when saving a web content draft in Web Content Display portlet.
  • LPS-91474: Portlet options does not appear after clicking the dropdown toggle a second time on IE11.

Fix Pack 72

  • LPS-89414: Users using IE11 will not be able to add images in AlloyEditor using the toolbar.

Fix Pack 62

  • LPS-87151: Web Content Display and articles are gone after a User upgrades from 6.1 or 6.2 to 7.0 DXP with Fix Pack 62 installed. This issue only occurs while performing an upgrade on Sybase 16.
  • LPS-87153: Document metadata are gone after a User upgrades from 6.1 or 6.2 to 7.0 DXP with Fix Pack 62 installed. This issue only occurs while performing an upgrade on Sybase 16.

Fix Pack 60

  • LPS-87429: A new upgrade was introduced for Blogs. Various components of Blogs such as, Notifications and Subscriptions will fail when trying to upgrade from 7.0.x to 7.1.x. - Resolved in Fix Pack 64
  • LPS-86091 Cannot publish a basic document to Sharepoint. The following NPE errors appear in the User console: 
    ERROR [http-nio-8080-exec-8][PortletServlet:112] javax.portlet.PortletException: java.lang.NullPointerException
javax.portlet.PortletException: java.lang.NullPointerEx

- Resolved in Fix Pack 70

Fix Pack 59

  • LPS-85875 Users cannot delete virtual instances that contains a Dynamic Data Lists record. - Resolved in Fix Pack 64
    • Workaround:
      • Navigate to virtual instance site
      • Delete existing Dynamic Data Lists
      • Navigate back to Site
      • Delete virtual instance that contained the DDL record

Fix Pack 56

  • LPS-84428: JSF portlets deployed to WildFly (JBoss, WebSphere, and tcServer may also be affected) are unable to submit forms after WildFly is restarted. After a restart, the application server's Bean Validation implementation is incorrectly provided to JSF portlets. This causes inappropriate validation failures. In order to work around this issue, add the following <context-param> to the JSF application's web.xml: 
    <context-param>
    <param-name>javax.faces.validator.DISABLE_DEFAULT_BEAN_VALIDATOR</param-name>
    <param-value>true</param-value>
</context-param>

Resolved in Fix Pack 58

Fix Pack 42

  • LPS-79013: The Applications panel is missing styling which causes duplicate dropdown arrows to show up when the panel is expanded. - Resolved in Fix Pack 44

Fix Pack 41

  • When the Central Authentication Service (CAS) is enabled, the login page does not load when logging in as a Guest.
  • LPS-78952: A User’s Twitter feed will not appear in the Activities portlet in the set interval time. This will require Users to wait a few minutes longer than their set interval time for their Twitter feed to appear. - Resolved in Fix Pack 51
  • Due to an error generating the release notes, the documentation.xml file in Fix Packs 41 and 42 contains an invalid list of fixed issues. As a result, a warning will appear when using a hotfix built of Fix Pack 41 or 42 and running the command patching-tool info. Please see Errors When Applying Support Driven Hotfixes Based on FP-41 or FP-42 for more information. - Resolved in Fix Pack 43

Fix Pack 37

  • LPS-75969 removes the exported package from rss-web. This causes an error Duplicate Entry 'com.liferay.rss.web.internal.util.RSSFeed' for Key 'IX_B27A301F in the console when starting the application server. For more information, see Applying Fix Pack 37 Causes Duplicate Entry of... - Resolved in Fix Pack 42
  • LPS-77766 restores the "request" object in context as a Map representation of the request. This allows  web content templates be able to use the request function. - Resolved in Fix Pack 40.
  • LPS-77767 changes the default behavior of JavaScript global functions. This can cause third party libraries that use global functions like require() or define() to stop working. - Resolved in Fix Pack 40
    • Workaround:
      • Navigate to Control Panel > System Settings > Foundation > Javascript Loader
      • Check the option "Expose Global"

Fix Pack 33

  • LPS-75869 removes a dependency of the Events List app that prevents portal from starting up when the Events List app is deployed with FP33 installed. - Resolved in Liferay Events List 1.0.1+
  • LPS-76221: Automatic translations were removed. - Resolved in Fix Pack 35

Fix Pack 32

  • LPS-76712: An exception is thrown when using JDBC_PING, causing clustering not to work. - Resolved in Fix Pack 35

Service Pack 5

Resolved in Service Pack 6

Due to packaging issues, the Liferay DXP 7.0 SP5 downloads were removed from Customer Portal. We are working on addressing these issues in the upcoming SP6 release. Fix packs are not affected by these issues, so existing users can also keep their systems updated by installing the latest fix pack, Marketplace apps, and Patching Tool.

Users who have downloaded SP5 can follow the workarounds listed below to resolve the known issues. Please note that these issues will not occur when deployed on custom setups. Instead, users will only encounter these problems when using the Tomcat and Wildfly bundles, as well as the Admin Tools file.

  • When upgrading to Liferay DXP 7.0 SP5, an exception is thrown: 
    • Exception in thread "main" java.lang.ClassNotFoundException: com.liferay.portal.tools.DBUpgrader
       at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
       at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
       at com.liferay.portal.tools.db.upgrade.client.DBUpgraderLauncher.main(DBUpgraderLauncher.java:43)
    • Resolution: The file structure in the DB Upgrade Tool changed and the properties files are missing.
    • Workaround:
      • Move the DB Upgrade jar back down one level:
        • From: /appserver_location/tools/portal-tools-db-upgrade-client/lib/com.liferay.portal.tools.db.upgrade.client.jar
        • To: /appserver_location/tools/portal-tools-db-upgrade-client/com.liferay.portal.tools.db.upgrade.client.jar
      • Delete the bin folder and contents.
      • Run the upgrade tool: java -jar com.liferay.portal.tools.db.upgrade.client.jar
      • Property files should be generated 
  • When applying a fix pack to Liferay DXP 7.0 SP5, an exception is thrown: 
    • Error: File not found: liferay-dxp-digital-enterprise-7.0-sp5/osgi/target-platform/integrity.properties
Patching tool stopped because of an exception, please see the logs for details.
    • Resolution: The target-platform folder is missing.
    • Workaround:
      • Download the attached target-platform.zip
      • Extract the file in the liferay-dxp-digital-enterprise-7.0-sp5/osgi folder
      • Re-run patch installation steps

Fix Pack 26

  • In the portal-ext.properties, the ehcache.cluster.link.replicator.properties were renamed to ehcache.replicator.properties, which can cause issues in clustered environments.
    • Resolution: Replace the following lines in the portal-ext.properties 
      • ehcache.cluster.link.replicator.properties.advisorcompassContentCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true
ehcache.cluster.link.replicator.properties.advisorcompassChannelCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true
ehcache.cluster.link.replicator.properties.advisorcompassFullViewCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true
ehcache.cluster.link.replicator.properties.advisorcompassRelatorsCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true
ehcache.cluster.link.replicator.properties.advisorcompassBreadCrumbCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true
ehcache.cluster.link.replicator.properties.insideCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true
      • with
      • ehcache.replicator.properties.advisorcompassContentCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true
ehcache.replicator.properties.advisorcompassChannelCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true
ehcache.replicator.properties.advisorcompassFullViewCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true
ehcache.replicator.properties.advisorcompassRelatorsCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true
ehcache.replicator.properties.advisorcompassBreadCrumbCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true
ehcache.replicator.properties.insideCache=replicatePuts=true,replicatePutsViaCopy=true,replicateUpdatesViaCopy=true,replicateRemovals=true

Fix Pack 25

  • Action Exception error appears during startup. Portal will still start up successfully. 
    • 17:01:19,059 ERROR [http-nio-8080-exec-10][MainServlet:1232] com.liferay.portal.kernel.events.ActionException: java.lang.IllegalStateException: Cannot create a session after the response has been committed
com.liferay.portal.kernel.events.ActionException: java.lang.IllegalStateException: Cannot create a session after the response has been committed
    • Workaround: Restart the Portal.
  • LPS-73789: Application panel does not always load on IE11 and Edge - Resolved in Fix Pack 33

Fix Pack 24

  • LPS-73634: Site name is added after publishing calendar resource from staging - Resolved in Fix Pack 26

Fix Pack 23

  • LPS-73548: Missing the Blogs Template in ADT - Resolved in Fix Pack 24
  • LPS-73390:  Image alignment in Blog Entry can't be saved
  • LPS-73412:  Unable to change the scope under Content - Resolved in Fix Pack 26

Fix Pack 22

  • Web application bundles (WABs) that require a JNDI data source will not work due to a missing comma in a portal property - Resolved in Fix Pack 24

Fix Pack 19

  • LPS-72862: Unexpected error occurs after clicking account settings - Resolved by LPS-74109 in Fix Pack 28
  • LPS-71783: Join Xor is not working in workflow - Resolved in Fix Pack 26

Fix Pack 16, 17, 18

  • Due to a packaging issue, the source cannot be applied. - Resolved in Fix Pack 19

Fix Pack 13

  • LPS-71944: Application display templates and themes broken by changes to method contracts for TemplatePortletPreferences - Resolved in Fix Pack 14

Service Pack 2

  • LPS-69528: Saving form does not redirect user or give confirmation - Resolved in Fix Pack 14
    • Workarounds:
      • After clicking on save, navigate back to Forms menu
      • Disable SPA by setting the javascript.single.page.application.enabled to false in the portal-ext.properties. Please see Automatic Single Page Applications in our Official Documentation for more information on this feature.

Fix Pack 12

  • When using a SQL Server driver downloaded from Sourceforge, the connection fails and an error is thrown.
    • Resolution: Use the driver automatically loaded by Liferay through jdbc.default.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver, instead of the Sourceforge driver (jdbc.default.driverClassName=net.sourceforge.jtds.jdbc.Driver).
  • Liferay DXP connected to PostgreSQL 9.4 may fail to start up with the following errors in the console: 
    • 09:54:46,272 INFO [localhost-startStop-1][HikariDataSource:95] HikariPool-1 - Starting...
09:54:46,356 INFO [localhost-startStop-1][PoolBase:491] HikariPool-1 - Driver does not support get/set network timeout for connections. (org.postgresql.jdbc3.Jdbc3Connection.getNetworkTimeout()I)
09:54:46,356 ERROR [localhost-startStop-1][PoolBase:429] HikariPool-1 - Failed to execute isValid() for connection, configure connection test query (org.postgresql.jdbc3.Jdbc3Connection.isValid(I)Z).
    • Resolution: This error occurs because of an older jar. To resolve this issue, please update the JDBC jar, which can be found here: PostgreSQL JDBC Driver.

Fix Pack 10

Fix Pack 8

  • LPS-69919: Portlet Always Writes to the Local Database, even if it is Configured to Write to an External Database - Resolved in Fix Pack 10
  • LPS-78546: When using Sybase 16 and upgrading from Liferay Portal 6.1 or 6.2 to DXP 7.0, the database tables may not be updated. Please open a Help Center ticket for further diagnosis and resolution.
Was this article helpful?
0 out of 0 found this helpful