Hi Amardeep, What you have recommended is looking good to me i.e. pagination target URL should be independent of page URL and it should be added on form using paginate-target attribute of form widget.
The approach you are planning to take is also looking good to me i.e. to create on parent ticket and add a child ticket for each of component to check and fix. Best regards, Pranay Pandey HotWax Systems http://www.hotwaxsystems.com/ On Tue, Jun 14, 2016 at 9:43 PM, Amardeep Singh Jhajj < amardeep.jh...@hotwaxsystems.com> wrote: > Hi Everyone, > > I found issue in pagination on some screens when we do any operation (like > update, delete) on list item. > > For example: I have updated the content type from list in Content Setup > Menu in Content application and then clicked on next link of pagination, I > got the following error: > > The Following Errors Occurred: > > Error calling event: org.ofbiz.webapp.event.EventHandlerException: Found > URL > parameter [contentTypeId] passed to secure (https) request-map with uri > [updateContentType] with an event that calls service [updateContentType]; > this is not allowed for security reasons! > > The above error is unexpected as I just tried to see next list records of > ContentType. The reason of error is pagination URL which is same as URL of > page i.e. updateContentType. This URL is the update operation URL and it is > not redirected to appropriate page after operation. > > IMO, pagination target URL should be independent of page URL and it should > be added on form using paginate-target attribute of form widget. > > This issue can be possible in all components. I am planning to create one > parent ticket and will add their child tickets wherever needed for each > component for adding "paginate-target" to the forms. > > Please let us know your thoughts. > > Thanks and Regards > -- > Amardeep Singh Jhajj > http://www.hotwaxsystems.com/ >
