Forum Discussion
Thanks SuzieH,
I will be using OFFSET, thanks. Is there a way to use Lithium's nice pagination indicators or will I have to whip up something that does the same function with the same structure?
Hi Inactive User,
You'll have to build a paging component. It would be great if we had some kind of default pager component that would take in specific parameters in order to be used with custom lists. If you want to post an idea...
Check out the webuisupport FreeMarker context object.
I know you're not on the latest version of the Responsive skin, but here are the current variables we have for pagination classes for styling. You'll have to check the _variables.scss file to see if your version of the skin supports these.
//== Pagination
//
//##
//$pagination-color: $text-color;
//$pagination-bg: transparent;
//$pagination-border: transparent;
//$pagination-hover-color: $text-color;
//$pagination-hover-bg: transparent;
//$pagination-hover-border: transparent;
//$pagination-active-color: $text-color;
//$pagination-active-bg: transparent;
//$pagination-active-border: transparent;
//$pagination-disabled-color: $text-color;
//$pagination-disabled-bg: transparent;
//$pagination-disabled-border: transparent;
And you might be able to make use of our Font Awesome variables for the pagination control icons: https://codepen.io/gxmikey/full/bZxrZY/
- Inactive User8 years ago
SuzieHCan you provide any information / guidance for the common.widget.pager component?
Also, the webuisupport methods are intriguing but I'd love an example of how to apply it -- confusing out of context.
I'm trying to get it to work for a custom page with custom url properties to pull blog posts for a particular author. So I create a url to give me that, for example, t5/custom/page/page-id/BlogArticlesByAuthor/author-id/50
In which case, I'm trying to pull author-id, which is not a ootb Lithium value (as far as I know), so it's throwing a Freemarker error.
<#assign author_id = webuisupport.path.parameters.name.get("author-id") />
It seems that's because it doesn't exist on the path object, rather than just pulling it from the URL. So ... how do I get that to work? Do I build a url with a parameter as shown on the webuisupport object? The documentation is unclear.
urls.fullyQualifiedPage .name.page_name .path("path_param_1_name","path_param_1_value") .query("query_param_1_name", "query_param_1_value") .build()
// returns a fully qualified url to a pageWhat does "fully qualified url" mean, and how do I create it? Etc.
I can't make heads or tails of how to use webuisupport, at least in the context of a custom page or building a fullyQualifiedUrl.
Thanks!
Hi Inactive User
The common.widget.pager isn't something that can be used in a customized way. It expects certain parameters from the underlying Java code. Exposing it in a way that would make it useful to customers would require core changes. I'm working on getting you more help with webuisupport. I'm hoping that PaoloT, ChiaraS, DougS, or AdamA might be able to help with examples.
Related Content
- 3 years ago
- 3 years ago
- 3 years ago
- 2 years ago