Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
Level 1
Level 2
Melden Sie sich an, um alle Badges zu sehen
Diese Konversation wurde aufgrund von Inaktivität geschlossen. Bitte erstellen Sie einen neuen Post.
We utilized the Experience fragment as the primary navigation (header navigation), and it contains a number of flyouts.
We used sly data-sly-resource="$@path=xffragmentpath, selectors='content', wcmmode='disabled'">/sly> to render the flyout on the page.
As shown in publish mode, the page takes a long time to load.
And we determined that the problem is caused solely by data-sly-resource.
The page has a lot of child pages; yet, if we do the same thing on a page with no child pages, it works properly.
Please advise any solutions to help me increase the performance of my site.
Gelöst! Gehe zu Lösung.
Zugriffe
Antworten
Likes gesamt
That means that the problem is rather with the amount of data you are checking. The path resolution itself is unlikely to be a problem here, unless you do that a thousand times in a loop.
Only data-sly-resource is the issue; performance improved if I commented out this line <sly data-sly-resource="${@path=....}"/>.
Only the main home page, which contains several child sites, is affected by this problem.
That means that the problem is rather with the amount of data you are checking. The path resolution itself is unlikely to be a problem here, unless you do that a thousand times in a loop.
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten
Zugriffe
Likes
Antworten