Loading

Page Designer pages in the B2C Commerce platform breaks when trying to use Page-Includes that contain long URLs

Publiseringsdato: Nov 6, 2024
Beskrivelse

Customers using the Commerce Cloud B2C platform may occasionally experience issues when attempting to access the Page Designer page. This problem can arise if the __SYSTEM__Page-Include component is configured with a URL that contains an excessive number of parameters in the wainclude URL. When these URLs become overly complex or lengthy due to the number of parameters included, it can prevent the Page Designer from loading correctly. This is likely because the extended URL structure may exceed the platform's limits on URL length or parameter count, causing load errors or timeouts.

When rendering a PD page, it always involves a remote include, meaning the information necessary for the page is appended to the remote include URL. Once that URL exceeds a certain length, JWA (Java Web Application) will refuse to execute the request and will instead print the URL to the response

Løsning

The root cause is likely that the search is being executed in the outer controller, with all the search results being passed directly to the page. This approach significantly increases the amount of data included in the URL, eventually hitting the limit.

To resolve this, it would be better to pass only the search parameters to the page and then perform the actual search within the page type implementation. This approach minimizes the amount of information transferred through the URL, preventing the overflow.

If for some reason it’s essential to perform the search outside the page (perhaps due to architectural constraints), consider limiting the number of search results passed to the page. For instance, if the page only renders the first 20 products, there’s no need to send the entire result set. Instead, just pass the first 20 products to the page. This not only reduces the volume of information being transmitted but also ensures that the remote include URL stays within its permissible length.

By streamlining the amount of data passed, the length of the remote include URL is reduced, thus avoiding this execution issue.

Knowledge-artikkelnummer

003434657

 
Laster
Salesforce Help | Article