wpDataTables
Forum Replies Created
-
Hello,
Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.
In regards to this use case, our String column type can render custom HTML, so you should be able to render this as an image wrapped inside a link.
Here is an example of adding social media icons as clickable images. In our Lite/free wpDataTables, you first need to create your source file. We made an Excel spreadsheet and wrote something like this in a cell :<a href="https://facebook.com/yourprofile" target="_blank"> <img src="https://example.com/path-to-facebook-icon.png" alt="Facebook" style="width:20px;height:20px;"> </a>Replace the ‘href’ with your desired link and ‘
src‘ with the URL of the icon image.
You can also modify the desired width and height and add any other in-line CSS styles you need.
Here are a couple of screenshots of how the Excel cell looks and how the icon image renders as a clickable link in our table’s String cell :
Let us know if you have any additional questions on this topic.
Thank you.Hello,
Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.
Yes. If this is set to a date-type column – you can set it to sort the table on load and the order as descending.
Here are the detailed steps. Please go into this column’s settings, first make sure the Data type is set to “date”.
Then, go into the sorting settings – Check the option “Use as default sorting column”.
And lastly, set the order as “descending”, that’s it.
Now it should be sorting the table on load from the newest date to the oldest.
The same principle can be applied to both free and premium versions.
Let us know if you encounter any issues with this method.Hello,
Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.
As we can see from the report, it states that vulnerability was found in the premium version of wpDataTables version 6.3.1, so that premium version and the ones before that can be affected.The Lite 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 7.1) and our Lite plugin versions never did.
Unfortunately, until wpDataTables Lite goes above version 6.3.1 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,
First, I would like to sincerely apologize for the delayed response. We have been experiencing an unusually high number of tickets, and it has taken longer than usual to respond to your concern. Your patience is highly appreciated.
Can you please confirm what is the table type in question?
Looking at the error text, this could be a table linked from a JSON file – and it seems you can’t pull a specific root from the source. We will advise on this subject :1. For example, if you link the table to a JSON file, this file has to have structure as we pointed out on this documentation. I will copy the important part here :
Currently, wpDataTables accepts this, and only this format of JSON (see example on the docs page):
a one-level array of same-structured objects where each object will be parsed as a row, and each field inside of the object as a cell.
If your software does not return this format, you would need to prepare, for example, some PHP adapter to return one of the formats that wpDataTables would accept.
2. Or, if your JSON file has multiple levels, then you will have to try our NESTED JSON method.
If you’re trying to access a ‘one level deeper’ from a nested ‘root’ :As our developers pointed out in the example from the documentation hyperlinked above, if we only choose up to the first level deep in the JSON roots, 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 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.
Please note that using hooks requires certain level of programming skills and included support refers only to advice.
I hope this helps.
3. And finally, if you wish to use API and pull data from it, then you will have to adapt it to PHP Array, and make a table linked to PHP Array.
Please note, as we pointed out in that Documentation from the last hyperlink, when using a PHP Array as source data :
The format of the serialized array should be the following: 2D-array, where the parent level is an indexed array, and the second level is an associative array.
Parent array entries will be parsed as rows, child array keys will be parsed as column headers, and child array values as cell values.
If you can’t make any new tables, and you tried different table types, did you recently update our Plugin?
If so, it perhaps happened that some files on your FTP or WP Database did not ‘pick up’ some new file/functionality we might have added in an update. It is very rare to happen, though, but if that’s the case, you can try this :
Deactivate our Plugin in WP-Admin.
– Purge all cache of your Site
– Re-activate our Plugin
– Purge cache again
– Try to make a new table, and see if it works.
If that does not help, please provide us with more details about the issue, such as what type of table you’re trying to create;
If the source file for the linked table does not contain sensitive data, you can upload it to WeTransfer and send a download link.
If it has any sensitive data, it is best if you can open a pre-purchase ticket on our Main Support platform which doesn’t require a purchase code. You can just refer to this Post and one of our Agents can help you in more details there.
Kind regards.Hello,
We are aware of this report, it has been sent to us by other users.
As we can see from the report, it states that vulnerability was found in the premium version of wpDataTables version 6.3.1, so that premium version and the ones before that can be affected.The Lite 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 7.0.1) and our Lite plugin versions never did.
Unfortunately, until wpDataTables Lite goes above version 6.3.1 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.