Pagination problem

hello, 

First of all thank you for your utility. It is very powerful and easy to use, the generated code is clean ... great. 

Just one problem I encounter several months I use component creator: 
I can not handle paging. 

The default is random (page 16 items first, second page 20 ...) ... 

In addition, when returns on the component, paging stays on the page on which it was when the left ... 

I can not find an option to manage it in the creation of the component and when I try to change it in the php, it does not work. 

print_r () on $ this-> pagination gives: 


but on this page, I have 16 items and 18 of the following ... 

weird...

nobody has an idea? it would help me a lot.

Hi Simon, 

This looks like a weird behavior, have you reported it to our support team via component-creator.com/en/contact ?

I just followed your advice. Thank you.

This is the second time that I have come to the forums and found a question asked in the past that I now face. The answer is the same as last time: "contact support."

It would really be great if the answers to these questions were posted back at the forum the last time that someone solved it so that others could benefit from the work previously done.

I dont want pagination. At all. How do I disable it? How do I control it?

I found a solution as follows:

in the model file for your view, look for this code:

protected function populateState($ordering = null, $direction = null)
{
// Initialise variables.
$app = JFactory::getApplication();

// List state information
$limit = $app->getUserStateFromRequest('global.list.limit', 'limit', $app->get('list_limit'));

Change the line:
$limit = $app->getUserStateFromRequest('global.list.limit', 'limit', $app->get('list_limit'));

to this

$limit = 50;

or whatever number you want.

If you try to set the pagination property of the JPagination object in the view to something else, then the object will be modified (as verifiable through) var_dumping the pagination property to the screen, but the changes in limits will not have been made prior to the records being pulled from the server. Thats why you have to hack the model itself and short-circuit the call to the global list limit for the app.

There is probably a more thoughtful way to do this. Does anyone know a way to change the global value?