Biblioteca técnica
Video Tutorials
- How to Setup a Data Source in Liferay Analytics Cloud (Video)
- How to Create and Populate Organizations in Liferay DXP (Video)
- How to Add Tags and Categories in Liferay DXP (Video)
- How to Connect Liferay to LDAP (Video)
- How to Setup Notifications in Liferay DXP (Video)
- Editing Page Fragments in Liferay DXP (Video)
Support Policy
- Liferay DXP Compatibility with Elasticsearch Service on Elastic Cloud
- JDK Certification, Java TCK Compliance, and Liferay
- Xuggler Support Policy
- Digital Experience Platform 7.3 Deprecated and Archived Items
- Third-Party Paid Apps Activation Support Policy
- Microsoft Edge Compatibility
How-to
- How to Setup HTTPS on Tomcat for Liferay Portal 6.2 and DXP 7.0
- How to prevent user enumeration attacks through the Forgot Password functionality
- Installing Liferay Developer Studio 3.9.x
- How to implement custom resolvers for Liferay Connector to SAML 2.0
- Configuring Liferay's LDAP Settings to Import Users in DXP 7.3
- How-To Generate a HAR file for Liferay Support
Reference
- Auto Upgrade in DXP 7.3 and Above
- Impact of Google Chrome 80 and changes in the default behavior of the SameSite cookie setting on SAML
- DXP 7.3 Patching Source Code [Functionality Change]
- Understanding Liferay DXP's compatibility with Elasticsearch
- How HTTP cookies are being used in Liferay DXP 7.0+
- Liferay DXP Elasticsearch Connectors: Technical Data Sheet
Troubleshooting
- Unexpected new indexes appear in Elasticsearch after installing DXP 7.2 FP8+/SP3+
- DXP 7.2 Service Pack 1 (SP1)/Fix Pack 2 (FP2) requires Elastisearch 6.2 or higher due to InvalidTypeNameException error on startup
- DXP 7.2 Service Pack 1 (SP1)/Fix Pack 2 (FP2) requires install of Solr 7 connector version 2.0.1 or higher
- Search Tuning modules must be deactivated when DXP 7.2 Service Pack 1 (SP1)/Fix Pack 2 (FP2) is configured with Solr 7
- DXP 7.0 Fix Pack 70: Compatibility changes and deployment notes for Connector to Elasticsearch 6 and Solr 5 Search Engine
- Patching Tool 3 "info" Command showing multiple patches as "Will be Installed"
Solution
- Client-side HTTP parameter pollution vulnerabilities
- Is there any configuration that can be done in Liferay to encode all the URLs ?
- The source code format is misaligned in the AlloyEditor
- Liferay application servers getting unresponsive while switching the database
- HTTP Strict Transport Security (HSTS) Header Not Used
- Facing issues with the workflow powered application