Search Results

All Results 7011
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
FreeHTML - shows text undefined when clicking on it's preview
Issue Steps to reproduce: Create a content page and drag the Free HTML component on it from the default fragments list. Edit some text Then click in the preview on the right. It will show text undefined. Again making...
How to Setup HTTPS on Tomcat for Liferay Portal 6.2 and DXP 7.0
Liferay Support does not recommend or endorse specific third-party products over others. Liferay is not responsible for any instructions herein or referenced regarding these products....
Adaptive Media does not show errors in logs
Issue Adaptive Media cannot process some images, but the only info about these errors is found in the UI alone, as shown in the image below. No related errors can be found in the logs. Environment Liferay...
Broken Document Links in Search Results
Issue Clicking on a link to a document in Search Results leads to a /null page and error: Environment Liferay DXP 7.0 Liferay DXP 7.1 Resolution This behavior is reported and fixed in LPS-93120. The fix has been released...
The LAR file could not be imported because it requires page templates or site templates
Issue "The LAR file could not be imported because it requires page templates or site templates" error message apprears when the user is importing pages from different Liferay systems.   Environment DXP 7.0 or higher...
Creating a new structure with a date field results in a Freemarker error
Issue When you create a new structure that includes a date field and try to save it, you receive an error similar to this: Error executing FreeMarker template FreeMarker template error: The following has evaluated to...
Repeatable web content structure items causes error and block publishing
Issue Steps to Reproduce: 1) Take Liferay 7.1 and install fix-pack dxp-14. 2) Connect with MySQL 5.7 3) Create a structure with two text fields       a) Add one text field 1 - make it repeatable       b) Add another...
unsupported symbol error after migration with geolocation as field name
Issue The word "geolocation" is not a reserved word in Liferay Portal 6.2 but in DXP it is. If a field name at Liferay Portal 6.2 is "geolocation", after the upgrade to DPX it could generated an Elasticsearch error...