@mattab opened this Issue on February 21st 2019 Member

When exporting in an iframe the whole application using the Widgetize feature, when users try to export a report's data, they click on "Export this dataset in other formats" which generates JS error "TypeError: dataTable is undefined".

Steps to reproduce

as reported by a customer:

  • for example using this URL:
  • go under a report and click export icon "Export this dataset in other formats"
  • Got: JS error "TypeError: dataTable is undefined" and the popover stays on "Loading Export..."
  • Expected to see the popover and choose export options, and successfully export the data.
@diosmosis commented on February 21st 2019 Member

@mattab I'm not sure if widgetizing the entire app is supported by Widgetize? should just need to create an iframe to module=CoreHome&action=index

@tsteur commented on February 21st 2019 Member

This is not a supported feature and we're not really planning to add this @mattab

@tsteur commented on February 21st 2019 Member

There are potentially heaps of issues and it can be potentially heaps of work to make it work etc. It be very very appreciated to close this issue as wont fix or keep it open as a feature enhancement for the future in the backlog.

@mattab commented on February 21st 2019 Member

Yes correct, we don't want to implement it :+1:

That said, my suggestion would be: when module=Widgetize & moduleToWidgetize=CoreHome could we output a simple error message that says something like this (or better)

CoreHome embedding via an iframe is not a supported feature. Instead you can follow these steps:
1) in your iframe, embed Matomo directly using module=CoreHome (instead of module=Widgetize) and
2) change the INI setting as per this FAQ to allow iframing Matomo.

This would help guide users towards the supported way to do things (avoid bug reports) and make clear we don't support it.

Powered by GitHub Issue Mirror