How to deal with inconsistent Data output with WPML and DataTables FixedHeader disabled? #9

Open
opened 2021-12-15 12:44:43 +00:00 by 0rca · 3 comments

I have been using tablepress-pods on two sites now and it is very useful.
I managed to show a subset of data like this

[table id="2" pod_name="aussteller" pod_where="eventid.meta_value = '0022022' " datatables_fixedheader="top" datatables_fixedheader_offsettop="120" cache_table_output=false /]

You can see the output here: https://munichfashioncompany.com/trade-shows/womenmen-dusseldorf/#labels

For whatever reason I had the extension DataTables FixedHeader disabled and then the table was missing a lot of data, whole columns where empty in one language and showing different data in another.

Only by chance I realized that activating DataTables FixedHeader again fixes the issue, removing the (obsolete) datatables_fixedheader arguments does also help.

I think this is no issue with tablepress-pods per se, but it only accours in conjunction with it. And I also know this constellation is very obscure and unique, but I still wanted to post my findings in case anybody ever has something similar.

I have been using tablepress-pods on two sites now and it is very useful. I managed to show a subset of data like this ``` [table id="2" pod_name="aussteller" pod_where="eventid.meta_value = '0022022' " datatables_fixedheader="top" datatables_fixedheader_offsettop="120" cache_table_output=false /] ``` You can see the output here: https://munichfashioncompany.com/trade-shows/womenmen-dusseldorf/#labels For whatever reason I had the extension DataTables FixedHeader disabled and then the table was missing a lot of data, whole columns where empty in one language and showing different data in another. Only by chance I realized that activating DataTables FixedHeader again fixes the issue, removing the (obsolete) datatables_fixedheader arguments does also help. I think this is no issue with tablepress-pods per se, but it only accours in conjunction with it. And I also know this constellation is very obscure and unique, but I still wanted to post my findings in case anybody ever has something similar.
Owner

If I am understanding, disabling DataTables FixedHeader and removing the datatables_fixedheader... parameters from the shortcode results in the expected behavior. In that case, I think I agree that there is no problem or action item necessary with tablepress-pods. Please confirm, and I will mark this issue appropriately. But thank you for the report, and I am glad that tablepress-pods is being helpful for you.

If I am understanding, disabling DataTables FixedHeader **and** removing the datatables_fixedheader... parameters from the shortcode results in the expected behavior. In that case, I think I agree that there is no problem or action item necessary with tablepress-pods. Please confirm, and I will mark this issue appropriately. But thank you for the report, and I am glad that tablepress-pods is being helpful for you.
Author

It is disabling DataTables FixedHeader OR removing the datatables_fixedheader... parameters. In other words the datatables_fixedheader parameters are having very strange effects on the data itself.
But yes, mark the issue as you see fit or remove it, I just wanted to let you know.
Cheers,
Michael

It is disabling DataTables FixedHeader **OR** removing the datatables_fixedheader... parameters. In other words the datatables_fixedheader parameters are having very strange effects on the data itself. But yes, mark the issue as you see fit or remove it, I just wanted to let you know. Cheers, Michael
Owner

Thanks, Michael. I am not sure I entirely understand the situation, but it still sounds to me like there is not direct evidence of a problem with tablepress-pods itself, but some poor interaction with DataTables FixedHeader, which can be worked around in an acceptable way. No need to post further if that is basically right. I will leave this up as an FAQ in case it is useful to someone else working with tablepress-pods.

Thanks, Michael. I am not sure I entirely understand the situation, but it still sounds to me like there is not direct evidence of a problem with tablepress-pods itself, but some poor interaction with DataTables FixedHeader, which can be worked around in an acceptable way. No need to post further if that is basically right. I will leave this up as an FAQ in case it is useful to someone else working with tablepress-pods.
glen changed title from Inconsistent Data output with WPML and DataTables FixedHeader disabled to How to deal with inconsistent Data output with WPML and DataTables FixedHeader disabled? 2021-12-15 17:34:03 +00:00
glen added the
FAQ
label 2021-12-15 17:34:14 +00:00
Sign in to join this conversation.
No Milestone
No Assignees
2 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: glen/tablepress-pods#9
No description provided.