• Hello Fabrik Community

    Fabrik is now in the hands of the development team that brought you Fabrik for Joomla 4. We have recently transitioned the Fabrik site over to a new server and are busy trying to clean it up. We have upgraded the site to Joomla 4 and are running the latest version of Fabrik 4. We have also upgraded the Xenforo forum software to the latest version. Many of the widgets you might have been used to on the forum are no longer operational, many abandoned by the developers. We hope to bring back some of the important ones as we have time.

    Exciting times to be sure.

    The Fabrik 4.0 Official release is now available. In addition, the Fabrik codebase is now available in a public repository. See the notices about these in the announcements section

    We wish to shout out a very big Thank You to all of you who have made donations. They have really helped. But we can always use more...wink..wink..

    Also a big Thank You to those of you who have been assisting others in the forum. This takes a very big burden off of us as we work on bugs, the website and the future of Fabrik.

Filtering lists/tables and pagination

I just checked on the joomla25 branch and could not replicate this. Can you provide more info about what you are doing?
 
ok so let's say I want to filter a list by searching records that have an email, the url looks like:
Code:
?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:
Code:
?resetfilters=0&clearordering=0&clearfilters=0&limitstart1=30
=> the previous url pre-filters disapear form the url

Thanks
 
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
 
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.
 
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
 
We are in need of some funding.
More details.

Thank you.

Members online

No members online now.
Back
Top