Bug in Databasejoin AJAX update on where statement

[PvN94]

When using a databasejoin element with the ajax update option set to yes, the ajax update removes the 'Order by' part of the where statement, instead ordering just by the dbjoin value (id).

The ordering works fine when loading a new or existing record, it's just after the ajax has run that the ordering is gone and the standard ordering is used.

 

[troester]

Which exact Fabrik/GitHub version?
I think there was a thread about Order by/Limit etc. recently.

 

[PvN94]

It was a pretty recent versio (couple weeks ago from github), but to be sure I updated everything to the most recent version (joomla and fabrik) and did a github update. The behavior is the same in the newest version.

 

[cheesegrits]

If you'd like to take out a support sub, I'll see what I can do.

-- hugh

 

[PvN94]

Not sure it's a big enough issue for me to take out a subscription to have it fixed.
I just thought I'd notice you of the bug, seeing as the ajax update option is, according to the description, still a work in progress, and you may not know of it yet.

 

[cheesegrits]

Not sure it's a big enough issue for me to take out a subscription to have it fixed.

OK.

-- hugh