• 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.

Strange issue with User element in repeated group in details view

troester

Well-Known Member
Staff member
Setup (tested with 2 sites; one with latest Git, one with Git 2014-07-24):

List1 with user element (update on edit=no)
List2 joining to list1
on list1.id = list2.fk, repeatable.
The repeated group with the user element is displayed correctly in list view and in form view.
But in details view all user elements but the last one are empty, the last one is displaying the user element which should be in the first group entry.

It's ok if the user element is changed to a dbjoin to #_users.

Any idea?
 
yeah I can replicate this one. That part of the code is really messy, seems to be trying to test a load of stuff that may or may not be needed now.
I've got something working locally, but I want to start to write unit tests for anything like this that I fix as its the kind of change that may result in a bug elsewhere, then fixing that bug unfixes the original fix etc. At least with a unit test we can see that the original fix is still good.
in the mean time, if its urgent, let me know and I can set up a branch set up with the changes
 
It's not urgent as setting the element to dbjoin with default = {$my->id} is sufficiant (if update on edit=no).
 
Ive started on the unit tests but theres just too much set up work involved at the moment. I will try to pick it up when Hugh's back
 
We are in need of some funding.
More details.

Thank you.

Members online

Back
Top