[
https://issues.apache.org/jira/browse/OFBIZ-6547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14614781#comment-14614781
]
Akif Dinc edited comment on OFBIZ-6547 at 7/6/15 9:37 AM:
----------------------------------------------------------
Unfortunately adding paginate-target did not help here.
{noformat} paginate-target="mydevice" {noformat}
I need to say that the Form is included in a screen with include-form within a
screenlet. It still passes the previously submited values to the Next-button.
was (Author: adinc):
Unfortunately adding paginate-target did not help here.
{noformat} paginate-target="mydevice" {noformat}
I need to say that the Form is included in a screen with include-form within a
screenlet.
> Screen with pagination on tables lead to multiple db entries when submitting
> -----------------------------------------------------------------------------
>
> Key: OFBIZ-6547
> URL: https://issues.apache.org/jira/browse/OFBIZ-6547
> Project: OFBiz
> Issue Type: Bug
> Components: product
> Affects Versions: Trunk, 13.07.01
> Reporter: Akif Dinc
> Priority: Minor
> Attachments: OFBIZ-6547.patch
>
>
> Submitting a form on a Screen with larger list leads to double DB entries if
> pagination (next) is used.
> From the cookbook it is known that pagination is automatically added if
> viewSize and viewIndex is set. Using this "auto pagination" functionalities
> next button after submitting passes the submit parameters to the next call
> aswell.
> Following steps do reproduce the problem:
> * open up
> http://demo-stable-ofbiz.apache.org/catalog/control/EditProdCatalogCategories?prodCatalogId=TestCatalog&VIEW_SIZE_1=20&VIEW_INDEX_1=1
> * Take default element numbers per page (20)
> * Add a Category (and submit)
> * Check DB for added entry
> * Hit Next page link
> * Check DB again for entry (there will be twice the same)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
