checkbox within TH causes output from output widget to show "TRUE" or "FALSE" regardless of whether there is header text or not

[dmarra]

I have a table which has a few columns that, in addition to header text, also have checkboxes which act as a "select all" feature. All of this works fine, until I export it using the output widget. The resulting CSV file is missing the text from the header, instead using the check state of the checkbox to determine what the column header should be.

Maybe I am doing something wrong, but this seems like a bug. I am using v2.30.4

[Mottie]

Hi @dmarra!

You can use the output_formatContent callback to determine what is sent to the output widget... in this case you can send the content when it's processing the header and the parsed data otherwise (demo):

$(function() {
  var $table = $("table");

  $(".download").click(function() {
    $table.trigger("outputTable");
  });

  $table.tablesorter({
    theme: "blue",
    widgets: ["zebra", "output"],
    widgetOptions: {
      output_formatContent: function(c, wo, data) {
        return data.isHeader ? data.content : data.parsed;
      }
    }
  });
});

[dmarra]

This looked promising, but for some reason data.parsed is always undefined... This particular table uses a custom parser; could that be the reason why?

…

On Tue, Jul 3, 2018 at 6:33 PM, Rob Garrison ***@***.***> wrote: Hi @dmarra <https://github.com/dmarra>! You can use the output_formatContent callback <https://mottie.github.io/tablesorter/docs/example-widget-output.html#output_formatcontent> to determine what is sent to the output widget... in this case you can send the content when it's processing the header and the parsed data otherwise ( demo <https://jsfiddle.net/Mottie/yL1qon7e/35/>): $(function() { var $table = $('table'); $('.download').click(function() { $table.trigger('outputTable'); }); $table.tablesorter({ theme: 'blue', widgets: ['zebra', 'output'], widgetOptions: { output_formatContent: function(c, wo, data) { return data.isHeader ? data.content : data.parsed; } } }); }); — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1565 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC_YA5U7ewBCG7bIC_LcEGmdB-CnIOuWks5uC_EhgaJpZM4VBi8E> .

[Mottie]

Ah, the demo is using the "checkbox" parser in the parser-input-select file. Your custom parser may not be returning a human readable "checked" or "unchecked" value.

[Mottie]

I'm guessing this issue has been resolved, so I'm going to close it. If you continue to have problems, please feel free to continue the discussion in this thread.