Unfortunately this is not possible and it wouldn't make sense to render a different pagination by invoking a query string.

Is there any method existing other than overriding the file? I'm wanting to use it as an AJAX function.

Hm, not too sure what do you mean here?

Instead of overriding /administrator/components/com_easyblog/themes/default/elements/pagination.php to get custom pagination counts, would it be possible in, say, com_easyblog/views/latest/view.html.php or com_easyblog/themes/[theme]/blogs/latest/default.php to use a function to override the current pagination setting?

What I'd like to do in the frontend is to allow users to change pagination.




All I need, if it exists, is the correct variable or a function to use to change existing pagination within my template override. Right now the only frontend control I can find is using the URL variable &limitstart[#]

Ah no unfortunately you cannot override views currently.

I've found I can actually override the component views no problem. I just can't figure out a clean method of controlling pagination on the front end. If nothing else, I could probably define a custom URL variable and play with the for loop.

To be frank, I don't see a point in overriding view files. Most changes in extensions would be reflected on the views / models / controllers and quite often you will find yourself re-patching your hacks over and over again

I know it because this is exactly what I did for stackideas.com previously and I regretted every bit of it.

Wouldn't this be true as well of the theme files that are invoked by the views? Nothing stays the same; eventually SOMETHING has to be fixed. I'd rather patch my files than fork your code and be standing alone with no support at all.

Well, chances of views getting modified is higher than theme files