wpDataTables
Forum Replies Created
-
Hello,
We can see the issue on your Page. As you described, the table does load in your PopUp, but we notice the search or changing the number of rows per page does not work, while it works for the version of the table outside of your PopUp?
?
We are sending this use-case to our QA Team.
They will do tests to check if we can reproduce the issue of the table functionalities when loaded in a popup.
After that, we will report back to advise you on the findings.
Thank you for reporting this and your patience.Hello,
We will check with our developers if there is any possible typo on that part of the Documentation. If there is, they will fix it as quickly as possible.
I am just not fully understanding what you asked in this part :?‘What value of the param will we get as a result?
Is that how it should be?’We will do our best to advise you on what those hooks are used for, etc.
As our developers pointed out in this example on our Documentation?,
if we only choose up to the first level deep in the JSON roots from our sample Nested JSON file?, such as “root>results”,
then it works without any additional step needed.
There is this part of the Documentation beneath the example, where our devs stated :
Please note: The root path that is chosen, needs to have the same object with the same keys and values as you can see for chosen path “root->results”.
If values are not a string, then those values will be skipped by default.
In this case keys “films”, “vehicles”, “starships”, and “species” have values as arrays (in some cases they can be objects) and they will not be shown.
If you need to show data from those arrays as well, there is an option with a hook.
So, when one of the chosen root path objects contains keys that have an array or objects as values
and you need to include them in a table as cell values, then you can choose from these two hooks:
- wpdatatables_get_one_level_deep_json_data_from_array_as_string
and
- wpdatatables_set_one_level_deep_json_data_separator
Please check more details explained about this on this Documentation Page,
find the title as “Use hooks to parse one more level deep in root path”.
There you will find the detailed explanation how you can use this hook to access one more leel deep in your JSON root path.
As for the specific part you asked, the parameters :
For the first hook that accepts 3 params.- First param(parameter) is $deepParse – boolean – false by default.
2. Second param is $jsonURL – string – nested JSON URL.
3. Third param is $tableID – int – id of the table.
You only need to provide a boolean value true, please check our example from that Page.
Please note that using hooks requires certain level of programming skills and included support refers only to advice.
You can get a detailed description of WordPress hooks here in WP Codex
I hope this helps.
Hello,
It seems you set this column in our Table to be ‘integer’ data type?
That can not work, because for any numeric type column (float/integer), our Plugin can only render pure numerical data.When the data has brackets or spaces, anything other than pure numerical data format – this will be rendered as 0 or 1, as in your case.
The solution is to please change that column type to string and this should then render all the entries correctly.
Let us know if you encounter any further issues.
Kind regards.Hello,
if you take a closer look at that report, it clearly states that vulnerability was found only in the premium version 6.3.1 of wpDataTables , so that premium version and the ones before that can be affected.The Lite/free version of our Plugin does not have these functionalities (such as SQL based tables), so Lite version was never affected. Those reports are not related to the Lite version, but they can be reported in the lite version because the resources where this information about themes or plugins vulnerabilities are stored are generated by the theme or the plugin slug. Those slugs are the same in both lite and the full version, and because of that, you get those notifications.
The important thing is that there’s nothing to worry about. Newer versions of the wpDataTable premium don’t have these issues, ( the latest one at the time of this reply is 6.6.1) and our Lite plugin versions never did.
Unfortunately, until wpDataTables Lite goes above version 3.4.2 these reports will indicate a false positive. The lite and the full version have the same slug (wpdatatables), and that’s why the security plugins can’t differentiate between the versions.
I hope this helps, let us know if anything is unclear.
Thank you.Hello,
Thank you for reporting this. We are able to reproduce this issue when we made a Chart JS Line Chart from an Excel linked table.
We used the same date format, as per your screenshots, the default d/m/Y, placed some dummy dates and they render well in the table, but look strange on the chart X axis.
We passed this to our QA Team for further testing. It seems it is a bug with our latest Lite version, but we will report back to confirm this for you as soon as possible.
Thank you for your patience.