LPD-23982 #1091

…t to 'noindex' or 'nofollow' This is already enforced in the front end by disabling the fields (LPS-203513) but since they are disabled the values are not sent to the backend

…ed() method is for statically detecting if the filter is enabled. Once this returns false, it will always return false. This will not work with SAML, since SAML is not static and can be adjusted per instance.

they are already included in headless-staging

…et a better performance when it is not needed to check it

…eGroupId behavior

…e assetListEntryExternalReference code

… portlet preference when exporting, and ignore it when importing as assetListEntryExternalReferenceCode will be valid

…and use them, as this logic must be used for the other widgets

… import behavior

…port import behavior using the display style group ERC

…/main/java/com/liferay/layout/test/util/LayoutTestUtil.java

… opensearch as they were in elasticsearch. See LPD-26725 19d5511 https://liferay.atlassian.net/browse/LPD-34102

…ror page when a throwable is provided

Use the attribute key: RequestDispatcher.ERROR_EXCEPTION to provide the exception to the error page, which is the expected attribute to use for passing the exception, based on the Servlet specification. Note: we will retain the logic introduced by LPS-72744 (07375bf) to remove the relevant Servlet JSP error page attributes afterwards. This prevents double handling of the error from the application server.

Note: The additional testing with URL: http://localhost:8080/c and attribute keys: 'javax.servlet.error.exception' and 'javax.servlet.jsp.jspException', are included to make sure we keep track of the scenario, where double handling of the exception by the application server may occur. This scenario may be encountered if we decide to optimize or remove the extra logic introduced by LPS-72744 (07375bf).

Based on the Servlet specification (SRV.8.5), a servlet that is the target of a request dispatcher may throw a runtime exception, which should then be propagated to the calling servlet. Since this portion of code provides custom error handling for the calling servlet: Main Servlet, we will catch the RuntimeException and account for the exception when serving our fallback error page. Note: Without this commit, test case: testCustomErrorPageFallback would fail if the following portal property is set to true: direct.servlet.context.enabled (enabled by default).

…Just a skeleton.

…b_upgrade_client.sh from 6bc51d1

…index customizations in the dropdowns

… the ERC filled in the relationship field doesn't belongs to any object entry, a new object entry is created with this ERC

…eld value via PATCH request follow the ERC priority

…ass, then this ERC will be used to create the linked object entry when this exception is raised

…nly metadata values (draft object entry), the rows list is empty here

…ct definition

…de the upcoming value, when it is updated only through the relationship ID field, during partial update

…56 is indicated.

This would catch any deletion of the fragment or any mistake that makes the configuration invalid

This reverts commit f34e47f.

…inString instead

…bleFields

…plate" This reverts commit 1fab334.

…rvice.ranking.

…rvice.ranking

…der as before with auth.verifier.pipeline property. Mainly the important one is BasicAuthHeaderAuthVerifier because: * It has the force parameter, so it only makes sense to be the first if we have to enforce. * If other auth are not provided the next one in the list can be used, but BasicAuthHeaderAuthVerifier displays a pop up, so when forceBasicAuth is selected the others are not an alternative.

…to check which one is executed first.

… account in the pipeline.

… with an 'if' tag

…nd return at least a blank String. Replace with Validator check instead.

…figuration is saved. If we have just reset the configuration, the field will be hidden, not just empty. Adjust test to accommodate for this.

…shed version of ServiceBuilder instead of looking for latest

# breaking ## What modules/apps/commerce/headless/headless-commerce/headless-commerce-admin-order-api/src/main/java/com/liferay/headless/commerce/admin/order/resource/v1_0/OrderResource.java The patchOrder and patchOrderByExternalReferenceCode methods now return an Order. ## Why To generate the Test methods correctly ----

…ore generic. I'm establishing a new pattern here.

https://liferay.atlassian.net/browse/LPD-8360 # breaking ## What modules/apps/portal-search/portal-search-spi/src/main/java/com/liferay/portal/search/spi/index/configuration/contributor/helper/TypeMappingsHelper.java TypeMappingsHelper was renamed to MappingsHelper, and the method putTypeMappings() was renamed to putMappings() ## Why The word "type" is obsolete in regards to mappings. Although this interface is in the SPI module, it is a helper class which already has an internal implementation available. ---- # breaking ## What modules/apps/portal-search/portal-search-spi/src/main/java/com/liferay/portal/search/spi/index/configuration/contributor/helper/IndexSettingsHelper.java IndexSettingsHelper was renamed to SettingsHelper, and the methods public void loadFromSource(String source) and public String get(String key) were added ## Why The word "index" is redundant and unnecessary. The loadFromSource method allows a file to be read in order to contribute settings to the index. The get method allows the value of a setting to be retrieved. Although this interface is in the SPI module, it is a helper class which already has an internal implementation available. ---- # breaking ## What modules/apps/portal-search/portal-search-spi/src/main/java/com/liferay/portal/search/spi/index/configuration/contributor/IndexConfigurationContributor.java IndexConfigurationContributor was renamed to CompanyIndexConfigurationContributor, and a companyId parameter was added to the contributeMappings() and contributeSettings() methods ## Why This interface only contributes mappings and settings to the company indexes. Renaming the interface make this more clear. The new parameter helps contributors to decide what (or if) they contribute to an index for the given company ----

https://liferay.atlassian.net/browse/LPD-8360

…tingsHelper https://liferay.atlassian.net/browse/LPD-8360

…umber of shards to 1 https://liferay.atlassian.net/browse/LPD-8360

https://liferay.atlassian.net/browse/LPD-8360

…ated to index creation/contribution -Dynamic settings/mappings updates behind a Feature Flag -Applying SPI updates -Syncing with OpenSearch -General refactoring https://liferay.atlassian.net/browse/LPD-8360

…nd add tests https://liferay.atlassian.net/browse/LPD-8360

…er of shards to 1 https://liferay.atlassian.net/browse/LPD-8360

…d to index creation/contribution -Dynamic settings/mappings updates behind a Feature Flag -Applying SPI updates -Syncing with Elasticsearch -General refactoring https://liferay.atlassian.net/browse/LPD-8360

…add tests https://liferay.atlassian.net/browse/LPD-8360

…use it fails in both elastic and opensearch https://liferay.atlassian.net/browse/LPD-8360

…amp field does not exist https://liferay.atlassian.net/browse/LPD-8360

https://liferay.atlassian.net/browse/LPD-8360

…ch filter has the same synonyms, so only open and close the index once to apply all the changes https://liferay.atlassian.net/browse/LPD-8361

…anyIndexConfigurationContributor https://liferay.atlassian.net/browse/LPD-8361

…ing to match default https://liferay.atlassian.net/browse/LPD-8361

…st less flaky by waiting for the ConfigurationTemporarySwapper thread to complete all executions of *ConfigurationObserver#on*ConfigurationUpdate https://liferay.atlassian.net/browse/LPD-8361

https://liferay.atlassian.net/browse/LPD-8361

…eldCreationPortalInstanceLifecycleListener with TextEmbeddingCompanyIndexConfigurationContributor https://liferay.atlassian.net/browse/LPD-8362

https://liferay.atlassian.net/browse/LPD-8362

…ons and Relationhips of different companies.

…ition enabled/disabled, so there is a need to split the logic in two classes.

…ource.

…ng the schema used. This is useful to test the exported file partition against the database one, since the exported can be loaded in the database without removin the existing one.

…B Partition enabled.

…nted.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

LPD-23982 #1091

LPD-23982 #1091

Commits on Aug 20, 2024

Commits on Aug 21, 2024

LPD-23982 #1091

Are you sure you want to change the base?

LPD-23982 #1091

Commits on Aug 20, 2024

Commits on Aug 21, 2024