Filtering lists/tables and pagination

[arie]

Hi,
I'm using the url to filteri a list as described here (http://fabrikar.com/forums/index.php?wiki/filtering-lists-tables/).

I've got an issue when using the pagination or the dropdown number of records. If I want to go to page 2 by clicking on the pagination links or display more records using the dropdown select/option, the list doesn't keep the url filtering logic and the results are lost.

Any help?

 

[arie]

friendly bump

 

[rob]

I just checked on the joomla25 branch and could not replicate this. Can you provide more info about what you are doing?

 

[arie]

ok so let's say I want to filter a list by searching records that have an email, the url looks like:

?table_element[value]=@& table_element[condition]=CONTAINS&resetfilters=1

I have now more that 2 pages of results. Now if I want to navigate to page 2, the list is empty.
I saw that the url of the pagination Page 2 (and others) looks like:

?resetfilters=0&clearordering=0&clearfilters=0&limitstart1=30

=> the previous url pre-filters disapear form the url

Thanks

 

[arie]

friendly bump

 

[rob]

the querystring filter should be passed into the session so its normal that you no longer see it, I don't see that the results are incorrect though
Here's a video of what Im testing
http://screencast.com/t/71qP6Apkk

 

[rob]

ok so in fact I think the issue is the search string '@' is being encoded somewhere - so whilst it works in the initial query string - in the session filters I'm seeing 0 results matched

 

[arie]

I don't think so because I replaced '@' by 'a' and the problem is still here

 

[rob]

Ok so the filter code in 3.0 is OLD, and we have fixed a load of issues in it in Fabrik 3.2.
I've backported what I can, and it should fix your current issue.
Moving forward though - at some point you should consider upgrading, as it will become less likely that these types of back ports will be possible in the future. They are already horrifically difficult, this one took me over two hours to do. At some point in the not too distant future we will be stopping 3.0 support as well as Joomla 2.5 is end of life and we prefer to focus on our latest code.

 

[cheesegrits]

As far as I'm concerned, that's it for 3.0 development. We've agreed internally that 3.0 is end of lifed, time to just announce it. Put it in maintenance mode - security bug fixes only. Anything else is done on a custom, hourly rate basis.

I'd suggest we do this before the end of this month, and make the official EOL be end of May.

-- hugh