@Nicolas_NALLET - try _fullText MATCHES 'France'
Jun 9 2019
Mar 25 2019
I thought you included an extra cargo query or some parser function in the CONCAT field, but it's the same one.
After reading your use case, I don't know if you would be able to include the template's content directly in CONCAT.
This is a mystery to me as to why there is not the UNIQ-QINU error in the first case (i.e. when not using |details fields).
Ah, that's not good. If possible, can you please give me the exact query you are doing?
Even with |no html? When I tried it, then I either got UNIQ-QINU error (without |no html) in both cases or in none of the cases.
Mar 24 2019
I directly include the query in CONCAT function. I don't know if it's the best way or not, but it works for simple queries.
That note was for nested cargo queries, but your CONCAT field seemed like a template call. Or, are you using a different field now?
Mar 23 2019
@Yaron_Koren : What do you think about the 2nd bug?
Still, unlike a regular Table query, the field used by |oder by= must actually be included in the query, which is fine but it would be better to be able to use a field for |oder by= without actually displaying it.
Did you also include the changes in the formats/CargoDynamicTableFormat.php file?
Mar 15 2019
@Madrigal84 - I just created a patch for the first issue. It would be great if you check out the code, and see if it works for you.
@Madrigal84 - You're right. With details field, order by is being ignored.
Mar 14 2019
Sorry! But in my case, if Date is in the field list, then results are just as intended. If it's not, then whatever you're saying is happening (i.e. order by is being ignored).
@Madrigal84 - Okay, in the example you gave earlier, is date in your field list or not? Because, if it's not, then in dynamic table, order by will be ignored and the table will be sorted according to the first column.
You are not allowed to push any changes directly to the repository. You need to submit it for review first.
@Madrigal84 - I am unable to regenerate the first bug you mentioned. In my case, the table is being sorted according to the columns in order by property, not the first column.
And in the 2nd bug, what happens when you expand the details field column? What is being shown there?
Feb 19 2019
@Ofbeaton - I just checked in this patch: https://gerrit.wikimedia.org/r/c/mediawiki/extensions/Cargo/+/491407 . It should do.
Sep 8 2018
Final report can be found here.
Jun 9 2018
Apr 2 2018
most probably, mysql driver is not enabled.
Mar 31 2018
I don't think it can be fixed in ext.cargo.maps because these links are called by OpenLayers.js.
I found a discussion related to this, it may be somewhat helpful: https://gis.stackexchange.com/questions/83953/openlayers-maps-issue-with-ssl
Mar 30 2018
Mar 29 2018
Loading failed for the <script> with source “https://www.openlayers.org/api/OpenLayers.js”.
Mar 25 2018
Mar 20 2018
Mar 12 2018
Mar 11 2018
Mar 4 2018
@BamLifa: Are you working on this?
Feb 18 2018
@Yaron_Koren: Can you please review the above patch set submitted by me? And tell if it will do or something else is needed. It's working fine locally.