You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running Umbraco 7.13.1 with Articulate 3.0.2 - the site's /blog rendering of the List.cshtml and Pager.cshtml partials works as expected (pager values and links work), however then rendering a child category, e.g., /blog/news the same List.cshtml and Pager.cshtml renders but the BlogRootUrl value in the Pager.cshtml is the root blog (e.g., /blog) and the links to the listed child items will have an incorrect url.
I can partially fix this with a simple change to List.cshtml by passing in the absoluteRequestPath value:
@Html.ThemedPartial(Model.Content, "Pager", Model.Content.Pages, new ViewDataDictionary { { "BlogRootUrl", absoluteRequestPath } })
However, the Pager component only serves up the first batch of paged items no matter what page number is selected or Next/Previous, although the correct ?p=2 is correct in the params.
Since the PagerModel is read only I can only assume that internal code in the package is setting the values - is there any special setting we need to make to allow the pager to property work on child pages?
Any suggestions for a fix for this? I've only dug in at a high level, but hopeful there's a simple fix for this. Thanks for any tips or suggestions!
The text was updated successfully, but these errors were encountered:
Running Umbraco 7.13.1 with Articulate 3.0.2 - the site's /blog rendering of the List.cshtml and Pager.cshtml partials works as expected (pager values and links work), however then rendering a child category, e.g., /blog/news the same List.cshtml and Pager.cshtml renders but the BlogRootUrl value in the Pager.cshtml is the root blog (e.g., /blog) and the links to the listed child items will have an incorrect url.
I can partially fix this with a simple change to List.cshtml by passing in the absoluteRequestPath value:
@Html.ThemedPartial(Model.Content, "Pager", Model.Content.Pages, new ViewDataDictionary { { "BlogRootUrl", absoluteRequestPath } })
However, the Pager component only serves up the first batch of paged items no matter what page number is selected or Next/Previous, although the correct ?p=2 is correct in the params.
Since the PagerModel is read only I can only assume that internal code in the package is setting the values - is there any special setting we need to make to allow the pager to property work on child pages?
Any suggestions for a fix for this? I've only dug in at a high level, but hopeful there's a simple fix for this. Thanks for any tips or suggestions!
The text was updated successfully, but these errors were encountered: