[
https://issues.apache.org/jira/browse/OFBIZ-3083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12770937#action_12770937
]
Bruno Busco commented on OFBIZ-3083:
------------------------------------
Hi Bilgin,
thank you for reviewing the patch.
1) I agree. I will update the patch.
2) I did my tests about the ajax support on this page
https://localhost:8443/example/control/authview/findExampleAjax
and here you can see that the issue you found is not present.
I have seen that the issue in the page you point out. This is due to a wrong
link that appears on ALL the pagination buttons.
For example the NEXT button has this link when the page is first loaded:
<a
href="javascript:ajaxUpdateAreas('search-results,/accounting/control/FixedAssetSearchResults,fixedAssetName_op=like&noConditionFind=Y&fixedAssetId_op=like&fixedAssetName_ic=Y&fixedAssetId_ic=Y&VIEW_SIZE_2=20&VIEW_INDEX_2=1#')">Successivo</a>
and this link when the page is refreshed:
<a
href="javascript:ajaxUpdateAreas('search-results,/accounting/control/FixedAssetSearchResults,VIEW_INDEX_2=1&fixedAssetName_op=like&VIEW_SIZE_2=20&noConditionFind=Y&fixedAssetId_op=like&fixedAssetName_ic=Y&fixedAssetId_ic=Y&VIEW_SIZE_1=20&VIEW_INDEX_1=1#')">Successivo</a>
As you can see there is something wrong with the VIEW_INDEX_x and VIEW_SIZE_x
parameters.
The first link only contains VIEW_INDEX_2 and VIEW_SIZE_2 (and does not work),
the second link contains both VIEW_INDEX_1, VIEW_SIZE_1 and VIEW_INDEX_2,
VIEW_SIZE_2.
Anybody can help here?
> Adding a page size selector in the pagination bar
> -------------------------------------------------
>
> Key: OFBIZ-3083
> URL: https://issues.apache.org/jira/browse/OFBIZ-3083
> Project: OFBiz
> Issue Type: New Feature
> Components: framework
> Reporter: Bruno Busco
> Priority: Minor
> Attachments: OFBIZ-3083 viewSizeSelector.patch, OFBIZ-3083
> viewSizeSelector.patch, OFBIZ-3083 viewSizeSelector.patch
>
>
> I find usefull to let the user change, on the ui, the actual number of
> elements contained in a page.
> This can be usefull, for example, when there are 21 elements selected in a
> query, the user want to print them, and the page size is 20. In this case the
> user must print two pages.
> Having this feature, the user can select 30 as page size, and have all
> elements in one page.
> In the attached patch there is a first try I am working on.
> This seens to work (does not support yet ajax and i18n) but I would like to
> have the size selector shown even if all elements fit in one page so that the
> user can select a page size with less elements.
> Actually the page size selector is rendered with the prevNext bar. A solution
> that I was thinking on is to render the prevNext even if it would not be
> necessary (one page list) with all buttons disabled.
> What do you think about?
> Thank you,
> Bruno
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
