-
New Commercial Services Section
We have now opened a commercial services section here on the forum for registered users. If you have a Fabrik project that you wish to have someone work on for you, post it under Help Wanted. If you are an application developer and wish to earn some money helping others, post your details under Fabrik Application Developers.
Both of these are unmoderated. It will be up to both parties to work out the details and come to an agreement.
-
Joomla 5.1
For running J!5.1 you must https://fabrikar.com/forums/index.php?wiki/update-from-github/ or include the new file manually https://fabrikar.com/forums/index.php?threads/joomla-5-1-and-fabrik-cannot-find-files-error.54473/post-285151 See also Announcements
GoogleMap visualisation with two sources
- Thread starter koekkoek
- Start date
cheesegrits
Support Gopher
koekkoek
New Member
Hello,
We do not have any joined table on it, just single and simple table.
It's justs the same table twice with a different pre-filter (we want to display a different icon depending on address type)
I'm not shure but it looks like the filter array is kept alive from previous table on getlistModels.
So i have value=A AND value=B when value can be A OR B => No data
PS : Nice picture (avatar), hope it's fine for you now
We do not have any joined table on it, just single and simple table.
It's justs the same table twice with a different pre-filter (we want to display a different icon depending on address type)
I'm not shure but it looks like the filter array is kept alive from previous table on getlistModels.
So i have value=A AND value=B when value can be A OR B => No data
PS : Nice picture (avatar), hope it's fine for you now
cheesegrits
Support Gopher
Thanks for asking ... I'm still recovering, it was a tough 6 months, but I'm steadily getting my strength back.
OK, I'll try that scenraio.
Seems like we have two issue. I think I've found the issue which Troester was talking about, which is where where we chop the main row's keys down to the limit length for pagination. The map viz overrides pagination, as it obviously doesn't make any sense to apply 'x rows per page' limit in a map viz context. However ... that issue only happens when using joined, merged data.
So I'll take a look at the "same list" thing. And yes, I can imagine that would have issues with pre-filtering. One fix might be to copy the list, and use two different copies, rather than specifying the same list twice in the viz.
-- hugh
OK, I'll try that scenraio.
Seems like we have two issue. I think I've found the issue which Troester was talking about, which is where where we chop the main row's keys down to the limit length for pagination. The map viz overrides pagination, as it obviously doesn't make any sense to apply 'x rows per page' limit in a map viz context. However ... that issue only happens when using joined, merged data.
So I'll take a look at the "same list" thing. And yes, I can imagine that would have issues with pre-filtering. One fix might be to copy the list, and use two different copies, rather than specifying the same list twice in the viz.
-- hugh