Does not work always with Ajax-views

Do you have more info for me?

Yes does not work. Please help.

I have a view that has an exposed form (which uses AJAX). It's blocking this from working.

I don't know how views ajax works so I don't know how to solve this problem.

The Minimax pager works by using javascript to set document.location to the new page. It's just like directly typing the URL. This probably bypass the views ajax.

I have a client who is offering a $50 bounty for resolving this conflict.

For what it's worth, I'm using document.location in some of my own code on a page with an exposed view form (the ajax bit) and it works fine. I'm pretty sure it's not that.

Hi. I just installed the latest version and I like it. Looks nice.

It works fine if the special buttons have not yet been pressed on the pager.

But I can confirm that typing a number in a box then pressing Enter after pressing << < > or >> does not work.

It seems in this case as if it is not seeing the enter key at all, because there is no visible reaction on pressing enter.

I am using the latest firefox on Windows, on a view in a block.

mm this makes the use of this module pretty useless for 80% of us. I'll check back when this is fixed. Then i will use it.

Subscribing.

Ajax view support is added

#9: please send bounty :)

I think you mean #7, keep me updated if he sends you the bounty, or not.

This is not fixed. Clicking the arrows is fixed. That works. But when you manually type in a page number to go to and press enter, it does not work. Nor does it work with the up and down keys.

This is what firebug console tells me when i enter a number and hit enter:

M.url.match is not a function
http://##.nl/##/sites/all/modules/jquery_update/replace/jquery.min.js?x
Line 19

lasac:

Can you empty cache and force browser reload? The javascript file has changed so it must be reloaded to the browser. It probably won't make any difference but worth a try.

The error message is complaining of a function call of "M.url.match" called from inside jquery. It's not my code. I don't know what to make of it.

Since you are using jquery_update module, I even install that and tested and it works for me. Are you using the latest version of jquery_update? If not, update it and try again.

Try my demo: http://zen.hddigitalworks.com/drpager-views

I tried both with and without jquery_update enable and in both cases it works.

I did the upgrade, and drpager works well now on most pages. But some (such as a pager in a block created by a view) it doesnt work. The << < > >> work, and the up and down arrows work, but if i enter any number and press return the spinner just never stops. Fortunately, I can escape the spins by hitting a > for example

lasac, dpatte:

I know what's wrong. I'll get it fix tomorrow.

ZZZZZZZzz

Thanks matt. The module is really great for me since my space is tight on several pages on the old pager just didnt fit. your work is appreciated.

Great, and issue happens in blocks not tested on pages, maybe i should have stated that first :P.

try 6.x-1.10. let me know how it goes.

Matt: it seems to be fixed. There is a situation where it is still buggy tough. Cant tell what the problem could be because there is no error, nowhere. But the issue is that when you have the facebook statuses module and you have the facebook statuses block on a page together with another block. And when both use the minimaxpager module, the block that is NOT the facebook statuses block stops at the number of pages that the facebook statuses block has... So ok this probably sounds strange but let say we have the following setup.

Block A - normal block created with views, 200 pages
Block F - facebook statuses block, 4 pages

Now in block A when we click the input field to use the up and down arrows for navigating, we can't go over 4, because the facebook statuses block has 4 pages. When we change the view by displaying less values so the amount of pages goes up, let's say to 17. We refresh the page where both blocks are. And now block A can't go over 17 pages... It's like the pagere script sees Block F as the block it is the pager for...

The arrows do work tough, it's just the up and down keys. If you would like i can e-mail you the url to my dev and you can see it for yourself.

oh, just noticed 1.10. That was fast!

Yes with 1.10 up down now works, and it no longer hangs with a spinner as before. Great.

But I alsohave the same problem as lasac #21, in that using the page number it can go only to the lowest page max number of this or any previous pagers that appear on the current page.

I also tried -1 in the setup to see the effect and saw no visual difference between -1, and 0 as an option in setup. What is -1 supposed to do?

It would help if I can see the problem. Paste your url here or you can send it to me via my contact page here.

If you go to http://www.dance-ottawa.com/dance-style/salsa then go to the last block (Events) and enter 12, it only goes to page 4 - the number of pages in the previous minipager block. If you enter 12 again it now goes to 5. etc

Try the 'dev' version from today.

Be sure to force page load to get the new javascript file. Also make sure the page is not from the cache.

you got, it's fixed.

Hi Matt. Congrats! The dev works fine now. Appreciate all your work. As far as I'm concered you can consider it fixed.

~