Search Results

All Results 7011
ソート
Resource Type
Applicable Versions
Deployment Approach
Capability
Feature
Editable field isn't working within loops in page fragments
legacy Troubleshooting
Issue Steps to reproduce: Under Site Builder > Page Fragments, Import fragment entries.zip(Attached) Drag the fragment on the content page, In the configuration defaultValue for iteration is 3. It works fine and fields...
How to call custom CSS?
legacy How To
Issue How to call custom CSS in portal normal.ftl file Environment Liferay DXP 7.2 Resolution The custom styling can be added by using theme’s _custom.scss file (i.e., src/css/_custom.scss). Liferay DXP supports...
Liferay SaaS CDNs Cache Mode
legacy
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM). Issue What is the cache mode set for Liferay SaaS CDNs?...
Blacklisting Commerce components in 7.3 can stop other modules as well
legacy Troubleshooting
Issue When you add a Commerce component to the blacklist, other modules will stop functioning as well. This may cause the following issues:  - Certain Commerce menu elements could be missing  - Gogo Shell...
Large File Uploader Permissions
legacy
In compliance with the latest GDPR regulations, files uploaded via our large file uploader are encrypted. As an additional security measure, we require all large file attachments to be...
Unable to see Structures Field for the Templates
legacy Troubleshooting
Issue Steps to reproduce: Start a Liferay bundle. Create a structure with some fields in it Create a template for it Click on the Structure tab, then back to the Template tab Open the template Expected behavior: The...
Added buttons to AlloyEditor toolbar don't work in Blogs
legacy Troubleshooting
Issue I added buttons such as strike-through, superscript, and subscript to the AlloyEditor toolbar, but these buttons don't work when attempting to edit content in the Blogs module. Environment Liferay DXP 7.2...
User gets a site despite disabling it in portal-ext
legacy
Issue We have set the following settings in portal-ext.properties, but when a user is created, an entry is also created in the group_ table that has the username as the friendly-url....